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 1351-1375 of 1604 flagged pages
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed PowerShell examples and step-by-step instructions before presenting Azure CLI commands. PowerShell, which is primarily a Windows-centric tool, is given more coverage, with multiple code blocks and explanations. The CLI section is shorter and lacks the depth and context provided in the PowerShell section. There are no Linux-specific shell examples (e.g., bash), and no mention of Linux tools or patterns. The documentation implicitly assumes familiarity with PowerShell, which may disadvantage Linux users.
Recommendations
  • Provide bash-specific examples for Azure CLI commands, including variable usage and output parsing, to help Linux users.
  • Balance the depth of explanation between PowerShell and CLI sections, ensuring CLI instructions are as detailed as PowerShell ones.
  • Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide tips for Linux environments (e.g., jq for JSON parsing, use of environment variables).
  • Add a section or notes on how to perform backup policy management using REST API with curl, which is common on Linux.
  • Avoid assuming PowerShell as the default scripting environment; clarify tool parity and platform support in introductory notes.
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-12 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 method for restoring Azure Blobs, ahead of Azure CLI and REST API. This ordering may suggest a preference for Windows-centric tooling. There are no explicit Linux examples, nor is there mention of Linux-specific tools or shell commands, but Azure CLI is referenced, which is cross-platform.
Recommendations
  • Reorder related content to list Azure CLI before Azure PowerShell, or present both equally to avoid perceived prioritization.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Provide example commands for both Azure PowerShell and Azure CLI in the main tutorial, highlighting cross-platform usage.
  • Add a note clarifying that all operations can be performed from Linux environments using Azure CLI or REST API.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell as a restore method before Azure CLI and REST API, and by referencing PowerShell-specific instructions. There is no explicit mention of Linux-specific tools or parity in command-line examples, and PowerShell (primarily a Windows tool) is highlighted before CLI (cross-platform).
Recommendations
  • List Azure CLI before Azure PowerShell in all instructions and links, as CLI is cross-platform and widely used on Linux.
  • Explicitly mention that Azure CLI instructions are suitable for Linux and macOS users.
  • Provide example commands for both Azure CLI and PowerShell side-by-side where applicable.
  • Add a note clarifying platform compatibility for each tool (e.g., PowerShell is available on Linux, but CLI is preferred for Linux users).
  • Ensure that any referenced scripts or automation examples include both PowerShell and Bash/CLI versions.
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-12 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 steps, without mentioning or providing examples for command-line interfaces such as Azure CLI, Bash, or PowerShell. There is no explicit mention of Windows-specific tools, but the absence of Linux-oriented instructions or parity in examples (e.g., CLI commands) suggests a subtle Windows-first bias, as Azure portal usage is often associated with Windows environments and administrative patterns.
Recommendations
  • Add examples for configuring, restoring, and managing Elastic SAN backup using Azure CLI and/or Bash scripts.
  • Include references to cross-platform tools and workflows, ensuring that Linux users can follow equivalent steps.
  • Explicitly mention that all operations can be performed from any OS, and provide links to documentation for CLI-based management.
  • If PowerShell is supported, provide parity by including Bash or Azure CLI equivalents for each operation.
GitHub Create Pull Request
Backup Troubleshoot Azure Kubernetes Service backup ...backup/azure-kubernetes-service-backup-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-12 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/Azure portal bias by consistently presenting troubleshooting steps and configuration instructions using the Azure portal UI, with no mention of Linux-native or cross-platform alternatives (e.g., bash scripts, Linux desktop tools, or non-portal workflows). All CLI examples use Azure CLI and kubectl, which are cross-platform, but the portal instructions and screenshots are Windows-centric. There are no references to Linux-specific tools, nor are Linux workflows or desktop environments acknowledged. This may disadvantage Linux users who prefer command-line or automation-first approaches.
Recommendations
  • Provide equivalent command-line instructions for all portal-based steps, especially for resource scaling and extension configuration (e.g., using az CLI and kubectl YAML patches).
  • Include explicit notes that Azure CLI and kubectl commands work on Linux, macOS, and Windows, and show example shell commands for Linux environments.
  • Add references or links to Linux desktop tools or automation scripts where relevant.
  • Balance screenshots and UI walkthroughs with CLI and YAML-based workflows to support Linux-first and automation-centric users.
  • Where possible, mention OS-agnostic troubleshooting patterns and avoid assuming use of Windows/Azure portal as the primary interface.
