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 851-875 of 1604 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/private-endpoints.md ...re-docs/blob/main/articles/backup/private-endpoints.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by providing extensive PowerShell-based instructions and scripts, referencing Windows-specific tools (e.g., MARS agent, DPM server), and using Windows file path conventions. There are no Linux CLI (az), Bash, or cross-platform examples for key operations such as role assignment, private endpoint creation, or DNS management. Windows/PowerShell methods are presented first and sometimes exclusively, with no guidance for Linux administrators.
Recommendations
  • Add equivalent Azure CLI (az) and Bash examples for all PowerShell scripts and commands, especially for role assignment, private endpoint creation, and DNS management.
  • Include instructions for managing permissions, creating resources, and approving endpoints using cross-platform tools (Azure CLI, REST API, ARM templates) with Linux-friendly file paths.
  • Provide guidance for Linux-based backup agents and clarify any platform-specific requirements for MARS/DPM, or suggest alternatives for Linux workloads.
  • Ensure all code samples and scripts are available in both PowerShell and Bash/Azure CLI formats.
  • Explicitly mention platform compatibility for all tools and scripts, and link to Linux-specific documentation where relevant.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-azure-data-box.md .../main/articles/backup/offline-backup-azure-data-box.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows environments. All supported platforms listed are Windows SKUs, and the process centers around the MARS Agent, which is only available for Windows. All examples, prerequisites, and troubleshooting steps use Windows-specific tools (PowerShell, Control Panel, PsExec, registry editing, etc.), with no mention of Linux or cross-platform alternatives. There are no instructions or examples for Linux systems, nor any indication that Linux is supported for this workflow.
Recommendations
  • Clearly state in the prerequisites and support matrix whether Linux is supported or not. If not, explain why and suggest alternatives for Linux users.
  • If Linux support is possible, provide equivalent instructions for Linux environments, including supported distributions, installation steps, and commands (e.g., Bash, Azure CLI).
  • Offer examples using Azure CLI or REST API where possible, as these are cross-platform tools.
  • Avoid assuming the use of Windows-specific tools (e.g., Control Panel, PsExec, registry editing) and provide platform-agnostic alternatives or note their limitations.
  • Include troubleshooting steps relevant to Linux environments if supported.
  • Consider documenting alternative backup workflows for Linux servers, such as using Azure Backup for Linux or other supported agents.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-kubernetes-backup-arm.md ...ob/main/articles/backup/quick-kubernetes-backup-arm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 example for Azure CLI, Bash, or Linux shell environments. PowerShell is a Windows-centric tool, and its exclusive use may hinder Linux users. Additionally, the prerequisites and deployment steps mention PowerShell first and do not provide parity for Linux users.
Recommendations
  • Add Azure CLI and Bash examples for deploying the ARM template, ensuring Linux users have clear guidance.
  • In the prerequisites section, mention both PowerShell and Azure CLI/Bash tools, and provide installation instructions for each.
  • Where PowerShell scripts are shown, provide equivalent CLI/Bash commands side-by-side or in a tabbed interface.
  • Review all steps to ensure Linux and macOS users are equally supported and not required to use Windows-specific tooling.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-azure-files-vault-tier-bicep.md ...es/backup/quick-backup-azure-files-vault-tier-bicep.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by exclusively providing PowerShell deployment instructions, referencing Azure PowerShell modules in the prerequisites, and omitting equivalent Azure CLI or Bash examples for Linux/macOS users. The deployment workflow and next steps prioritize PowerShell, with CLI and REST API options mentioned only later and without example parity.
Recommendations
  • Add Azure CLI and Bash deployment instructions alongside PowerShell, especially in the 'Deploy the template' section.
  • Include Linux/macOS-specific guidance for installing and using Bicep and Azure CLI tools.
  • Ensure that all next steps (tracking jobs, restoring files, managing backups) provide parallel examples for Azure CLI and Bash, not just PowerShell.
  • Reorder or present PowerShell and CLI examples together to avoid implicit prioritization of Windows tools.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-flexible-server-terraform.md ...p/quick-backup-postgresql-flexible-server-terraform.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by mentioning PowerShell as a client for Azure Backup before CLI, and by referencing the Azure PowerShell module in the authentication note. There are no explicit Linux-specific instructions or examples, and the troubleshooting and next steps sections do not mention Linux-specific considerations or tools. While the main workflow uses Terraform (which is cross-platform), the supporting instructions and tool references lean toward Windows-centric tools and patterns.
