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 1251-1275 of 1604 flagged pages
Backup Support matrix for Azure VM backups ...lob/main/articles/backup/backup-support-matrix-iaas.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows scenarios, tools, and agent support (MARS, DPM, MABS) are described in detail and often appear before Linux equivalents. Restore instructions frequently mention PowerShell and Windows-specific features, while Linux support is more limited and often described as 'not supported' for several backup/restore methods. Linux examples are sparse, and advanced backup scenarios (e.g., file-level restore, agent-based backups, DPM/MABS integration) are unavailable for Linux VMs. Windows-centric terminology and tooling (PowerShell, Storage Spaces, ReFS, BitLocker, etc.) are referenced without Linux alternatives.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside or before PowerShell instructions for restore and backup operations.
  • Expand documentation of Linux backup scenarios, including file-level restore, agent-based backups, and integration with backup servers if/when supported.
  • Clearly indicate parity gaps and offer Linux workarounds or alternatives where possible.
  • Add more Linux-specific troubleshooting and configuration guidance, especially for advanced scenarios (e.g., encrypted disks, custom scripts, restore to specific configurations).
  • Avoid listing Windows-only tools (MARS, DPM, MABS) first or exclusively; clarify their OS limitations upfront.
  • Highlight Linux support and limitations in summary tables and callouts, not just in separate sections.
GitHub Create Pull Request
Backup Automation in Azure Backup support matrix ...blob/main/articles/backup/backup-support-automation.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation consistently lists PowerShell as a primary automation method for Azure Backup tasks, often before CLI and other cross-platform tools. PowerShell is a Windows-centric tool, and its prominence may signal a Windows bias. Many example links are PowerShell-focused, and the term 'Supported' is frequently used for PowerShell, sometimes with more detailed references than for CLI. While Azure CLI is also supported and referenced, PowerShell is often listed first, and there is no explicit mention of Linux/macOS-specific considerations or parity. REST API, ARM, Bicep, and Terraform are included, but the documentation does not clarify platform differences or provide guidance for Linux/macOS users where PowerShell is referenced.
Recommendations
  • Alternate the order of PowerShell and CLI in tables and examples, or list CLI first to avoid implicit prioritization of Windows tools.
  • Explicitly state that Azure CLI is cross-platform and provide links to Linux/macOS installation and usage guides.
  • Where PowerShell is referenced, add notes or links for Linux/macOS users, such as using PowerShell Core or alternatives.
  • Ensure example links for CLI are as comprehensive and detailed as those for PowerShell.
  • Add a section clarifying platform support and any limitations for Linux/macOS users.
  • Consider including Bash or shell script examples for common automation scenarios.
GitHub Create Pull Request
Backup Encrypt backup data in a Backup vault by using customer-managed keys ...backup/encryption-at-rest-with-cmk-for-backup-vault.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions and code examples for Azure Portal, PowerShell, and Azure CLI. However, PowerShell is featured prominently and often before CLI, and all PowerShell examples assume a Windows environment. There are no explicit Linux/macOS shell (e.g., Bash) examples or notes on cross-platform differences, and the documentation does not mention or address potential issues Linux/macOS users might encounter with PowerShell commands. While Azure CLI is cross-platform, the documentation does not clarify this or provide Linux/macOS-specific guidance, which may cause friction for non-Windows users.
Recommendations
  • Clearly indicate that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Where PowerShell is used, add notes or links for installing and using PowerShell Core on Linux/macOS, or clarify if commands are Windows-only.
  • Present CLI examples before PowerShell to avoid implicit Windows-first bias.
  • Add explicit Bash shell examples or at least validate that CLI commands work as shown in Linux/macOS terminals.
  • Include troubleshooting notes for common cross-platform issues (e.g., differences in quoting, environment variables, or authentication).
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias, primarily through repeated references to PowerShell for automation and management tasks, and the use of Windows-centric tooling (e.g., MARS agent, DPM/MABS) for hybrid backups. PowerShell is mentioned as a primary automation channel before CLI and other cross-platform options. Windows tools and patterns (MARS agent, DPM/MABS) are described in detail, while Linux/macOS equivalents or considerations are not addressed. Examples and guidance do not include Linux-specific instructions or parity for non-Windows environments.
Recommendations
  • Provide Linux/macOS-specific examples and instructions alongside PowerShell, especially for automation and scripting (e.g., Bash, Azure CLI).
  • Explicitly mention cross-platform support for Azure CLI and REST API, and clarify any differences in capabilities or usage between platforms.
  • Include guidance for Linux-based workloads and backup agents, such as Azure Backup Server for Linux or native Linux backup solutions.
  • Balance the order of presentation so that cross-platform tools (CLI, REST API) are mentioned before or alongside PowerShell.
  • Add sections or notes addressing Linux/macOS administrator concerns, such as agent installation, backup/restore procedures, and security features.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page for Azure Backup Server (MABS) V3 UR1 protection matrix demonstrates a notable Windows bias. Windows workloads and tools are described in detail, with Windows-centric technologies (NTFS, VSS, Exchange, SharePoint, etc.) dominating the protection matrix. Linux support is relegated to a separate section, with only basic VM-level backup described and no mention of file-level or application-level backup for Linux. Windows-specific tools and patterns (NTFS, VSS, Windows Management Framework, domain authentication, etc.) are referenced throughout, while Linux equivalents are missing or not discussed. Recovery options for Linux VMs are limited compared to Windows, and examples or guidance for Linux users are sparse.