GitHub Create Pull Request
Backup Restore Azure VMs using REST API .../backup/backup-azure-arm-userestapi-restoreazurevms.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. While the REST API examples themselves are platform-neutral, several example responses and request bodies (especially in the Cross Region Restore section) repeatedly use 'osType': 'Windows' and Windows VM names. There are no explicit Linux VM examples, nor is there any mention of restoring Linux VMs or handling Linux-specific scenarios. This may lead Linux users to feel underrepresented or uncertain about Linux support.
Recommendations
  • Include example responses and request bodies that feature Linux VMs (e.g., set 'osType': 'Linux', use Linux VM names).
  • Explicitly state that the REST API supports both Windows and Linux VMs, and note any differences in restore operations or metadata.
  • Add a section or note addressing Linux-specific considerations, such as file system consistency, encryption, or agent requirements.
  • Ensure parity in documentation by alternating or combining Windows and Linux examples throughout, especially in sample JSON and response bodies.
  • Where possible, clarify that all steps and APIs apply equally to Linux VMs, and link to Linux-specific troubleshooting or best practices.
GitHub Create Pull Request
Backup Replace your tape infrastructure by using Azure Backup ...n/articles/backup/backup-azure-backup-cloud-as-tape.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing System Center Data Protection Manager (DPM), a Windows-only tool, and by providing links and examples that focus on Windows backup scenarios (e.g., 'backup-windows-with-mars-agent.md'). There are no Linux-specific examples, tools, or guidance, and Linux backup workflows are not mentioned or illustrated.
Recommendations
  • Include Linux backup examples and workflows, such as using Azure Backup with Linux VMs or workloads.
  • Reference Linux-compatible backup tools (e.g., Azure Backup for Linux, Azure CLI, or third-party solutions) alongside or before Windows tools.
  • Provide parity in screenshots and sample policies for Linux environments.
  • Add links to Linux-specific documentation, such as 'backup-linux-with-azure-agent.md' if available.
  • Clarify that Azure Backup supports both Windows and Linux, and outline any platform-specific considerations.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page contains a reference to the 'default PowerShell object' for PostgreSQL Flexible servers, implying a Windows-centric approach to backup policy creation and scheduling. There are no Linux-specific examples, nor are alternative Linux-native tools or command-line patterns mentioned. The only tooling reference is PowerShell, which is traditionally associated with Windows, and it is mentioned before any cross-platform or Linux alternatives.
Recommendations
  • Replace or supplement references to 'PowerShell object' with cross-platform alternatives, such as Azure CLI or Bash scripts.
  • Provide explicit examples for Linux users, including how to perform the same REST API operations using curl, wget, or Azure CLI.
  • Clarify that PowerShell is available cross-platform, or avoid implying that it is the default or only option.
  • Add a section or note describing how Linux administrators can automate or schedule these backups using cron jobs or other Linux-native tools.
  • Ensure that all examples and tooling references are presented in a platform-neutral way, or provide parallel examples for both Windows and Linux environments.
GitHub Create Pull Request
Backup Back up Azure Disks using Azure Data Protection REST API. ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-disks.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates subtle Windows bias. In the 'Next steps' section, the order of restore instructions lists 'Azure PowerShell' before 'Azure CLI', which is commonly associated with Linux/macOS. Additionally, the only explicit link to permissions assignment refers to a PowerShell-based page (backup-managed-disks-ps.md), with no mention of Linux/CLI alternatives in the main flow. There are no direct Linux/CLI examples or references in the main backup workflow, and no Bash or shell scripting examples are provided.
Recommendations
  • Ensure parity by providing explicit Azure CLI examples alongside PowerShell, especially for permissions assignment and backup configuration.
  • When linking to further instructions, list Azure CLI and PowerShell together or alternate their order to avoid implicit prioritization.
  • Include Bash/shell scripting examples for REST API calls to demonstrate Linux compatibility.
  • Reference both PowerShell and CLI documentation in prerequisite and workflow steps, not just in 'Next steps'.
  • Add a note clarifying that all REST API operations can be performed from any OS, and provide sample commands for both Windows and Linux environments.
