Backup

755
Total Pages
562
Linux-Friendly Pages
193
Pages with Bias
25.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

520 issues found
Showing 326-350 of 520 flagged pages
Backup Azure Backup support matrix ...ocs/blob/main/articles/backup/backup-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Backup support matrix demonstrates a moderate Windows bias. Windows backup scenarios (using MARS agent, DPM, MABS) are described first and in greater detail, with explicit support and feature tables. Linux support is often described in terms of limitations or exclusions (e.g., MARS agent not supported, direct backup of Linux on-premises not supported), and Linux backup options are generally presented as exceptions or after Windows options. Windows-centric tools (MARS, DPM, MABS) are referenced throughout, with Linux support limited to specific scenarios (mostly VM-level backup via extension or as guest VMs in Hyper-V/VMware). There are few Linux-specific examples or guidance, and the documentation lacks parity in describing Linux backup workflows and features.
Recommendations
  • Provide Linux backup scenarios and workflows with equal prominence and detail as Windows, including step-by-step examples and feature tables.
  • Add explicit guidance for Linux users on alternative backup strategies when direct backup is not supported (e.g., using Azure VM extension, third-party tools, or scripts).
  • Include Linux-specific limitations and workarounds in the main support tables, not just as exclusions.
  • Reference Linux backup tools and patterns where applicable, and avoid framing Linux support only in terms of what is not supported.
  • Consider reordering sections or tables to present Windows and Linux options side by side for easier comparison.
GitHub Create Pull Request
Backup Support matrix for Azure VM backups ...lob/main/articles/backup/backup-support-matrix-iaas.md
Medium Priority View Details →
Scanned: 2026-01-12 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 moderate Windows bias. Windows scenarios, tools, and agents (such as MARS, DPM, and MABS) are described in greater detail and are supported for more backup and restore options. Windows-specific tools (PowerShell, MARS agent) are mentioned as restore methods, while Linux equivalents are absent or marked as unsupported. Windows operating system support is listed first and in more detail, with Linux support relegated to a separate section and with more limitations. Some restore and backup scenarios (file-level restore, agent-based backup with MARS/DPM/MABS) are available only for Windows, with Linux users missing parity or having to rely on custom scripts.
Recommendations
  • Provide Linux CLI (az, bash) examples for restore and backup operations, especially where PowerShell is mentioned.
  • Clarify or expand support for Linux backup agents or provide guidance for agentless alternatives.
  • List Linux operating system support alongside Windows in the main support matrix, not in a separate section.
  • Offer parity for file-level restore and backup frequency options for Linux VMs, or document workarounds.
  • Explicitly mention Linux limitations in each scenario table, not just in a separate section.
  • Where features are Windows-only, provide rationale and suggest alternatives for Linux users.
GitHub Create Pull Request
Backup Guidance and best practices ...s/blob/main/articles/backup/guidance-best-practices.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While it covers Azure Backup concepts broadly, automation and scripting examples (such as auto-retry of failed backup jobs) are presented only with PowerShell, and references to management via PowerShell precede mentions of Azure CLI. There are no explicit Linux/macOS shell (bash) examples, nor are Linux-specific tools or patterns discussed. The MARS agent is described for hybrid backups, but its Windows-centric nature is not clarified, and Linux agent alternatives are not mentioned.
Recommendations
  • Include equivalent Azure CLI and bash examples alongside PowerShell for all automation and scripting scenarios.
  • Explicitly mention Linux/macOS compatibility and provide guidance or links for Linux users where Windows-specific tools (e.g., MARS agent, PowerShell) are referenced.
  • Where videos or walkthroughs use PowerShell, add parallel demonstrations using Azure CLI/bash.
  • Clarify agent support for hybrid backups (e.g., MARS agent is Windows-only) and reference Linux backup options (such as Azure Backup Server, third-party solutions, or native Linux backup agents).
  • Ensure that CLI examples are presented before or alongside PowerShell to avoid Windows-first impression.