Recommendations
  • List Azure CLI before PowerShell when mentioning supported clients, or mention both together to avoid order bias.
  • Add explicit notes or examples for Linux/macOS users, such as shell commands for directory creation and file editing.
  • Clarify that Terraform and Azure CLI work cross-platform and provide links to installation guides for Linux/macOS.
  • In the authentication note, mention that Azure CLI is available on Linux/macOS and provide a link to installation instructions.
  • Include troubleshooting tips or links relevant to Linux environments, such as common permission issues or shell differences.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-flexible-server-bicep.md ...ackup/quick-backup-postgresql-flexible-server-bicep.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by exclusively providing PowerShell deployment instructions for the Bicep template, referencing Azure PowerShell modules, and omitting equivalent Azure CLI or Bash examples. The deployment workflow and next steps are centered around PowerShell, which is primarily used on Windows, with no mention of Linux-native tools or cross-platform alternatives.
Recommendations
  • Add Azure CLI deployment instructions for the Bicep template, suitable for Linux and macOS users.
  • Include Bash script examples for template deployment to improve accessibility for non-Windows environments.
  • Reference both Azure PowerShell and Azure CLI modules in prerequisites and next steps, with links to installation guides for each.
  • Clearly indicate that Bicep and Azure CLI are cross-platform, and provide guidance for using these tools on Linux and macOS.
  • Ensure that all code snippets and instructions are presented for both PowerShell and CLI/Bash, or at least provide links to equivalent Linux instructions.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-blob-vaulted-backup-cli.md .../main/articles/backup/quick-blob-vaulted-backup-cli.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page, while focused on Azure CLI, exhibits Windows bias by referencing PowerShell and linking to PowerShell-based instructions before or alongside CLI examples. The 'create a Backup vault' link points to a PowerShell guide, and the 'Next step' section lists Azure PowerShell before Azure CLI. There is no explicit mention of Linux-specific tools or shell environments, and the documentation assumes familiarity with Windows-centric patterns.
Recommendations
  • Provide direct links to Linux/bash instructions for creating a Backup vault, not just PowerShell.
  • Ensure CLI examples are presented before PowerShell examples in all sections.
  • Add notes or sections clarifying how to perform steps in Linux/macOS environments, including any differences in command syntax or prerequisites.
  • Avoid referencing PowerShell in CLI-focused documentation unless strictly necessary, or provide equivalent bash/Linux examples.
  • Review included files to ensure they do not contain Windows-specific instructions or screenshots.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-azure-encrypted-virtual-machines.md ...les/backup/restore-azure-encrypted-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias in several ways: PowerShell is mentioned as the primary method for creating a VM from restored disks, with no equivalent CLI or Linux-native example provided. The OS disk swap operation is linked only to Windows documentation. The Linux-specific restore instructions are brief and lack step-by-step guidance or command examples, while Windows-related actions are referenced first and in more detail.
Recommendations
  • Provide Azure CLI and/or Bash examples for restoring VMs and creating VMs from restored disks, alongside PowerShell examples.
  • Include explicit Linux instructions for operations such as OS disk swap, with links to Linux documentation.
  • Ensure that Linux and Windows procedures are presented with equal detail and prominence, ideally in parallel sections.
  • Mention Linux tools and patterns (e.g., cloud-init, SSH, Bash scripting) where relevant.
  • Add screenshots or code snippets demonstrating Linux workflows, not just Windows/PowerShell.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-bicep-file.md ...lob/main/articles/backup/quick-backup-vm-bicep-file.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. The Bicep template exclusively provisions a Windows VM, with no mention or example of Linux VM deployment or backup. All deployment and cleanup instructions use Azure PowerShell, with no Azure CLI or Bash equivalents provided. The template parameters and allowed values are tailored to Windows OS versions only, and the backup workflow references Windows-centric tools and patterns.