GitHub Create Pull Request
Backup Integrate Microsoft Defender's ransomware alerts to protect Azure Backup recovery points ...up-azure-integrate-microsoft-defender-using-logic-apps.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Azure Virtual Machines and Microsoft Defender integration, but all examples, terminology, and workflows implicitly assume Windows environments. There are no references to Linux VMs, Linux-specific backup considerations, or examples of how ransomware detection and backup protection would work for Linux workloads. All instructions, screenshots, and role assignments are generic but do not mention Linux or cross-platform scenarios, which may lead Linux users to feel unsupported or unclear about applicability.
Recommendations
  • Explicitly mention support for Linux VMs in the scope and prerequisites, or clarify limitations if Linux is not supported.
  • Provide examples or workflows that demonstrate how the integration works for Linux-based Azure VMs, including any differences in alerting or backup retention.
  • Include screenshots or step-by-step instructions that reference Linux VM resources where applicable.
  • Discuss any Linux-specific considerations for ransomware detection, backup retention, or logic app deployment.
  • If Microsoft Defender for Cloud or Azure Backup features differ for Linux, document those differences and provide guidance for Linux administrators.
GitHub Create Pull Request
Backup Supported VM SKUs for Azure Policy .../articles/backup/backup-azure-policy-supported-skus.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Windows Heavy
Summary
The documentation page lists supported VM SKUs for Azure Backup policies, and the table of supported images is heavily weighted toward Windows-based SKUs. Windows SKUs are listed first and in much greater detail, with many variants and specialized options, while Linux distributions are listed later and with less granularity. There are no examples or guidance specific to Linux backup scenarios, and the documentation does not mention Linux-specific considerations or tools.
Recommendations
  • Provide equal detail for Linux SKUs, including variants and specialized options (e.g., server core, containers, BYOS, etc.) where applicable.
  • Add Linux-specific notes or examples, such as considerations for backup on different Linux distributions, or guidance for custom images.
  • Clarify any differences in backup features or limitations between Windows and Linux VMs.
  • Consider listing Linux SKUs first or interleaving them with Windows SKUs to avoid perceived prioritization.
  • Include links to Linux backup documentation or troubleshooting guides.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on managing SQL Server databases in Azure VMs using Azure CLI, but all examples and terminology assume a Windows environment (SQL Server, Windows-style resource/container naming, no mention of Linux SQL Server or cross-platform differences). There are no references to Linux-based SQL Server VMs, nor any examples or notes for Linux-specific considerations, despite SQL Server being supported on Linux. The documentation implicitly assumes the reader is using Windows VMs.
Recommendations
  • Add explicit notes clarifying that SQL Server on Linux VMs is supported and highlight any differences in backup/restore operations or prerequisites.
  • Provide example commands and outputs for Linux-based SQL Server VMs, including any differences in resource/container naming conventions or required permissions.
  • Include troubleshooting or FAQ sections for common Linux-specific issues (e.g., permissions, file system paths, service management).
  • Where relevant, mention OS-specific requirements for Azure Backup agent installation/configuration on Linux SQL Server VMs.
  • Ensure terminology and instructions are inclusive of both Windows and Linux SQL Server deployments.