GitHub Create Pull Request
Backup Manage Backup vaults ...-docs/blob/main/articles/backup/manage-backup-vault.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page mentions PowerShell as a method for moving Backup vaults, but does not provide equivalent Bash or Linux shell examples, nor does it reference Linux-specific tools or workflows. The CLI is mentioned, but only as a link, and no explicit Linux/macOS command-line examples are shown. The primary workflow described is via the Azure portal, which is cross-platform, but the only script/tool reference is PowerShell, a Windows-centric technology.
Recommendations
  • Provide explicit Azure CLI examples for all operations where PowerShell is referenced, including sample commands for moving Backup vaults.
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS, and show usage in those environments.
  • Where scripts or tools are mentioned, ensure parity by including Bash/Linux shell script snippets alongside PowerShell.
  • Add notes or sections for Linux/macOS users, highlighting any differences or considerations.
GitHub Create Pull Request
Backup MABS (Azure Backup Server) V3 UR1 protection matrix ...kup/microsoft-azure-backup-server-protection-v3-ur1.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for MABS V3 UR1 protection matrix exhibits a notable Windows bias. Windows workloads and tools are described in detail and presented first, with extensive coverage of supported versions, backup scenarios, and recovery options. Linux support is relegated to a single, brief section, with limited detail and only VM-level backup/recovery described. Windows-specific technologies (NTFS, VSS, ReFS, FAT, FAT32) and tools are referenced throughout, while Linux equivalents are absent. There are no Linux-specific backup/recovery examples, nor coverage of file-level or application-level Linux backup. Windows terminology and requirements dominate, and Linux support is only mentioned as a VM guest, with no parity in features or documentation depth.
Recommendations
  • Provide Linux-specific backup and recovery examples, including file-level and application-level scenarios.
  • Expand the Linux section to detail supported distributions, file systems, and backup/recovery limitations.
  • Reference Linux-native technologies (e.g., ext4, LVM snapshots) where relevant, or clarify their support status.
  • Present Windows and Linux workloads in parallel in tables, rather than relegating Linux to a separate, minimal section.
  • Include guidance for Linux users on agent installation, configuration, and troubleshooting.
  • Clearly state feature parity (or lack thereof) between Windows and Linux, and provide workarounds or alternatives for Linux users.
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 a file path example using Windows-style (C:\temp2\Policy.json) and does not mention or show Linux/macOS equivalents. There are no Linux/macOS-specific instructions or examples for saving or referencing the JSON file, which may cause confusion for 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.
  • Explicitly mention that the Azure CLI commands work cross-platform and provide parity in examples.
  • Consider showing both Windows and Linux/macOS commands side-by-side where file paths are referenced.
GitHub Create Pull Request
Backup Backup Classic Alerts using Azure Backup ...b/main/articles/backup/move-to-azure-monitor-alerts.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references PowerShell and the Azure portal as primary management interfaces, with no mention of Linux/macOS CLI usage or examples. The phrase 'portal/PowerShell/the CLI clients' lists PowerShell before CLI, and there are no explicit Bash, Linux, or cross-platform CLI instructions or screenshots. Notification configuration is stated to be portal-only, but troubleshooting and alert visibility are described in terms of PowerShell and portal, with no Linux parity guidance.
Recommendations
  • Add explicit Azure CLI (az) examples for alert management and troubleshooting, including Linux/macOS usage.
  • Clarify whether all features (such as alert deactivation and notification configuration) are available via CLI or REST API, and provide parity instructions if possible.
  • Include screenshots or instructions for Linux/macOS environments where relevant.
  • Avoid listing PowerShell before CLI when describing cross-platform tools; use 'CLI/PowerShell/portal' or similar neutral order.
