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 1376-1400 of 1604 flagged pages
Backup Troubleshoot data recovery from Microsoft Azure Backup Server by using Azure Backup ...ckup/backup-azure-alternate-dpm-server-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively references Microsoft Azure Backup Server (MABS), which is based on Windows Server and Data Protection Manager (DPM). All troubleshooting steps and error messages assume a Windows environment, with no mention of Linux-based backup servers, Linux agents, or cross-platform recovery scenarios. There are no examples, recommendations, or tools provided for Linux users.
Recommendations
  • Explicitly state platform requirements and limitations at the beginning of the article, clarifying that MABS is Windows-only.
  • Provide links or references to equivalent Azure Backup solutions for Linux environments, such as Azure Backup for Linux VMs or Azure Backup agent for Linux.
  • Include troubleshooting steps, error messages, and recovery recommendations for Linux-based backup scenarios where applicable.
  • Ensure parity in documentation by offering examples and guidance for both Windows and Linux users, or clearly indicate when a feature is Windows-exclusive.
GitHub Create Pull Request
Backup Support matrix for Azure Elastic SAN Backup (preview) ...cles/backup/azure-elastic-san-backup-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively references the Azure portal for configuration, restore, and management operations, without mentioning or providing examples for cross-platform command-line tools such as Azure CLI or PowerShell. There is no explicit mention of Windows-specific tools, but the absence of Linux/CLI examples and the portal-centric approach can be considered a subtle Windows-first bias, as the Azure portal is often associated with Windows environments and workflows.
Recommendations
  • Add examples for configuring, restoring, and managing Elastic SAN backup using Azure CLI commands, which are cross-platform and widely used on Linux.
  • If PowerShell examples are provided elsewhere, ensure equivalent Azure CLI examples are present and given equal prominence.
  • Explicitly mention that all operations can be performed from Linux, macOS, or Windows using Azure CLI, and provide links to relevant CLI documentation.
  • Include a section comparing portal, PowerShell, and CLI workflows, highlighting parity and platform neutrality.
GitHub Create Pull Request
Backup Troubleshoot Azure Kubernetes Service backup ...backup/azure-kubernetes-service-backup-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily through the exclusive use of Azure Portal GUI instructions and Azure CLI commands, with no mention of Linux-specific tools, shell environments, or alternative workflows. All step-by-step instructions for resource scaling, extension configuration, and troubleshooting are given for the Azure Portal (a web GUI, often used by Windows admins) or Azure CLI, but there are no examples for Linux-native tools, shell scripting, or PowerShell alternatives. There is no explicit mention of Linux, Bash, or cross-platform command-line nuances, and no guidance for users who may be operating from Linux workstations or headless environments.
Recommendations
  • Add explicit Bash shell examples for all CLI commands, including environment variable usage and output parsing.
  • Clarify that Azure CLI commands are cross-platform and provide any necessary Linux-specific installation or usage notes.
  • Include instructions for managing AKS resources using Linux-native tools (e.g., Bash scripts, SSH, text editors like vim/nano for YAML editing).
  • Mention PowerShell alternatives for users on Windows, but ensure parity by providing Bash equivalents.
  • Add troubleshooting steps that consider Linux environments (e.g., file permissions, shell differences, package management).
  • Explicitly state platform requirements or differences where relevant, especially for steps involving local file operations or scripting.
GitHub Create Pull Request
Backup Create backup policies via REST API in Azure Backup ...up/backup-azure-arm-userestapi-createorupdatepolicy.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Windows Timezones
Summary
The documentation page exhibits mild Windows bias primarily through the repeated use of 'Pacific Standard Time' as the example time zone in request bodies and responses, rather than a more neutral or Linux-friendly time zone like UTC. The first example policy for Azure VM and SAP HANA VM uses 'Pacific Standard Time' before switching to UTC in later examples. No explicit PowerShell, Windows-only tools, or CLI examples are present, and the REST API usage is platform-neutral. However, the time zone selection and ordering of examples may subtly favor Windows conventions.
Recommendations
  • Use UTC as the default time zone in all example request bodies and responses, or provide examples for both UTC and a common Windows time zone.
  • Add a note clarifying that time zones are configurable and provide a link to supported time zone formats for both Windows and Linux.
  • Ensure that examples and documentation do not implicitly prioritize Windows conventions (such as time zone names) over platform-neutral or Linux-friendly options.
  • If there are platform-specific considerations (e.g., time zone format differences between Windows and Linux), document these explicitly.