Recommendations
  • Add Linux VM deployment options to the Bicep template, including parameters for popular Linux distributions (e.g., Ubuntu, CentOS).
  • Provide Azure CLI and Bash examples for template deployment and resource cleanup, alongside PowerShell.
  • Include documentation and links for Linux VM backup and restore workflows.
  • Clarify in the introduction that both Windows and Linux VMs can be backed up, and provide parity in examples.
  • Reference Linux-specific documentation and tools where relevant (e.g., SSH instead of RDP, Linux admin username conventions).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-azure-sql-vm-rest-api.md .../main/articles/backup/restore-azure-sql-vm-rest-api.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based SQL Server (e.g., SQLServer2012, msdb, C:\ paths), using Windows-style directory paths in examples, and omitting any mention of Linux-based SQL Server or Linux file system conventions. There are no examples, notes, or guidance for restoring SQL Server databases on Linux VMs, nor are Linux-specific patterns, tools, or directory structures referenced.
Recommendations
  • Add explicit guidance and examples for restoring SQL Server databases running on Linux Azure VMs, including REST API usage and any Linux-specific considerations.
  • Include Linux-style directory paths (e.g., /var/opt/mssql/data) in request body examples for alternate data directory restores.
  • Clarify any differences in restore workflows, permissions, or prerequisites for SQL Server on Linux VMs.
  • Reference Linux tools and commands where relevant, and provide parity in troubleshooting or validation steps.
  • Update terminology to be OS-neutral where possible (e.g., 'SQL Server VM' instead of 'SQLServer2012', avoid hardcoding Windows instance names).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-azure-files-vault-tier-cli.md ...cles/backup/quick-backup-azure-files-vault-tier-cli.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. While the main instructions use Azure CLI (which is cross-platform), references to Windows-centric tools and workflows appear throughout. The example CLI output includes a Windows file path (C:\Users\testuser...), and alternative instructions prioritize Azure PowerShell and the Azure portal, both of which are more commonly used on Windows. There is no explicit Linux example or mention of Linux-specific considerations, and Docker is suggested only for Windows/macOS users, not for Linux.
Recommendations
  • Provide explicit Linux examples, such as showing CLI output from a Bash shell on Linux (e.g., /home/user/...) instead of Windows paths.
  • When mentioning alternative methods, list Azure CLI and REST API first, then PowerShell and portal, to avoid Windows-first ordering.
  • Add notes or examples for running Azure CLI on Linux, including installation and usage tips.
  • Clarify that Azure CLI is fully cross-platform and provide parity in troubleshooting or environment setup for Linux users.
  • Avoid using Windows-specific paths in example outputs unless also providing Linux equivalents.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-flexible-server-cli.md .../backup/quick-backup-postgresql-flexible-server-cli.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias in several ways. It references PowerShell and Windows object patterns before describing CLI/file-based workflows, and mentions PowerShell as the default or primary example for backup policy objects. File path examples use Windows-style backslashes (e.g., .\OSSPolicy.json), and there is no mention of Linux-specific considerations or examples (such as POSIX paths or shell scripting). The workflow assumes familiarity with Windows tools and conventions, with no explicit Linux parity.
Recommendations
  • Provide Linux-specific examples, including POSIX file paths (e.g., ./OSSPolicy.json) and shell scripting equivalents.
  • Clarify that the Azure CLI commands work cross-platform and highlight any differences in file handling or scripting between Windows and Linux.
  • Include a section or callout for Linux/macOS users, noting how to adapt the instructions (e.g., using forward slashes, shell redirection, etc.).
  • Avoid referring to PowerShell objects as the default; instead, present CLI and file-based workflows as the primary cross-platform method.
  • Ensure that all examples and explanations are platform-neutral unless a platform-specific difference is relevant.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-template.md .../blob/main/articles/backup/quick-backup-vm-template.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by focusing almost exclusively on Azure PowerShell for deployment and cleanup steps, providing only PowerShell scripts and cmdlets, and referencing a template that creates a Windows VM. Linux equivalents (Azure CLI, Bash) are mentioned only in passing and without examples. The workflow and instructions assume familiarity with Windows tools and patterns, with no Linux-specific guidance or parity in examples.