Recommendations
  • Provide Linux-specific backup and recovery examples, including file-level and application-level scenarios.
  • Discuss Linux filesystem support (e.g., ext4, xfs) and snapshot mechanisms, analogous to NTFS/VSS for Windows.
  • Clarify agent installation and authentication procedures for Linux systems, including domain/workgroup scenarios.
  • List Linux workloads and applications that can be protected, similar to the detailed Windows workload matrix.
  • Include parity in recovery options (e.g., item-level recovery for Linux files/folders if supported, or explain limitations).
  • Reference Linux tools and patterns where relevant (e.g., LVM snapshots, Linux backup agents).
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-14 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 paths (C:\temp2\Policy.json) and does not mention or show Linux/macOS equivalents. There are no references to Linux/macOS file system conventions or alternative examples, which may cause confusion or friction for non-Windows users.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/user/Policy.json) alongside Windows examples.
  • Explicitly state that the Azure CLI commands work cross-platform and that file paths should be adjusted for the user's OS.
  • Add a note or table showing path syntax differences between Windows and Linux/macOS.
  • Consider showing Linux/macOS examples first or in parallel to Windows examples.
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-14 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 exhibits a notable Windows bias. Most automation and scripting examples are provided exclusively in PowerShell, and references to Windows-specific tools (such as MARS agent, DPM server, and domain controller DNS Manager) are prevalent. Instructions for role assignment, DNS configuration, and private endpoint creation use PowerShell scripts and commands, with no equivalent Bash, Azure CLI, or Linux/macOS guidance. The Cloud Shell example defaults to PowerShell, and file paths use Windows conventions. Linux/macOS users are left to adapt these steps on their own, creating friction and potential confusion.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell scripts and commands, especially for role assignment, private endpoint creation, and DNS management.
  • Include instructions and screenshots for DNS configuration using Linux-based DNS servers (e.g., BIND) and macOS host files.
  • Reference cross-platform tools (such as Azure CLI) before or alongside Windows-specific tools.
  • Clarify that Cloud Shell supports Bash and show how to use it for relevant steps.
  • Use platform-neutral file path conventions or provide both Windows and Unix-style examples.
  • Mention and link to Linux/macOS agent installation and configuration guides where relevant (e.g., for MARS agent alternatives).
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-14 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 exhibits a notable Windows bias. The deployment instructions exclusively use Azure PowerShell, with no Azure CLI or Bash examples provided. The prerequisites specifically call out installing the Azure PowerShell module, omitting mention of Azure CLI or cross-platform alternatives. The deployment steps and next steps prioritize PowerShell and Windows-centric workflows, with Linux/macOS options mentioned only as secondary links and not in the main walkthrough.
Recommendations
  • Add Azure CLI and Bash examples for deployment steps, showing parity with PowerShell.
  • Update prerequisites to mention both Azure PowerShell and Azure CLI, clarifying that either can be used.
  • Present cross-platform instructions first or side-by-side, rather than PowerShell-only.
  • Ensure all critical workflows (deploy, track, restore) have CLI/Bash examples and links.
  • Explicitly state that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
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-14 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. PowerShell scripts are referenced multiple times as the primary method for granting privileges to database users, both in the prerequisites and during the backup configuration flow. While alternatives like PG admin or PSQL are mentioned, they are listed after PowerShell and lack detailed instructions or examples. There are no explicit Linux/macOS command examples, and the documentation assumes familiarity with PowerShell, which is native to Windows environments.
Recommendations
  • Provide step-by-step examples for granting database privileges using Linux/macOS tools such as psql and pgAdmin, with equivalent SQL commands.
  • List Linux/macOS methods before or alongside PowerShell, ensuring parity in instructions and visibility.
  • Clarify that PowerShell is not required and that all steps can be completed using platform-agnostic tools.
  • Include screenshots or terminal output from Linux/macOS environments where relevant.
  • Explicitly state cross-platform compatibility for all scripts and commands.
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-14 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 Azure PowerShell deployment examples and instructions, with no equivalent Azure CLI or Bash examples for Linux/macOS users. The 'Deploy the template' section and subsequent 'Next steps' primarily reference PowerShell, and PowerShell is presented before other cross-platform tools. This may create friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for deploying the ARM template, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Present both PowerShell and CLI/Bash examples side-by-side or in tabs, ensuring Linux/macOS users have clear, first-class instructions.
  • In the 'Next steps' section, list Azure CLI and REST API options before or alongside PowerShell, not after.
  • Explicitly state that the deployment can be performed from any OS using Azure CLI, and provide links to relevant CLI documentation.