GitHub Create Pull Request
Backup Create backup policies for Azure database for PostgreSQL - Flexible server using data protection REST API in Azure Backup ...base-postgresql-flex-use-rest-api-create-update-policy.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias by referencing the 'default PowerShell object' for PostgreSQL - Flexible servers as the baseline for backup policy scheduling and retention. No equivalent Linux CLI or Bash scripting examples or references are provided, and PowerShell is mentioned as the default tool for object creation and management. There are no explicit Linux or cross-platform command-line examples, nor is there guidance for users who may prefer Bash, Azure CLI, or other non-Windows tooling.
Recommendations
  • Replace or supplement the reference to 'default PowerShell object' with cross-platform alternatives, such as Azure CLI, Bash, or REST API examples.
  • Provide explicit Linux/Bash/CLI examples for creating and managing backup policies, alongside or instead of PowerShell references.
  • Clarify that the REST API can be used from any platform, and offer sample commands using curl or httpie for Linux/macOS users.
  • Avoid implying PowerShell is the default or only supported method; instead, present it as one of several options.
  • Add a section or note for Linux/macOS users, highlighting platform-agnostic approaches and tools.
GitHub Create Pull Request
Backup Manage SQL server databases in Azure VMs using Azure Backup via CLI ...ob/main/articles/backup/backup-azure-sql-manage-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references SQL Server running in Azure VMs, which is most commonly associated with Windows environments. All examples use Azure CLI, which is cross-platform, but there are no explicit references or examples for Linux-based SQL Server VMs. There is no mention of Linux-specific considerations, tools, or patterns, nor any parity notes for Linux users. The documentation implicitly assumes a Windows context (e.g., SQL Server, VM/container naming conventions) and does not address Linux SQL Server scenarios.
Recommendations
  • Add explicit notes clarifying whether the instructions apply to both Windows and Linux SQL Server VMs.
  • Include examples or guidance for managing SQL Server on Linux-based Azure VMs, if supported.
  • Mention any differences in backup/restore processes, prerequisites, or limitations for Linux SQL Server VMs.
  • Reference Linux-specific tools or troubleshooting steps where relevant.
  • Ensure terminology and resource naming conventions do not assume a Windows-only context.
GitHub Create Pull Request
Backup Back Up Azure VMs with the Enhanced Policy ...in/articles/backup/backup-azure-vms-enhanced-policy.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed PowerShell examples for configuring Enhanced backup policies, with step-by-step cmdlets and explanations. These examples are significantly more extensive than the Azure CLI section, which is comparatively brief and lacks the same level of detail. PowerShell is a Windows-centric tool, and its prominence suggests a bias toward Windows users. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native tools or workflows. The order of presentation also places PowerShell before CLI, reinforcing a Windows-first approach.
Recommendations
  • Provide equally detailed Azure CLI examples, including step-by-step breakdowns and explanations for each command, matching the PowerShell section.
  • Add Bash shell examples for Linux users, especially for tasks like time zone handling, date formatting, and JSON manipulation.
  • Explicitly mention Linux compatibility and workflows, including any differences or considerations when running Azure CLI on Linux.
  • Consider reordering sections so that Azure CLI (cross-platform) examples appear before PowerShell, or present both in parallel tabs.
  • Include notes or links to documentation for using these commands on Linux systems, and clarify any platform-specific requirements.
GitHub Create Pull Request
Backup Perform actions using Backup center in Azure Backup ...ocs/blob/main/articles/backup/backup-center-actions.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure Virtual Machines (VMs), SQL in Azure VMs, and SAP HANA in Azure VMs, which are commonly associated with Windows workloads. Examples and links focus on VM backup and restore operations without specifying or providing parity for Linux VM scenarios. There are no explicit Linux or cross-platform CLI examples, nor are Linux-specific backup/restore patterns or tools mentioned. The documentation does not clarify whether instructions apply equally to Linux VMs, nor does it provide Linux-specific guidance or troubleshooting.
Recommendations
  • Explicitly state that backup and restore instructions apply to both Windows and Linux Azure VMs, or clarify any differences.
  • Provide Linux-specific examples, such as restoring a Linux VM, configuring backup for Linux VMs, or using Linux-based workloads.
  • Include cross-platform CLI (e.g., Azure CLI, Bash) examples alongside any GUI instructions.
  • Reference Linux tools or patterns (e.g., file system considerations, application consistency for Linux workloads) where relevant.
  • Add troubleshooting notes or links for common Linux backup/restore issues.