Recommendations
  • Provide equivalent Azure CLI (bash) examples for all PowerShell scripts, including deployment and cleanup steps.
  • Explicitly mention and demonstrate how to deploy and back up Linux VMs using ARM templates.
  • Ensure that instructions for pasting code and interacting with the shell are not Windows-centric (e.g., include Linux/Mac copy-paste instructions).
  • Reference and link to Linux-focused quickstarts or tutorials where relevant.
  • Clarify that the template can be customized for Linux VMs and provide a sample template or parameters for Linux VM deployment.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/save-backup-passphrase-securely-in-azure-key-vault.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/save-backup-passphrase-securely-in-azure-key-vault.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows environments, specifically the MARS agent, which is a Windows-only backup tool. All operational examples and screenshots reference Windows tools (MARS console, installation wizard, Set-OBMachineSetting PowerShell cmdlet), and there are no Linux equivalents or instructions for Linux-based backup agents. PowerShell is used extensively for scripting and automation, with no mention of Bash or Linux-native commands. The documentation assumes the use of Windows patterns and tools throughout, and Linux scenarios are not addressed.
Recommendations
  • Clearly state at the beginning that MARS agent is Windows-only, and provide links to equivalent Linux backup solutions (e.g., Azure Backup for Linux VMs).
  • Add a section comparing Windows (MARS) and Linux backup agents, including their passphrase/key management options.
  • For automation, provide Bash/Azure CLI examples where possible, or clarify that PowerShell examples are for Windows only.
  • If Azure Backup for Linux supports Key Vault integration, include parallel instructions and examples for Linux users.
  • Ensure troubleshooting and prerequisites sections mention platform limitations and alternatives for Linux environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-hana-database-instances-restore.md ...articles/backup/sap-hana-database-instances-restore.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing the use of PowerShell and CLI scripts for permission management without providing explicit Linux shell (bash) examples. The workflow and screenshots are oriented around the Azure portal, which is platform-agnostic, but the only command-line references are to PowerShell and CLI, with no mention of Linux-specific commands or tools. There is no guidance for Linux administrators on how to perform equivalent tasks using native Linux tools or shell scripts.
Recommendations
  • Provide explicit bash shell examples for permission management and disk mounting steps, alongside PowerShell and CLI scripts.
  • Clarify that Azure CLI commands can be run on both Windows and Linux, and provide examples for both environments where syntax or prerequisites differ.
  • Include guidance for mounting and managing disks on Linux VMs, such as using 'lsblk', 'mount', and 'fdisk', in addition to any Windows-specific instructions.
  • Add troubleshooting steps and references for common Linux issues encountered during SAP HANA restores.
  • Ensure that any references to scripts or automation include both PowerShell and bash script versions.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-kubernetes-backup-bicep.md .../main/articles/backup/quick-kubernetes-backup-bicep.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively providing Azure PowerShell deployment instructions, referencing PowerShell in prerequisites, and omitting equivalent Azure CLI or Bash examples for Linux/macOS users. The deployment workflow and examples are tailored for Windows environments, with no mention of Linux shell usage or cross-platform alternatives.
Recommendations
  • Add Azure CLI deployment instructions alongside PowerShell, including Bash shell examples for Linux/macOS users.
  • Update the prerequisites section to mention both Azure PowerShell and Azure CLI, with installation links for each.
  • Where shell instructions are given, clarify which platforms are supported and provide parity in example scripts.
  • Consider including a note or table comparing PowerShell and CLI usage for common tasks in the workflow.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-azure-backup-server-vmware.md .../articles/backup/restore-azure-backup-server-vmware.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by focusing exclusively on Windows environments and tools. All examples and procedures are based on the Microsoft Azure Backup Server (MABS) Administrator Console, which is a Windows application. Item-level recovery (ILR) is only available for Windows Server VMs, with no mention of Linux VM support or equivalent recovery options. Registry key configuration for parallel restores uses Windows registry paths, with no Linux alternative provided. There are no Linux-specific instructions, examples, or parity features discussed.
Recommendations
  • Add explicit guidance for restoring individual files from Linux VMs, or clarify limitations if Linux ILR is not supported.
  • Include examples or notes for Linux VM recovery scenarios, such as restoring to Linux-based ESXi hosts or handling Linux guest filesystems.
  • If MABS does not support Linux file-level recovery, suggest alternative approaches or tools for Linux VM users.
  • Document any differences in recovery workflows for Linux vs. Windows VMs, and provide parity where possible.
  • Where registry modifications are required, note that these are Windows-specific and provide Linux equivalents if applicable (e.g., config files, environment variables).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/soft-delete-virtual-machines.md ...b/main/articles/backup/soft-delete-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by providing detailed PowerShell examples and instructions, referencing Windows-centric tools (PowerShell), and omitting equivalent Linux CLI or automation examples. The PowerShell tab is given prominence as the only CLI example, with no mention of Azure CLI, Bash, or Linux-native scripting. This may disadvantage Linux users or those preferring cross-platform tools.