GitHub Create Pull Request
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Server with an Azure Resource Manager template .../backup/quick-backup-postgresql-flexible-server-arm.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only PowerShell examples for deploying the ARM template and restoring backups, with no mention of Azure CLI or Bash equivalents. The prerequisites and next steps also reference PowerShell exclusively, creating friction for Linux/macOS users who typically use Azure CLI or Bash.
Recommendations
  • Add Azure CLI and Bash examples for deploying the ARM template, alongside PowerShell.
  • Mention cross-platform tools (e.g., Azure CLI) in prerequisites and next steps.
  • Clarify that PowerShell is available on Linux/macOS, but provide native Bash/CLI instructions for parity.
  • Reorder examples so that CLI/Bash instructions are presented before or alongside PowerShell.
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-14 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 and behaviors as the default, describes modification workflows using Windows-style file paths (e.g., .\OSSPolicy.json), and discusses PowerShell object manipulation before mentioning CLI/file-based workflows. There are no explicit Linux/macOS examples, and Windows-centric patterns (backslash paths, PowerShell object usage) are presented as defaults, which may confuse or hinder Linux/macOS users.
Recommendations
  • Add explicit Linux/macOS examples, including file path formats (e.g., ./OSSPolicy.json instead of .\OSSPolicy.json).
  • Clarify that PowerShell object manipulation is Windows-specific and provide equivalent Linux/macOS workflows using files and CLI.
  • Avoid referring to PowerShell objects as the default; present CLI/file-based workflows as the primary cross-platform method.
  • Include notes or examples for Linux/macOS users where command syntax or file handling differs.
  • Ensure that all examples use platform-neutral conventions unless platform-specific behavior is being described.
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-14 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 and referencing Windows-specific interaction patterns (e.g., right-click to paste in shell). There are no Azure CLI or Bash examples, and Linux/macOS users are not given guidance for deploying the Bicep template or restoring backups using their native tools.
Recommendations
  • Add Azure CLI and Bash examples for deploying the Bicep template, alongside the PowerShell example.
  • Include instructions for pasting code in Linux/macOS terminals (e.g., Ctrl+Shift+V in most terminals).
  • Reference cross-platform tools (Azure CLI, Bash) equally and provide links to their documentation.
  • Ensure 'Next steps' includes both PowerShell and CLI/Bash restore instructions.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively demonstrates how to back up a Windows virtual machine in Azure with Terraform. All examples, resource creation steps, and references are specific to Windows VMs, with no mention of Linux VM equivalents or how to adapt the process for Linux. The 'Next steps' section also directs users to Windows VM articles, reinforcing the Windows-centric approach.
Recommendations
  • Add parallel instructions and Terraform code samples for creating and backing up a Linux VM (e.g., using azurerm_linux_virtual_machine).
  • Include notes or sections highlighting differences between Windows and Linux VM backup processes in Azure.
  • Provide links to documentation or quickstarts for Linux VM backup with Terraform.
  • Ensure that CLI commands and resource naming are generalized or include both Windows and Linux examples.
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-14 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 PowerShell deployment instructions for the ARM template, with no equivalent Azure CLI or Bash example for Linux/macOS users. The prerequisites and next steps mention PowerShell first, and do not clarify cross-platform alternatives for the main deployment workflow.
Recommendations
  • Add Azure CLI and Bash examples for deploying the ARM template, ensuring Linux/macOS users have clear instructions.
  • Explicitly state that Azure PowerShell is available cross-platform, but also provide CLI alternatives for users who prefer native Linux tools.
  • Alternate the order of PowerShell and CLI references in prerequisites and next steps to avoid Windows-first presentation.
  • Include a note or table summarizing which tools are supported on which OS platforms.