GitHub Create Pull Request
Backup Support matrix for Backup center for Azure Backup ...b/main/articles/backup/backup-center-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page lists supported workloads and scenarios for Azure Backup Center. While it covers both Windows and Linux workloads (e.g., Azure VMs, Azure Database for PostgreSQL, SAP HANA), there is a noticeable Windows bias in the 'Insights' section, where legacy Windows backup tools (System Center Data Protection Manager, Azure Backup Agent (MARS), Azure Backup Server (MABS)) are mentioned explicitly, but no equivalent Linux-native backup tools are referenced. Additionally, examples such as 'SQL in Azure VM' and 'SAP HANA in Azure VM' are listed, but there is no explicit mention of Linux VM backup scenarios or parity in tooling. The order of workloads often places Windows-centric technologies first (e.g., Azure Virtual Machine, SQL in Azure VM) before Linux-centric workloads.
Recommendations
  • Explicitly mention Linux VM backup scenarios and clarify support for Linux-based workloads in the tables.
  • Include references to Linux-native backup tools or third-party solutions where applicable, to balance the mention of Windows tools.
  • Ensure that workload lists alternate or group Windows and Linux workloads together, rather than listing Windows-centric technologies first.
  • Add examples or documentation links for Linux backup and restore operations, not just Windows/SQL/MARS/MABS.
  • Clarify whether features such as 'View Backup Reports' or 'Create backup policy' are equally available for Linux VMs and workloads.
GitHub Create Pull Request
Backup Update the existing VM backup policy using CLI ...docs/blob/main/articles/backup/modify-vm-policy-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a CLI-based workflow for updating Azure VM backup policies, but the only file path example given uses Windows-style paths (C:\temp2\Policy.json). There are no Linux or macOS path examples, nor any mention of Linux-specific considerations. This may unintentionally signal a Windows-first bias and could confuse or exclude Linux users.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/user/Policy.json) alongside Windows examples.
  • Add a note clarifying that file paths should be adapted to the user's operating system.
  • Ensure that all CLI examples are OS-agnostic or provide parallel examples for both Windows and Linux/macOS.
  • Mention common text editors for both Windows (e.g., Notepad) and Linux (e.g., nano, vim) when editing JSON files.
GitHub Create Pull Request
Backup Overview of offline backup ...s/blob/main/articles/backup/offline-backup-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation focuses exclusively on Microsoft Azure Backup Server (MABS), System Center Data Protection Manager (DPM), and the MARS Agent—all Windows-based backup solutions. There is no mention of Linux backup agents, Linux-compatible workflows, or examples using Linux tools. The described utilities and processes (such as BitLocker encryption and custom utilities for disk preparation) are Windows-centric, and there are no Linux equivalents or instructions provided.
Recommendations
  • Include information about Linux backup agents or workflows, if supported, and clarify platform compatibility for each offline backup option.
  • Provide Linux-specific examples for preparing disks, such as using Linux command-line tools (e.g., dd, cryptsetup for disk encryption) and mounting disks.
  • Mention Linux-compatible encryption methods and utilities alongside BitLocker.
  • Add guidance for Linux administrators on how to use Azure Import/Export service and Data Box, including any required software or steps.
  • Clearly state any platform limitations if offline backup is only supported on Windows, and suggest alternatives for Linux environments if applicable.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Blobs using Azure Backup ...ob/main/articles/backup/blob-backup-configure-quick.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell as a restore method before Azure CLI, and by referencing PowerShell specifically (which is traditionally associated with Windows environments) in the 'Next step' section. There are no explicit Linux-specific examples or mentions of Linux tools, and PowerShell is presented as a primary automation method, which may disadvantage Linux users who typically use Bash or CLI.
Recommendations
  • List Azure CLI before Azure PowerShell in example sequences to avoid implicit prioritization of Windows tooling.
  • Include explicit Linux/Bash examples or references where automation or scripting is discussed.
  • Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux (Bash) environments.
  • Add a note or section highlighting parity between Windows and Linux tooling for Azure Backup operations.