GitHub Create Pull Request
Backup Create and use private endpoints for Azure Backup ...re-docs/blob/main/articles/backup/private-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Many examples and scripts are provided only in PowerShell, and references to Windows-specific tools (e.g., MARS agent, DPM server) are frequent. The instructions for role creation, DNS management, and private endpoint setup use PowerShell commands and scripts, with no equivalent Bash, Azure CLI, or Linux/macOS examples. Additionally, the Cloud Shell instructions default to PowerShell, and file paths use Windows conventions. There is little to no guidance for Linux/macOS users, making it harder for them to follow the steps or automate processes.
Recommendations
  • Provide Azure CLI and Bash script equivalents for all PowerShell examples and scripts.
  • Include Linux/macOS file path conventions and instructions where file uploads or script executions are described.
  • Add explicit guidance for using the Azure portal and REST API for users who do not use PowerShell.
  • Mention cross-platform alternatives for tools like MARS agent and DPM server, or clarify platform limitations.
  • Reorder examples so that cross-platform or platform-neutral methods (e.g., Azure portal, REST API, Azure CLI) are presented before or alongside Windows/PowerShell methods.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure Bicep ...es/backup/quick-backup-azure-files-vault-tier-bicep.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. The deployment instructions exclusively use Azure PowerShell, with no Azure CLI or Bash examples provided. The prerequisites mention Azure PowerShell and Bicep CLI, but do not reference Azure CLI or Bash, which are more common on Linux/macOS. The step-by-step deployment process is written for PowerShell, and the 'Next steps' section lists PowerShell-based management tasks before CLI or REST alternatives. There are no Linux/macOS-specific instructions or examples, and the use of PowerShell as the default shell in Azure Cloud Shell further reinforces the Windows-centric approach.
Recommendations
  • Add Azure CLI and Bash examples for template deployment, especially in the 'Deploy the template' section.
  • Update prerequisites to mention Azure CLI as an alternative to PowerShell for Linux/macOS users.
  • Provide explicit instructions for running Bicep deployments from Bash/CLI in Azure Cloud Shell.
  • Ensure that management and restore steps include CLI/Bash examples alongside PowerShell.
  • Reorder examples so that CLI/Bash instructions are presented before or alongside PowerShell, not after.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure Resource Manager ...cles/backup/quick-backup-azure-files-vault-tier-arm.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The deployment instructions and code samples exclusively use Azure PowerShell, with no Azure CLI, Bash, or cross-platform examples provided. The 'Next steps' section lists PowerShell-based management tasks before CLI or REST API alternatives, and the only explicit deployment walkthrough is for PowerShell. Linux/macOS users are left to infer how to perform equivalent actions using Azure CLI or other tools.
Recommendations
  • Add explicit Azure CLI and Bash examples for deploying the ARM template, including parameter usage.
  • Present cross-platform instructions first, or side-by-side, rather than PowerShell-only.
  • In 'Next steps', list Azure CLI and REST API options before or alongside PowerShell, to signal parity.
  • Clarify which methods are supported on all platforms and link to relevant documentation for Linux/macOS users.
  • Consider a table or section comparing PowerShell, CLI, and portal deployment methods.
GitHub Create Pull Request
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Servers with a Bicep file ...ackup/quick-backup-postgresql-flexible-server-bicep.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing only PowerShell deployment instructions for the Bicep template, with no mention of Azure CLI or Bash equivalents. The instructions assume use of a Windows shell (right-click to paste), and the 'Next steps' section links exclusively to a PowerShell-based restore guide. There are no Linux/macOS-specific examples or guidance.
Recommendations
  • Add Azure CLI deployment instructions for the Bicep template, including example commands for Linux/macOS users.
  • Clarify that Bicep files can be deployed from any OS and provide Bash or shell examples.
  • Update instructions to use cross-platform terminology (e.g., 'paste into your terminal' instead of 'right-click the shell window').
  • Include links to Linux/macOS restore guides or CLI-based restore documentation in the 'Next steps' section.
GitHub Create Pull Request
Backup Quick start - Back up Azure Database for PostgreSQL server ...cles/backup/quick-backup-postgresql-database-portal.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It repeatedly references PowerShell scripts for key operations (such as granting privileges to database users) and lists PowerShell as the primary method, with Linux alternatives (PG admin or PSQL tool) mentioned only as an afterthought. There are no explicit Linux/macOS command examples, and no Bash or shell script equivalents are provided. This creates friction for Linux/macOS users, who must infer or adapt steps themselves.
Recommendations
  • Provide explicit Linux/macOS command examples using psql or Bash scripts alongside PowerShell instructions.
  • List cross-platform tools (e.g., psql, Azure CLI) before or alongside Windows-specific tools like PowerShell.
  • Include screenshots or walkthroughs for Linux/macOS environments where appropriate.
  • Clarify that all steps can be performed on Linux/macOS and provide references to relevant documentation.