GitHub Create Pull Request
Backup Quickstart - Resource Manager template VM Backup .../blob/main/articles/backup/quick-backup-vm-template.md
Medium Priority View Details →
Scanned: 2026-01-14 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: all deployment examples use Azure PowerShell, with no Azure CLI or Bash equivalents shown. The template specifically deploys a Windows VM, and PowerShell is presented as the primary method for both deployment and cleanup, with only passing mention of Azure CLI, REST API, or portal alternatives. Linux/macOS users are left to infer how to adapt the instructions for their platforms.
Recommendations
  • Provide Azure CLI and Bash examples for template deployment and cleanup, shown alongside PowerShell.
  • Explicitly mention cross-platform compatibility for Azure Cloud Shell (which supports both Bash and PowerShell).
  • Offer a Linux VM template example or clarify how to adapt the template for Linux VMs.
  • Reorder or parallelize instructions so that Windows and Linux/macOS users see relevant examples for their platforms.
  • Link directly to CLI and Bash documentation for each major step, not just as a footnote.
GitHub Create Pull Request
Backup Quickstart - Install Azure Backup extension in an AKS cluster ...main/articles/backup/quick-install-backup-extension.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes installation of the Azure Backup extension in AKS via the Azure Portal, with screenshots and step-by-step instructions. No Linux/macOS-specific instructions, CLI commands, or examples are provided in the main quickstart. The 'Next steps' section mentions Azure CLI and Terraform, but does not link to or show any Linux-native workflows in the quickstart itself. The ordering and focus on GUI-based (portal) instructions is typical of Windows-centric documentation.
Recommendations
  • Add step-by-step instructions for installing the backup extension using Azure CLI, which is cross-platform and commonly used on Linux/macOS.
  • Include example commands for ARM, Bicep, and Terraform directly in the quickstart, not just in 'Next steps'.
  • Add a note clarifying that the portal steps are platform-agnostic, but provide parity by showing CLI workflows.
  • Ensure screenshots or instructions do not assume Windows-only environments (e.g., referencing PowerShell or Windows-specific UI elements).
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-14 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 PowerShell deployment instructions for the Bicep template, with no equivalent Azure CLI or Bash example for Linux/macOS users. The instructions and code snippets assume use of PowerShell, which is primarily associated with Windows environments. The prerequisites and deployment steps mention PowerShell first and do not offer alternative cross-platform guidance.
Recommendations
  • Add Azure CLI and Bash examples for deploying the Bicep template, ensuring Linux/macOS users have clear instructions.
  • Explicitly state that the deployment can be performed using Azure CLI or Bash, and provide links or code snippets for those methods.
  • Reorder or parallelize instructions so that PowerShell and CLI/Bash options are presented together, rather than PowerShell first.
  • Clarify that PowerShell is available cross-platform, but highlight the most common tools for each OS.
GitHub Create Pull Request
Backup Restore encrypted Azure VMs ...les/backup/restore-azure-encrypted-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides detailed steps for restoring encrypted Azure VMs but exhibits Windows bias in several areas. PowerShell is mentioned as the primary method for creating a VM from restored disks, with no equivalent CLI or Linux-specific example. The OS disk swap note links only to Windows documentation. Linux-specific guidance is limited to a brief mention of reinstalling the ADE extension, without step-by-step instructions or command examples. Windows tools and patterns are referenced before Linux equivalents, and Linux users must infer or search for their own procedures.
Recommendations
  • Add Azure CLI and/or Bash examples for creating a VM from restored disks, alongside PowerShell.
  • Provide a link or instructions for swapping the OS disk on Linux VMs, not just Windows.
  • Include step-by-step guidance for reinstalling the ADE extension on Linux, with relevant commands.
  • Ensure parity in troubleshooting and next steps for both Windows and Linux VM restore scenarios.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation displays a Windows bias by focusing exclusively on Windows Server VMs for individual file recovery and referencing Windows-specific tools and registry paths. There are no examples or guidance for Linux VMs, nor are Linux-specific recovery scenarios or tools mentioned. The registry modification instructions are Windows-only, and the documentation does not address Linux or macOS users' needs.