GitHub Create Pull Request
Backup Script Sample - Disable Soft delete for File Share using ARM API .../backup/scripts/disable-soft-delete-for-file-shares.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows environments by using Windows-style file paths (e.g., .\rqbody-disableSoftDelete.json) in command examples and omitting Linux/macOS equivalents. There are no Linux-specific instructions or examples for running armclient, nor any mention of cross-platform usage considerations.
Recommendations
  • Include Linux/macOS command examples using forward slashes (e.g., ./rqbody-disableSoftDelete.json) and clarify file path differences.
  • Explicitly state armclient is cross-platform (if true), and provide installation instructions for Linux/macOS.
  • Add notes or examples for running commands in Bash or other non-Windows shells.
  • Ensure parity in documentation by presenting both Windows and Linux usage patterns side-by-side.
GitHub Create Pull Request
Backup Back up Azure Managed Disks using Azure CLI .../blob/main/articles/backup/backup-managed-disks-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is generally cross-platform, focusing on Azure CLI, which is available on both Windows and Linux. However, there are subtle signs of Windows bias: variable assignment examples use PowerShell syntax (e.g., $DiskId = ...), and references to Azure PowerShell and the Azure portal are mentioned before CLI in the 'Next steps' and permissions assignment sections. There are no explicit Linux shell (bash) examples, and PowerShell-style variable usage may confuse Linux users.
Recommendations
  • Provide both PowerShell and Bash variable assignment examples when referencing environment variables, e.g., show both $DiskId=... (PowerShell) and DiskId=... (Bash).
  • When listing next steps or alternative tools, mention CLI and Linux-friendly options before or alongside PowerShell and portal.
  • Explicitly state that all Azure CLI commands work on both Windows and Linux, and consider including a note or section for Linux users if there are any OS-specific considerations.
  • Where possible, avoid using syntax or patterns (like $variable assignment) that are specific to Windows/PowerShell in generic CLI documentation.
  • If referencing scripts or automation, provide both .ps1 (PowerShell) and .sh (Bash) script examples or templates.
GitHub Create Pull Request
Backup Azure Resource Manager and Bicep files ...lob/main/articles/backup/backup-rm-template-samples.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly providing a template for deploying a Windows Server VM with backup enabled, while not offering equivalent examples or templates for Linux VMs. There is no mention of Linux-specific backup scenarios, nor are Linux VM deployment and backup templates included alongside the Windows example. The page also references SQL Server (a Microsoft technology typically associated with Windows), without mentioning Linux database workloads.
Recommendations
  • Add templates and examples for deploying and backing up Linux VMs, such as Ubuntu or CentOS, with Recovery Services vault integration.
  • Include backup scenarios for popular Linux workloads (e.g., MySQL, PostgreSQL running on Linux VMs) to match the SQL Server example.
  • Ensure that documentation references both Windows and Linux environments equally, and avoid presenting Windows scenarios first or exclusively.
  • Where possible, clarify that templates and backup features are cross-platform, and specify any platform-specific limitations or requirements.
GitHub Create Pull Request
Backup Tutorial - Configure vaulted backup for Azure Blobs using Azure Backup ...main/articles/backup/blob-backup-configure-tutorial.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by listing Azure PowerShell as the first option for restoring Azure Blobs, ahead of Azure CLI and REST API. This ordering can imply a preference for Windows-centric tooling. There is also a slight emphasis on PowerShell in the related content, which is more commonly used on Windows, though Azure CLI is mentioned as well. No explicit Linux tools or examples are provided, and there are no direct Linux-specific instructions or parity notes.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or list CLI first to avoid implying preference for Windows tools.
  • Explicitly mention that Azure CLI is cross-platform and provide examples for both Windows and Linux shells where appropriate.
  • Add notes or links for Linux users, such as installation instructions for Azure CLI on Linux.
  • Include example commands for both PowerShell and Bash (or other Linux shells) in relevant sections.
  • Clarify that all operations can be performed equally on Linux and Windows, and highlight any platform-specific considerations.