GitHub Create Pull Request
Backup Back Up an Azure Virtual Machine with Azure Extended Zones Portal ...ain/articles/backup/backup-azure-vms-extended-zones.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page generally uses the Azure Portal UI for backup configuration, which is cross-platform. However, in the 'Install the VM agent' section, instructions for Windows appear first, with explicit download links and file paths, while Linux instructions are less detailed and refer users to distribution repositories. The Windows agent installation is described with more step-by-step guidance and tool references (MSI installer, file paths), whereas the Linux section is more generic and lacks equivalent detail or troubleshooting steps.
Recommendations
  • Present Linux and Windows instructions in parallel, with equal detail and troubleshooting guidance.
  • Include explicit Linux agent installation commands (e.g., apt, yum, zypper) and verification steps, similar to the Windows example.
  • Provide direct links to documentation for both Windows and Linux agent installation and updates.
  • Avoid listing Windows instructions before Linux; consider using tabs or side-by-side formatting.
  • Mention Linux-specific considerations (e.g., SELinux, systemd service status) where relevant.
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-12 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 consistently focusing on Azure Virtual Machines (VMs) as the primary backup and restore example, with references to SQL and SAP HANA in Azure VMs, which are commonly Windows workloads. There is a lack of explicit Linux VM examples, Linux-specific backup/restore scenarios, or mention of Linux tools/commands. The documentation does not provide parity for Linux users, as it omits guidance for Linux VM backup/restore or any Linux-specific considerations, and always uses VM examples generically without clarifying Windows vs. Linux applicability.
Recommendations
  • Add explicit examples and instructions for backing up and restoring Linux VMs, including screenshots and step-by-step guidance.
  • Clarify whether the procedures for Azure VMs apply equally to both Windows and Linux, and note any differences or prerequisites for Linux workloads.
  • Include references to Linux-specific backup scenarios (e.g., file-level restore, application-consistent backups for Linux workloads).
  • Where SQL in Azure VM is mentioned, also mention open-source database workloads commonly run on Linux (e.g., MySQL, MongoDB) if supported.
  • Ensure that any command-line or automation examples (if present) include both PowerShell and Bash/Azure CLI equivalents.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Windows-centric workloads (such as SQL in Azure VM, SAP HANA in Azure VM, System Center Data Protection Manager, Azure Backup Agent (MARS), and Azure Backup Server (MABS)) are listed before Linux workloads or Linux-native equivalents. Windows backup tools (MARS, MABS, DPM) are mentioned explicitly, while Linux backup agents or tools are not referenced. There are no explicit Linux examples, and the documentation does not clarify support for Linux VMs or Linux-specific backup scenarios.
Recommendations
  • Explicitly mention Linux VM backup support and provide parity in listing Linux workloads alongside Windows workloads.
  • Include references to Linux-native backup agents or tools if available, or clarify that Azure Backup supports Linux VMs.
  • Provide examples or documentation links for Linux backup scenarios, such as restoring or backing up Linux VMs.
  • Avoid listing Windows workloads and tools before Linux equivalents; use neutral or alphabetical ordering.
  • Clarify any differences or limitations for Linux workloads in the support matrix.
GitHub Create Pull Request
Backup Encryption in Azure Backup ...re-docs/blob/main/articles/backup/backup-encryption.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by mentioning BitLocker (a Windows encryption tool) before DM-Crypt (the Linux equivalent) in the context of Azure Disk Encryption for VM backups. The explanation of in-guest encryption lists BitLocker for Windows VMs first, and DM-Crypt for Linux VMs second. Additionally, the section on TDE-enabled database backup restoration refers only to SQL Server (a Microsoft/Windows-centric product) without mentioning Linux-based database restoration scenarios or tools.
Recommendations
  • Present Linux and Windows tools in parallel, or alternate the order to avoid consistently listing Windows tools first.
  • Include explicit examples or references for Linux-based backup and restoration processes, such as restoring TDE-enabled databases on Linux SQL Server instances.
  • Expand documentation to mention Linux-native tools and patterns where relevant, ensuring parity in guidance for both platforms.
  • Add links or references to DM-Crypt documentation and Linux database backup/restore procedures, similar to those provided for BitLocker and SQL Server.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation is largely cross-platform, focusing on Azure CLI commands, which are available on both Windows and Linux. However, there are subtle signs of Windows bias: (1) Variable assignment examples use PowerShell syntax (e.g., $DiskId = ...), which is not valid in Bash or other Linux shells; (2) The 'Next steps' section lists 'Azure portal', 'Azure PowerShell', and 'Azure CLI' in that order, putting PowerShell before CLI, which can imply a Windows-first mindset. There are no Linux-specific examples or notes, and the documentation does not explicitly show Bash-compatible variable usage or mention Linux shell environments.