Recommendations
  • Include examples and procedures for restoring individual files from Linux VMs, or explicitly state if this is not supported.
  • Clarify platform limitations (e.g., ILR only for Windows VMs) at the beginning of the article.
  • If possible, provide alternative Linux recovery workflows or recommend third-party tools for Linux VM file-level recovery.
  • Add notes or sections for macOS/Linux administrators regarding recovery options and limitations.
  • When describing registry changes, mention that these steps are Windows-specific and provide equivalent configuration guidance for Linux-based environments if applicable.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on SQL Server running in Azure VMs, which is a Windows-centric workload. All example paths, database names, and directory mappings use Windows conventions (e.g., C:\SQLfiles\Default.ldf), and there are no references to Linux-based SQL Server VMs or examples using Linux file paths. The documentation does not mention or provide guidance for restoring SQL Server databases on Linux VMs, nor does it clarify whether the REST API supports Linux SQL Server instances. Windows patterns and terminology are used exclusively throughout.
Recommendations
  • Explicitly state whether the REST API supports SQL Server on Linux VMs and, if so, provide Linux-specific examples.
  • Include example request bodies and directory mappings using Linux file paths (e.g., /var/opt/mssql/data/Default.ldf).
  • Add a section or note clarifying any differences or limitations when restoring to Linux-based SQL Server VMs.
  • Ensure terminology and instructions are inclusive of both Windows and Linux environments where applicable.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page exhibits a notable Windows bias. It references Windows-specific tools (PsExec, NT AUTHORITY\SYSTEM), Windows filesystem paths (C:\...), and Windows-centric instructions for file permissions and restore operations. There are no examples or guidance for Linux-based Azure VMs running SQL Server, nor are Linux file paths, permissions, or tools mentioned. All examples and screenshots use Windows conventions, and Windows-specific patterns are presented without Linux alternatives.
Recommendations
  • Add explicit instructions and examples for restoring SQL Server databases on Linux-based Azure VMs, including file paths, permissions, and relevant Linux commands.
  • Provide Linux equivalents for Windows tools (e.g., alternatives to PsExec for privilege escalation, using sudo or setfacl for file permissions).
  • Include screenshots and walkthroughs using Linux environments where applicable.
  • Mention any differences or limitations when restoring SQL Server on Linux VMs, and link to relevant documentation.
  • Ensure that examples (T-SQL, file paths, restore procedures) are provided for both Windows and Linux, or clarify platform limitations.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page focuses almost exclusively on Azure Portal workflows and mentions using PowerShell or CLI scripts for permissions, but does not provide any explicit Linux-specific instructions, examples, or screenshots. There is no mention of Linux tools, shell commands, or guidance for Linux users, despite SAP HANA commonly running on Linux. The documentation assumes the use of Azure Portal (which is platform-agnostic) and PowerShell/CLI (which can be cross-platform), but does not clarify Linux compatibility or provide Linux-centric examples.
Recommendations
  • Add explicit Linux shell (bash) command examples for key steps, especially for mounting disks and managing permissions.
  • Clarify whether the Azure CLI and PowerShell instructions are compatible with Linux and macOS, and provide installation/setup guidance if needed.
  • Include screenshots or terminal output from a Linux environment where relevant.
  • Mention Linux-specific considerations for SAP HANA restores, such as filesystem mounting commands (e.g., mount, lsblk) and SAP HANA service management on Linux.
  • Ensure that all scripts and instructions are tested and documented for Linux platforms.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides command-line examples using armclient with Windows-style path separators (e.g., .\rqbody-disableSoftDelete.json) and does not mention or provide examples for Linux/macOS users (e.g., using ./rqbody-disableSoftDelete.json). There is no guidance on running armclient on Linux/macOS, nor alternative instructions for those platforms.
Recommendations
  • Add Linux/macOS command examples using forward slashes (e.g., ./rqbody-disableSoftDelete.json).
  • Clarify armclient installation and usage for Linux/macOS, including any prerequisites or differences.
  • Explicitly state cross-platform compatibility of armclient, or suggest alternative tools if armclient is Windows-only.
  • Include notes or sections addressing platform-specific differences in command syntax and file paths.
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-14 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 an 'Undelete File Share Script' that is a PowerShell script, and does not mention or provide equivalent Linux/macOS CLI examples or scripts. The guidance for undeleting file shares and purging data relies on either the Azure Portal (GUI) or a PowerShell script, with no mention of Azure CLI, Bash, or cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer command-line tools native to their platforms.
Recommendations
  • Provide Azure CLI and Bash examples for undeleting file shares and purging data, alongside PowerShell scripts.
  • Explicitly mention cross-platform alternatives where PowerShell scripts are referenced.
  • Ensure that all automation steps (such as undelete and purge) have both Windows (PowerShell) and Linux/macOS (Azure CLI/Bash) instructions.
  • Add a note clarifying platform compatibility for provided scripts and tools.
GitHub Create Pull Request
← Previous Page 51 of 65 Next →