GitHub Create Pull Request
Backup Encrypt backup data by using customer-managed keys ...ob/main/articles/backup/encryption-at-rest-with-cmk.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides examples for Azure portal, PowerShell, and Azure CLI for all major operations. However, PowerShell examples are consistently present and detailed, sometimes with more explanation or output formatting than CLI. The page also references BitLocker for Windows and DM-Crypt for Linux, but BitLocker is mentioned first. There are no explicit Linux shell or scripting examples, and PowerShell (a Windows-centric tool) is given equal or greater prominence than CLI, which is more cross-platform. No Linux-specific tools or commands are discussed, and there is no mention of Linux shell scripting or integration patterns.
Recommendations
  • Add explicit Bash shell examples for key operations, especially for users on Linux or macOS.
  • Where PowerShell is referenced, clarify that Azure CLI commands work natively on Linux/macOS and highlight their parity.
  • When mentioning encryption technologies (e.g., BitLocker, DM-Crypt), present Linux options first or equally.
  • Include troubleshooting or scripting tips for Linux environments, such as using Bash scripts for automation.
  • Review output formatting and ensure CLI examples are as detailed as PowerShell, including sample outputs.
  • Add a section or note on cross-platform compatibility, emphasizing that all steps can be performed on Linux, macOS, and Windows.
GitHub Create Pull Request
Backup Manage and monitor SQL Server DBs on an Azure VM .../articles/backup/manage-monitor-sql-database-backup.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently refers to 'SQL Server databases running on Azure VMs' without specifying or providing examples for Linux-based SQL Server deployments. All screenshots and UI references imply Windows environments, and there are no command-line or automation examples for Linux (e.g., bash, systemd, Linux file paths). While the Azure CLI and REST API are mentioned, no Linux-specific guidance or parity is provided. The documentation implicitly assumes SQL Server on Windows, which may exclude or confuse users running SQL Server on Linux VMs.
Recommendations
  • Explicitly state whether the guidance applies to both Windows and Linux SQL Server deployments, or clarify any limitations.
  • Add examples and screenshots for managing SQL Server on Linux VMs, including differences in portal experience, backup agent installation, and troubleshooting.
  • Provide Linux-specific command-line instructions (e.g., bash scripts, systemctl commands) for backup management and monitoring.
  • Reference Linux tools and patterns (such as log locations, service management, and file permissions) where relevant.
  • Ensure parity in REST API and Azure CLI examples by including Linux VM scenarios and any required configuration differences.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure CLI ...cles/backup/quick-backup-azure-files-vault-tier-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page shows mild Windows bias. While the main instructions use Azure CLI (cross-platform), references to Azure PowerShell and the Azure portal are given before REST API alternatives. The CLI example output includes a Windows-style path (C:\Users\...), which may confuse Linux users. There is no explicit Linux example or mention of Linux-specific considerations, and PowerShell is referenced as an alternative before REST API or other cross-platform tools.
Recommendations
  • Remove Windows-style paths from CLI example outputs, or provide examples with Linux-style paths (e.g., /home/user/...).
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide Linux-specific usage notes if relevant.
  • When listing alternatives (e.g., PowerShell, portal, REST API), avoid always mentioning Windows-centric tools first; alternate the order or group cross-platform tools together.
  • Add a note or example showing how to run the Azure CLI commands on Linux (e.g., in a local Bash shell or Linux terminal).
  • Ensure that any screenshots, code snippets, or outputs do not assume a Windows environment unless necessary.
GitHub Create Pull Request
Backup Quickstart - Back up a VM with the Azure portal by using Azure Backup ...cs/blob/main/articles/backup/quick-backup-vm-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias. The only explicit OS-specific instructions are in the 'Install the VM agent' section, where Windows instructions (including a direct download link, file path, and executable details) are presented before Linux instructions. Windows-specific tools and patterns (MSI installer, file path, executable properties) are described in detail, while Linux instructions are more generic and less detailed. The initial VM creation link also points to a Windows VM creation guide, with no mention of Linux VM creation.
Recommendations
  • Provide a parallel link to a Linux VM creation guide alongside the Windows VM creation link.
  • In the 'Install the VM agent' section, present Windows and Linux instructions with equal detail and in parallel (side-by-side or in tabs), including explicit Linux commands for installing/updating the agent (e.g., apt, yum, zypper).
  • Include Linux file paths and verification steps (e.g., agent version check via command line) similar to the Windows example.
  • Ensure screenshots and examples are OS-neutral or provide both Windows and Linux variants where relevant.