GitHub Create Pull Request
Backup Quickstart - Create a backup policy for Azure Database for PostgreSQL - Flexible Server using Azure CLI .../backup/quick-backup-postgresql-flexible-server-cli.md
Medium Priority View Details →
Scanned: 2026-01-12 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. It references PowerShell objects as the default for backup policy manipulation, describes modification workflows in terms of PowerShell objects first, and uses Windows-style file paths (e.g., .\OSSPolicy.json) in CLI examples. There is no mention of Linux/macOS equivalents for file path syntax or object manipulation, nor are there any explicit Linux/macOS-specific notes or examples. The workflow assumes familiarity with Windows conventions, which may cause confusion or friction for Linux/macOS users.
Recommendations
  • Add explicit Linux/macOS examples for file path syntax (e.g., ./OSSPolicy.json instead of .\OSSPolicy.json).
  • Clarify that PowerShell objects are a Windows-specific concept and provide guidance for Linux/macOS users on how to manipulate JSON files using common tools (e.g., jq, sed, or text editors).
  • Rephrase sections that reference 'default PowerShell object' to be platform-neutral, or provide parallel descriptions for Linux/macOS.
  • Include notes or tips for Linux/macOS users where workflows differ (e.g., file redirection, path separators).
  • Ensure that all CLI examples are tested and presented in a way that works on both Windows and Linux/macOS shells.
GitHub Create Pull Request
Backup Quickstart - Bicep file VM Backup ...lob/main/articles/backup/quick-backup-vm-bicep-file.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All deployment and cleanup instructions use Azure PowerShell, with no Azure CLI or Bash examples provided. The template provisions only Windows VMs, and references to Linux or cross-platform alternatives are absent. Windows tools and patterns (PowerShell, Windows VM images, RDP port) are mentioned exclusively and before any Linux equivalents, which are not present.
Recommendations
  • Add Azure CLI and Bash examples for template deployment and resource cleanup.
  • Include instructions for deploying Linux VMs (e.g., Ubuntu, CentOS) in the Bicep template, or provide a separate Linux VM example.
  • Mention cross-platform tools and workflows explicitly, and clarify which steps are OS-agnostic.
  • Reorder or balance examples so that Linux and Windows are treated equally, or provide parallel instructions for both.
  • Reference Linux-specific documentation where relevant (e.g., SSH access, Linux VM backup).
GitHub Create Pull Request
Backup Quickstart: Back up a virtual machine in Azure with Terraform ...blob/main/articles/backup/quick-backup-vm-terraform.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 exclusively demonstrates backing up an Azure Windows virtual machine, with no mention of Linux VM options or examples. All resource creation and backup steps are tailored to Windows VMs, and the 'Next steps' section further reinforces Windows focus. There are no Linux VM equivalents or guidance for Linux users.
Recommendations
  • Add parallel instructions and Terraform code samples for creating and backing up an Azure Linux VM.
  • Explicitly mention that the process is similar for Linux VMs, or link to Linux-specific documentation.
  • Include Linux VM resource names and backup commands in verification steps.
  • Balance 'Next steps' links to include Linux VM articles.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for an Azure Kubernetes Service (AKS) cluster using Azure Backup via Azure Resource Manager ...ob/main/articles/backup/quick-kubernetes-backup-arm.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based deployment instructions for the ARM template, with no equivalent Azure CLI, Bash, or Linux/macOS shell examples. The prerequisites and deployment steps focus on PowerShell, which is primarily used on Windows, and do not mention or show how to perform the same actions on Linux or macOS platforms. This creates friction for non-Windows users attempting to follow the quickstart.
Recommendations
  • Add Azure CLI and Bash examples for deploying the ARM template, alongside PowerShell.
  • Explicitly mention cross-platform tools and provide instructions for Linux/macOS users.
  • Reorder or parallelize example sections so that Windows and Linux/macOS instructions are equally prominent.
  • Clarify that PowerShell Core is available cross-platform, but provide CLI/Bash alternatives for users who prefer native tools.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for an Azure Kubernetes Service (AKS) cluster using Azure Backup via Azure Bicep .../main/articles/backup/quick-kubernetes-backup-bicep.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing Azure PowerShell deployment instructions, with no equivalent Azure CLI or Bash example for Linux/macOS users. The instructions and deployment script are tailored to PowerShell, which is native to Windows, and the guidance for pasting code references Windows shell behavior. This may create friction for Linux/macOS users who typically use Bash and Azure CLI.