Recommendations
  • Provide variable assignment examples in both PowerShell and Bash syntax, or use Bash syntax by default for cross-platform parity (e.g., DiskId="..." instead of $DiskId = ...).
  • Add a note clarifying that Azure CLI commands work identically on Windows, Linux, and macOS, and provide shell-agnostic examples where possible.
  • In the 'Next steps' section, list Azure CLI before PowerShell, or group them together without implying an order of preference.
  • Explicitly mention that the instructions are valid for both Windows and Linux, and consider adding a short section or callout for Linux/macOS users if there are any environment-specific considerations.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by providing a template specifically for deploying a Windows Server VM with backup enabled, while lacking equivalent examples for Linux VMs. There are no Linux-specific backup scenarios or templates mentioned, and Windows is the only OS highlighted in the VM deployment section. No PowerShell or Windows-only tools are referenced directly, but the absence of Linux parity in examples is notable.
Recommendations
  • Add templates and examples for deploying and backing up Linux VMs (e.g., Ubuntu, CentOS) with Recovery Services vaults.
  • Include documentation or links for Linux-specific backup scenarios, such as backing up Linux workloads or configuring backup policies for Linux VMs.
  • Ensure that examples for VM backup and deployment cover both Windows and Linux operating systems equally.
  • Explicitly mention cross-platform compatibility where applicable, and provide guidance for Linux administrators alongside Windows instructions.
GitHub Create Pull Request
Backup Manage Azure Files backups with the Azure CLI ...ocs/blob/main/articles/backup/manage-afs-backup-cli.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally cross-platform, focusing on Azure CLI commands that work on both Windows and Linux. However, there is evidence of Windows bias: (1) The output example for creating a backup policy includes a Windows file path (C:\Users\testuser\Downloads\CLIForAFS\azure-cli>), which is unnecessary and may confuse Linux users. (2) The instructions for exporting policies use the '>' operator, which works on both platforms, but the output example is Windows-specific. (3) No Linux-specific shell examples (e.g., bash, file paths, or environment setup) are provided, and Windows-centric patterns (e.g., file locations) appear first or exclusively.
Recommendations
  • Remove or supplement Windows-specific output examples with Linux equivalents (e.g., show both C:\... and ~/... paths).
  • Explicitly mention that all CLI commands work on both Windows and Linux, and provide notes about any platform-specific differences.
  • Include Linux shell examples (e.g., using bash, showing output redirection with '>', and file paths like ~/vaultdemopol.json).
  • Avoid referencing Windows file paths or environments unless also providing Linux alternatives.
  • Add a short section on preparing the environment for Linux users, if relevant.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on managing and monitoring SQL Server databases on Azure VMs, implicitly assuming a Windows environment. There are no examples, instructions, or references for Linux-based SQL Server VMs, nor any mention of Linux-specific tools, commands, or UI differences. All screenshots and workflows are generic to the Azure portal, but the absence of Linux parity is notable given SQL Server's support on Linux.
Recommendations
  • Explicitly state whether the instructions apply to both Windows and Linux SQL Server VMs, or clarify any differences.
  • Add examples or notes for managing SQL Server on Linux VMs, including any differences in backup agent installation, extension management, or troubleshooting.
  • Include references to Linux-specific documentation or CLI commands where applicable.
  • If certain features are Windows-only, clearly highlight this and provide Linux alternatives or workarounds.
  • Add screenshots or walkthroughs for Linux SQL Server VM scenarios to ensure parity.
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-12 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 conventions exclusively. There are no Linux/macOS path examples or notes on cross-platform usage, which may confuse or exclude non-Windows 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.
  • Where possible, use platform-neutral examples or show both Windows and Linux/macOS variants for commands involving file paths.
  • Explicitly mention that Azure CLI is cross-platform and works on Windows, Linux, and macOS.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias primarily in the 'Install the VM agent' section, where Windows instructions are listed before Linux instructions and provide more detail (including download links, file paths, and verification steps). The Linux instructions are less detailed and lack direct package commands or verification steps. Additionally, the initial VM creation link points to a Windows VM creation guide, with no mention of a Linux equivalent.