GitHub Create Pull Request
Backup Troubleshoot SAP HANA databases instance backup errors ...cles/backup/sap-hana-database-instance-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently refers to 'Azure VM' and troubleshooting steps for SAP HANA backup/restore, but does not specify or provide examples for Linux-based Azure VMs, which are the typical platform for SAP HANA. There are no OS-specific commands, but the language and troubleshooting scripts are presented generically, without explicit Linux parity or examples. The documentation does not mention Linux tools, shell commands, or provide guidance tailored to Linux administrators, despite SAP HANA's primary deployment on Linux.
Recommendations
  • Explicitly state that SAP HANA is typically deployed on Linux and clarify that the troubleshooting steps apply to Linux-based Azure VMs.
  • Provide Linux-specific examples, such as shell commands for checking managed identity, mounting disks, or verifying file system types.
  • Reference Linux tools (e.g., lsblk, mount, df, systemctl) where relevant in troubleshooting steps.
  • If scripts are provided, clarify their compatibility with Linux environments and offer Bash or Python alternatives if only PowerShell is referenced.
  • Add a section or appendix with common Linux administrative commands relevant to SAP HANA backup/restore operations.
GitHub Create Pull Request
Backup Azure Resource Manager and Bicep files ...lob/main/articles/backup/backup-rm-template-samples.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page shows evidence of Windows bias by providing a template specifically for deploying a Windows Server VM with backup enabled, while there are no equivalent examples or templates for Linux VMs. The only OS-specific example is for Windows, and Linux scenarios are not mentioned or represented in the sample templates.
Recommendations
  • Add templates and examples for deploying and backing up Linux VMs, ensuring parity with Windows VM backup scenarios.
  • Explicitly mention support for Linux VMs in relevant sections, and provide links to Linux-specific quickstart templates if available.
  • Review all OS-specific instructions and ensure both Windows and Linux are covered equally, including any differences in backup configuration or monitoring.
  • If certain features are Windows-only, clearly state this limitation and provide guidance for Linux users.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Blobs using Azure Backup ...ob/main/articles/backup/blob-backup-configure-quick.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell as a restore method before Azure CLI and REST API, and by providing a dedicated PowerShell example link. There is no explicit mention of Linux-specific tools or workflows, and PowerShell (traditionally Windows-centric) is highlighted as a primary automation method.
Recommendations
  • Ensure that Azure CLI examples are presented alongside or before PowerShell examples, as CLI is cross-platform and widely used on Linux.
  • Explicitly mention Linux compatibility and workflows where appropriate, such as using Azure CLI on Linux systems.
  • Provide bash script examples for common operations, not just PowerShell.
  • Clarify that REST API and Azure CLI methods are fully supported on Linux and macOS, not just Windows.
  • Add a section or note for Linux administrators outlining recommended tools and steps.
GitHub Create Pull Request
Backup Update the existing VM backup policy using CLI ...docs/blob/main/articles/backup/modify-vm-policy-cli.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides CLI instructions for updating a VM backup policy, but file path examples (e.g., C:\temp2\Policy.json) use Windows-style paths exclusively. There are no Linux or macOS path examples, nor any mention of Linux-specific considerations for file handling. This may confuse or exclude users on non-Windows platforms.
Recommendations
  • Include Linux/macOS file path examples (e.g., /tmp/Policy.json) alongside Windows examples.
  • Add notes clarifying that the CLI commands work on all platforms and adjust file paths accordingly.
  • Explicitly mention that the Azure CLI is cross-platform and provide parity in examples for both Windows and Linux/macOS users.
GitHub Create Pull Request
Backup Script Sample - Disable Soft delete for File Share using ARM API .../backup/scripts/disable-soft-delete-for-file-shares.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by using Windows-style file paths (e.g., .\rqbody-disableSoftDelete.json) in command examples and does not provide equivalent Linux/macOS examples (e.g., ./rqbody-disableSoftDelete.json). There is no mention of Linux-specific considerations or cross-platform usage for the armclient tool, nor are alternative Linux tools or shell commands referenced.
Recommendations
  • Provide Linux/macOS command examples alongside Windows examples, especially for file paths and shell usage.
  • Clarify whether armclient is cross-platform and, if so, provide installation and usage instructions for Linux/macOS.
  • Use neutral file path syntax or show both Windows (e.g., .\file.json) and Linux/macOS (e.g., ./file.json) variants in command blocks.
  • Mention any Linux prerequisites or differences in authentication, environment setup, or tool usage.
  • Consider referencing alternative tools or methods that are popular in Linux environments if applicable.
GitHub Create Pull Request
← Previous Page 56 of 65 Next →