Recommendations
  • Add Azure CLI examples for all operations (delete backup, undelete, resume backup) alongside PowerShell.
  • Include Bash script snippets or instructions for Linux users where applicable.
  • Explicitly mention cross-platform options and clarify that PowerShell Core is available on Linux, if relevant.
  • Reorder or present CLI options (PowerShell, Azure CLI, REST API) in a way that does not prioritize Windows tools.
  • Ensure screenshots and UI instructions are not Windows-specific (e.g., avoid references to Windows-only features in portal screenshots).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/transport-layer-security.md .../blob/main/articles/backup/transport-layer-security.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses exclusively on Windows environments, providing registry-based instructions and references to Windows KB articles. There are no examples, instructions, or guidance for enabling or verifying TLS 1.2 on Linux systems, nor any mention of Linux-specific tools or configuration patterns. All troubleshooting and configuration steps are Windows-centric, and related links are also Windows/.NET focused.
Recommendations
  • Add a section describing how to enable and verify TLS 1.2 on Linux systems, including common distributions (e.g., Ubuntu, CentOS).
  • Provide Linux command-line examples (e.g., using openssl, curl, or configuration files such as /etc/ssl/openssl.cnf) for checking and enforcing TLS 1.2.
  • Mention Linux equivalents to Windows registry and KB updates, such as package updates or configuration changes.
  • Include troubleshooting steps and error messages relevant to Linux backup agents or Azure Backup clients.
  • Reference cross-platform documentation and best practices for TLS configuration, not just Windows/.NET resources.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-ase-backup-support-matrix.md .../main/articles/backup/sap-ase-backup-support-matrix.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows Missing Linux Only Missing Windows Example
Summary
The documentation page is strongly Linux-centric, with explicit support only for SAP ASE databases running on Azure Linux VMs. Windows is listed as unsupported in the topology table, and all examples, scripts, and supported OS versions are Linux-specific (SLES, RHEL). There are no Windows or PowerShell examples, nor any mention of Windows tools, patterns, or support for Windows-based SAP ASE deployments. The Azure CLI/PowerShell row explicitly states that support is not available, reinforcing the lack of Windows parity.
Recommendations
  • Clarify in the introduction that Windows support is not available and provide reasoning if possible.
  • If Windows support is planned, include a roadmap or expected timeline.
  • Add a section comparing Linux and Windows support for SAP ASE on Azure VMs, explaining the rationale for Linux-only support.
  • If feasible, provide guidance or alternatives for users who need to back up SAP ASE databases on Windows VMs (e.g., third-party solutions, manual backup procedures).
  • Ensure that future updates consider parity for Windows users, including examples, scripts, and supported scenarios when/if support becomes available.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sql-support-matrix.md ...e-docs/blob/main/articles/backup/sql-support-matrix.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias: only Windows Server operating systems are supported and listed, with Linux explicitly stated as unsupported. All examples and configuration instructions reference Windows-specific tools (PowerShell, .NET Framework), and there is no mention of Linux equivalents or parity. Backup configuration is only available via the Azure portal or PowerShell, with CLI (which is more cross-platform) unsupported. The documentation repeatedly references Windows patterns and tools, with no Linux guidance or alternatives.