Recommendations
  • Provide Linux VM creation instructions or link to the Linux VM creation quickstart alongside the Windows link.
  • In the 'Install the VM agent' section, present Linux and Windows instructions with equal detail, including explicit package installation commands (e.g., apt, yum) and verification steps for Linux.
  • Alternate the order of Windows and Linux instructions, or present them in parallel, to avoid implicit prioritization.
  • Include screenshots or examples for Linux where relevant, matching the level of detail given for Windows.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation refers exclusively to 'Azure VM' without specifying or providing examples for Linux-based VMs, which are the typical platform for SAP HANA. There are no Linux-specific troubleshooting steps, commands, or references to Linux tools (such as shell commands or Linux file system management). The guidance and terminology are generic but implicitly Windows-centric by omitting Linux context, despite SAP HANA's primary deployment on Linux.
Recommendations
  • Explicitly mention Linux VM scenarios and clarify that SAP HANA is generally deployed on Linux VMs.
  • Provide Linux-specific troubleshooting steps, including relevant shell commands (e.g., for mounting disks, checking file systems, moving data between volumes).
  • Reference Linux file system types and tools (e.g., ext3, xfs, mount, lsblk, fdisk) in error resolutions where appropriate.
  • Include example commands for assigning roles and permissions using Azure CLI or shell scripts, not just PowerShell or portal instructions.
  • Add notes or sections highlighting differences or additional steps for Linux VMs versus Windows VMs, if any.
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-12 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 toward Windows environments by using Windows-style file paths (e.g., .\rqbody-disableSoftDelete.json) in all command examples and omitting any Linux/macOS equivalents. There are no bash or shell examples, and the documentation does not mention how to run armclient or manage JSON files on Linux systems.
Recommendations
  • Provide Linux/macOS command examples using forward slashes (e.g., ./rqbody-disableSoftDelete.json) and appropriate shell syntax.
  • Clarify that armclient is cross-platform and provide installation and usage instructions for Linux/macOS.
  • Add notes or sections highlighting differences in file path conventions and shell usage between Windows and Linux.
  • Ensure parity in documentation by including both Windows and Linux/macOS examples for all commands and file operations.
GitHub Create Pull Request
Backup Tutorial - Restore a VM with Azure CLI ...ocs/blob/main/articles/backup/tutorial-restore-disk.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows Reference Windows First
Summary
The documentation is largely cross-platform and focused on Azure CLI, which is inherently cross-platform and works on both Windows and Linux. However, there are subtle signs of Windows bias: (1) The only cross-link to alternative tooling is for PowerShell, with no mention of Bash or Linux-native scripting; (2) In the cross-zonal restore section, the link to 'Azure zone pinned VMs' points to a Windows-specific page; (3) There is no explicit mention or example for restoring Windows VMs, but the only alternative tool mentioned is PowerShell, which is most commonly used on Windows. The CLI examples themselves are platform-neutral.
Recommendations
  • Include a cross-link to Bash or Linux shell scripting guides for users who may prefer those over PowerShell.
  • When referencing 'zone pinned VMs', link to both Windows and Linux VM documentation, or to a neutral overview page.
  • Explicitly state that all CLI commands apply equally to both Windows and Linux VMs, and provide examples or notes where behavior may differ.
  • If mentioning PowerShell as an alternative, also mention Bash or other Linux-native automation options for parity.
  • Ensure that any referenced documentation or examples do not default to Windows unless there is a technical reason.
GitHub Create Pull Request
← Previous Page 55 of 65 Next →