Recommendations
  • Add Azure CLI and Bash deployment instructions alongside the PowerShell example.
  • Explicitly mention that the Bicep CLI and Azure CLI are cross-platform and provide links to installation guides for Linux/macOS.
  • Update shell interaction instructions to be platform-neutral (e.g., describe copy/paste for Bash/Terminal as well as PowerShell).
  • Present CLI/Bash examples before or alongside PowerShell to avoid Windows-first bias.
GitHub Create Pull Request
Backup Restore VMware virtual machines using Azure Backup Server .../articles/backup/restore-azure-backup-server-vmware.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing exclusively on Windows Server VMs for individual file recovery, referencing Windows registry keys for configuration, and omitting Linux/macOS-specific guidance or examples. All examples and instructions are tailored to Windows environments, with no mention of Linux guest VM recovery or cross-platform considerations.
Recommendations
  • Include instructions and examples for restoring individual files from Linux VMs, or clarify limitations if unsupported.
  • Provide parity in documentation by listing supported and unsupported guest OS types for all recovery features.
  • If Linux file-level recovery is not supported, explicitly state this and suggest alternative approaches for Linux users.
  • Add troubleshooting and recovery guidance for Linux/macOS users where applicable.
  • Avoid Windows-centric terminology (e.g., registry keys) without Linux/macOS equivalents or alternatives.
GitHub Create Pull Request
Backup Restore encrypted Azure VMs ...les/backup/restore-azure-encrypted-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. Windows-specific tools (PowerShell) are mentioned as a primary method for VM creation from restored disks, with no equivalent CLI or Linux-native example provided. The OS disk swap example links only to Windows instructions. Linux-specific restore steps are relegated to a separate section, and the main restore workflow does not provide parity for Linux users. Windows terminology and tools appear first or exclusively in critical steps.
Recommendations
  • Provide Azure CLI and/or Bash examples for creating a VM from restored disks, alongside PowerShell instructions.
  • Include explicit instructions and links for swapping OS disks on Linux VMs, not just Windows.
  • Ensure that restore steps and workflows are presented in an OS-agnostic manner, or with parallel instructions for both Windows and Linux.
  • Mention Linux tools and patterns (e.g., cloud-init, Linux VM agent) where relevant.
  • Avoid presenting Windows tools or examples first unless there is a technical reason.
GitHub Create Pull Request
Backup Restore SQL server databases in Azure VMs with REST API .../main/articles/backup/restore-azure-sql-vm-rest-api.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It exclusively covers restoring SQL Server databases in Azure VMs, which are inherently Windows-based workloads. Examples and request bodies use Windows-style paths (e.g., 'C:\SQLfiles\Default.ldf'), and there is no mention of Linux-based SQL Server VMs or guidance for restoring databases on Linux. All resource names and scenarios assume Windows conventions, and no Linux/macOS command-line tools or patterns are referenced.
Recommendations
  • Explicitly state that the instructions apply only to Windows-based SQL Server VMs, or clarify Linux support status.
  • If Azure supports SQL Server on Linux VMs, add equivalent examples and request bodies using Linux-style paths (e.g., '/var/opt/mssql/data').
  • Mention any differences or limitations for Linux SQL Server VM restores, if applicable.
  • Include links or references to Linux-specific documentation if available.
  • Avoid hardcoding Windows paths in generic examples; use placeholders or show both Windows and Linux formats.
GitHub Create Pull Request
Backup Restore SQL Server databases on an Azure VM .../main/articles/backup/restore-sql-database-azure-vm.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. It references Windows-specific tools (e.g., PsExec, NT AUTHORITY\SYSTEM), assumes Windows file paths (C:\Program Files\...), and provides instructions and examples tailored to Windows environments. There are no explicit Linux or macOS examples, nor guidance for restoring SQL Server databases on Linux-based Azure VMs. Windows-centric terminology and steps (such as using SSMS, NTFS permissions, and Windows shell commands) are presented exclusively and/or first, with no Linux alternatives or parity.
Recommendations
  • Add explicit instructions and examples for restoring SQL Server databases on Linux-based Azure VMs, including file paths, permissions, and relevant tools.
  • Provide Linux equivalents for Windows-specific tools (e.g., alternatives to PsExec for privilege escalation, using sudo or setfacl for file permissions).
  • Include examples using Linux shell commands for file operations and database restores.
  • Clarify any differences in the restore process for SQL Server on Linux VMs, including supported features and limitations.
  • Ensure screenshots and UI references are not Windows-specific where possible, or provide Linux UI variants if applicable.