Recommendations
  • Clearly indicate plans or timelines for Linux support, if any.
  • Add a dedicated section for Linux support status and alternatives, including recommended backup strategies for SQL Server on Linux in Azure VMs.
  • Where CLI is unsupported, explain why and provide workarounds or roadmap for CLI parity.
  • If Linux support is planned, provide example commands and configuration steps for Linux environments.
  • Reference cross-platform tools and patterns where possible, and avoid Windows-only terminology unless strictly necessary.
  • Consider including a comparison table for Windows vs. Linux support to clarify limitations and guide users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/selective-disk-backup-restore.md .../main/articles/backup/selective-disk-backup-restore.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides extensive examples for both Azure CLI and PowerShell, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and no Linux shell-specific examples (e.g., Bash scripts) are provided. Windows-specific terminology and tools (e.g., drive C, BitLocker) are mentioned before or more prominently than Linux equivalents. Linux-specific requirements (e.g., lsblk, lsscsi) are referenced only in passing, and there are no Linux command-line walkthroughs or troubleshooting steps. The documentation lacks parity in practical Linux usage examples and troubleshooting.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for scripting disk selection and backup operations.
  • Include troubleshooting steps and error messages specific to Linux environments (e.g., permissions, missing tools).
  • Mention Linux tools and patterns (e.g., using /dev/sdX, root filesystem) alongside or before Windows equivalents where relevant.
  • Provide example workflows for Linux VMs, including installation of required utilities (lsblk, lsscsi) and verification steps.
  • Balance references to Windows and Linux features in limitations, billing, and FAQ sections, ensuring Linux is not treated as an afterthought.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/upgrade-mars-agent.md ...e-docs/blob/main/articles/backup/upgrade-mars-agent.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation exclusively describes upgrading the MARS agent in the context of Windows environments, referencing Remote Desktop, Windows-specific tools (DPM, agent installer wizards), and only providing instructions and screenshots for Windows servers. There are no examples, instructions, or mentions of Linux systems, Linux tools, or cross-platform considerations. The 'Next steps' section further reinforces the Windows focus by linking only to Windows backup instructions.
Recommendations
  • Clarify in the introduction whether the MARS agent is Windows-only or provide equivalent Linux agent upgrade instructions if available.
  • If Linux is supported, add Linux-specific upgrade steps, including command-line examples (e.g., Bash, system package managers), and screenshots from Linux environments.
  • Mention alternative remote connection methods (e.g., SSH) for Linux servers alongside Remote Desktop for Windows.
  • Provide parity in troubleshooting and firewall configuration for Linux systems.
  • Update 'Next steps' to include links to Linux backup documentation if applicable.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-sql-database-azure-vm.md .../main/articles/backup/restore-sql-database-azure-vm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation demonstrates a clear Windows bias. All examples and instructions assume the use of Windows-based SQL Server instances, Windows file paths (e.g., C:\Program Files), and Windows-specific tools (e.g., PsExec, NT AUTHORITY\SYSTEM). There are no examples or guidance for restoring SQL Server on Linux-based Azure VMs, nor any mention of Linux equivalents for the tools and patterns described. The documentation also references SQL Server Management Studio (SSMS), which is a Windows-only tool, and does not mention cross-platform alternatives.
Recommendations
  • Add explicit instructions and examples for restoring SQL Server databases on Linux-based Azure VMs.
  • Include Linux file paths and commands (e.g., /opt/azureworkloadbackup/bin) alongside Windows paths.
  • Provide Linux equivalents for Windows-specific tools (e.g., alternatives to PsExec for privilege escalation, using sudo or setfacl for permissions).
  • Mention cross-platform SQL Server management tools (such as Azure Data Studio) and provide examples using them.
  • Ensure that any JSON configuration steps are shown for both Windows and Linux environments.
  • Where NT AUTHORITY\SYSTEM is referenced, explain the Linux equivalent (e.g., root user) and how to grant permissions.
  • Review all screenshots and examples to ensure Linux parity, or add Linux-specific visuals and walkthroughs.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-sql-backup.md ...-docs/blob/main/articles/backup/tutorial-sql-backup.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific components (such as the AzureBackupWindowsWorkload extension and NT Service accounts), and does not mention or provide guidance for SQL Server running on Linux VMs. All examples, instructions, and screenshots assume a Windows environment, with no parity for Linux-based SQL Server deployments.
Recommendations
  • Explicitly state whether the tutorial applies only to Windows-based SQL Server VMs, or provide equivalent instructions for SQL Server on Linux VMs.
  • Add sections or notes describing how to back up SQL Server databases on Linux VMs, including any differences in required extensions, permissions, or agent installation.
  • Include Linux-specific examples, commands, and screenshots where applicable (e.g., using bash, systemd service accounts, or Linux file paths).
  • Clarify any limitations or unsupported scenarios for Linux-based SQL Server in Azure Backup, and link to relevant documentation if available.
  • Ensure that prerequisites and troubleshooting steps cover both Windows and Linux environments.
GitHub Create Pull Request
← Previous Page 35 of 65 Next →