GitHub Create Pull Request
Backup Restore SAP HANA database instances on Azure VMs ...articles/backup/sap-hana-database-instances-restore.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 primarily describes restore workflows using the Azure portal, which is platform-neutral, but it references using PowerShell or CLI scripts for permissions without providing explicit Linux (bash/az CLI) examples. There is no mention of Linux-specific tools, nor are Linux command-line instructions or screenshots shown. The page does not clarify if the process differs for Linux VMs (which are typical for SAP HANA), and Windows terminology (e.g., PowerShell) appears before CLI alternatives.
Recommendations
  • Add explicit bash/az CLI examples for permission assignment and disk mounting, especially for Linux users.
  • Clarify any OS-specific steps for mounting disks and restoring SAP HANA on Linux VMs.
  • Include screenshots or terminal commands relevant to Linux environments.
  • Ensure that references to PowerShell are accompanied by equivalent Linux instructions, not just 'CLI'.
  • State clearly that SAP HANA is typically run on Linux and address any differences in restore procedures.
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 provides command examples using Windows-style paths (e.g., .\rqbody-disableSoftDelete.json) and does not mention or show Linux/macOS equivalents. There are no bash or shell examples, and the use of armclient is not contextualized for non-Windows platforms, potentially causing confusion or friction for Linux/macOS users.
Recommendations
  • Add Linux/macOS command examples using forward slashes (e.g., ./rqbody-disableSoftDelete.json) and appropriate shell syntax.
  • Explicitly state armclient's cross-platform compatibility and provide installation instructions for Linux/macOS.
  • Mention alternative tools or approaches if armclient is not supported on all platforms.
  • Ensure that file path and command syntax are shown for both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh).
GitHub Create Pull Request
Backup Accidental Delete Protection for Azure Files ...b/main/articles/backup/soft-delete-azure-file-share.md
Medium Priority View Details →
Scanned: 2026-01-12 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 a 'Undelete File Share Script' that is a PowerShell script, with no mention of Linux/macOS alternatives or CLI equivalents. All script/tool references are Windows-centric, and there are no examples or guidance for Linux/macOS users. The documentation assumes access to Windows tools and does not provide parity for other platforms.
Recommendations
  • Provide Azure CLI and/or REST API examples for undeleting file shares alongside PowerShell scripts.
  • Explicitly mention cross-platform methods for all operations, including undelete and disabling soft delete.
  • Add notes or sections for Linux/macOS users, detailing how to perform each step without Windows/PowerShell.
  • Ensure all referenced scripts/tools have platform-agnostic or alternative implementations.
GitHub Create Pull Request
Backup Selective Disk Backup and Restore for Azure Virtual Machines .../main/articles/backup/selective-disk-backup-restore.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring selective disk backup and restore, but PowerShell (a Windows-centric tool) is given a dedicated, extensive section with many examples. There are no Bash or Linux shell script examples, and Windows-specific tools and terminology (such as PowerShell cmdlets and references to drive C) are mentioned before or more prominently than Linux equivalents. Linux-specific requirements (like lsblk and lsscsi) are mentioned only as prerequisites, not in example workflows. The FAQ and limitations sections also mention Windows first and provide more detail for Windows scenarios.
Recommendations
  • Add Bash/Linux shell script examples for common operations, especially for modifying protection and restoring disks.
  • Provide parity in example depth: ensure Linux CLI workflows are as detailed as PowerShell ones.
  • Explicitly mention cross-platform compatibility for CLI commands, and clarify any differences in output or usage between Windows and Linux.
  • Include Linux-specific troubleshooting steps and error messages, similar to the PowerShell section.
  • Balance references to Windows and Linux tools in limitations and FAQs, listing Linux first in some cases.
GitHub Create Pull Request
← Previous Page 14 of 21 Next →