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 701-725 of 1604 flagged pages
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by referencing Azure PowerShell and the Azure portal as alternative methods before mentioning Linux-specific options. The CLI example includes a Windows-style command prompt path (C:\Users\...), which may confuse Linux users. There is no explicit Linux example or mention of Linux-specific command-line environments beyond a brief reference to Bash in Azure Cloud Shell.
Recommendations
  • Provide explicit Linux shell examples (e.g., Bash, zsh) and show command execution in a Linux terminal context.
  • Avoid Windows-specific command prompt paths in CLI examples; use generic or Linux-style paths when possible.
  • Mention Linux and macOS as first-class platforms for Azure CLI usage, including installation and environment setup instructions.
  • List alternative methods (CLI, PowerShell, portal) in a neutral order or highlight cross-platform parity.
  • Add troubleshooting or environment notes for common Linux issues (e.g., permissions, package dependencies).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-azure-files-vault-tier-terraform.md ...ackup/quick-backup-azure-files-vault-tier-terraform.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by mentioning Azure PowerShell as an authentication client alongside Azure CLI, even though only Azure CLI is supported for Terraform authentication. In 'Next steps', PowerShell is consistently listed before Azure CLI, and there are no explicit Linux shell (bash) or cross-platform command-line examples. There is also no mention of Linux-specific tools, shell environments, or command syntax, which may leave Linux users without clear guidance.
Recommendations
  • Clarify that Azure CLI is cross-platform and the only supported authentication method for Terraform, and de-emphasize Azure PowerShell in this context.
  • When listing tools or interfaces (e.g., in 'Next steps'), alternate the order or explicitly state parity between PowerShell and CLI, or list CLI first to reflect its cross-platform nature.
  • Include explicit Linux/bash shell command examples where relevant (e.g., directory creation, file editing), or note that the steps are OS-agnostic.
  • Add a note or section confirming that all Terraform commands and Azure CLI steps work identically on Linux, macOS, and Windows.
  • Where PowerShell is referenced, provide equivalent bash or shell commands, or link to documentation that covers Linux usage.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/pre-backup-post-backup-scripts.md ...main/articles/backup/pre-backup-post-backup-scripts.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, referencing Windows-specific paths, tools, and conventions (e.g., 'Drive:', 'cscript', Windows SharePoint Services, and typical Windows folder structures). There are no examples or guidance for Linux systems, and all instructions assume Windows as the operating system.
Recommendations
  • Add explicit guidance and examples for configuring pre- and post-backup scripts on Linux-based protected computers, including typical file paths and permissions.
  • Include Linux shell script examples and mention Linux equivalents for command-line execution (e.g., bash, sh) instead of only referencing 'cscript' and VBScripts.
  • Clarify whether MABS supports Linux agents and scripting, and if so, provide parity in documentation for Linux users.
  • Reference Linux data source naming conventions and provide examples for common Linux applications (e.g., MySQL, Apache).
  • Ensure that permissions and best practices are described for both Windows and Linux environments.
GitHub Create Pull Request
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-09 00:34
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 (such as MARS Agent, DPM server, and domain controller DNS Manager), and omitting equivalent Linux CLI or automation examples. The use of Windows paths (e.g., C:\<filepath>), reliance on PowerShell for role creation and DNS management, and instructions for uploading scripts in the PowerShell Cloud Shell further reinforce this bias. There are no bash/az CLI examples, nor is there guidance for Linux-based DNS management or automation workflows.
Recommendations
  • Add equivalent examples using Azure CLI (az) and bash scripts for all PowerShell instructions, including role creation, private endpoint management, and DNS record updates.
  • Provide guidance for Linux administrators on managing DNS (e.g., using bind, dnsmasq, or systemd-resolved) and scripting DNS entries.
  • Include instructions for uploading and running scripts in the Bash Cloud Shell, not just PowerShell.
  • Reference Linux-compatible tools and workflows for backup agents and DNS management, or clarify cross-platform support where Windows-specific tools are mentioned.
  • Use platform-neutral file paths and terminology, or provide both Windows and Linux examples where file paths/scripts are referenced.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/query-backups-using-azure-resource-graph.md ...les/backup/query-backups-using-azure-resource-graph.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 listing PowerShell as the first automation client for ARG queries, referencing PowerShell before CLI and SDK, and not providing explicit Linux or Bash examples. There is no mention of Linux-specific tools or shell usage, and the automation examples are generic or Windows-centric.
Recommendations
  • List Azure CLI before PowerShell when mentioning automation clients, or present both equally.
  • Provide explicit Bash/Linux shell examples for running ARG queries, including sample commands.
  • Reference Linux-native tools (e.g., Bash, curl, jq) in automation contexts alongside PowerShell.
  • Clarify that all sample queries can be executed from Linux environments using Azure CLI.
  • Add screenshots or instructions for Linux terminal usage where appropriate.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-database-portal.md ...cles/backup/quick-backup-postgresql-database-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 primarily referencing PowerShell scripts for privilege assignment and role management, with only brief mentions of alternatives like PG admin or PSQL. There are no explicit Linux shell or cross-platform CLI examples, and Windows-centric tools (PowerShell, ARM templates) are mentioned first or exclusively in key steps. This may make it less accessible for Linux users or those using non-Windows environments.
Recommendations
  • Provide equivalent Linux shell (bash) and cross-platform CLI examples for privilege assignment and role management, alongside PowerShell.
  • Explicitly mention and document how to use psql and PG admin for all steps where PowerShell is referenced.
  • Ensure that ARM template instructions are platform-neutral and clarify how to run them from Linux/macOS environments.
  • Add screenshots or step-by-step instructions for Linux users where UI or tool usage may differ.
  • Review all prerequisite and configuration steps to ensure Linux parity and avoid assuming a Windows environment.
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-09 00:34
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, referencing Windows-specific shell behaviors (right-click to paste), and omitting equivalent Linux or cross-platform CLI examples. The 'Next steps' section also links only to PowerShell-based restore instructions. There is no mention of Azure CLI, Bash, or Linux-specific workflows, despite Bicep and Azure being cross-platform.
Recommendations
  • Add Azure CLI deployment instructions alongside PowerShell, showing how to deploy the Bicep template from Bash or a Linux shell.
  • Include notes or examples for Linux/macOS users, such as using Ctrl+Shift+V to paste in terminal, or referencing Bash shell conventions.
  • Provide links to restore instructions using Azure CLI or other cross-platform tools, not just PowerShell.
  • Clarify that Bicep and Azure tools are cross-platform and can be used from Windows, Linux, or macOS.
  • Consider reordering or balancing examples so that CLI and PowerShell are presented together, or CLI first, to avoid Windows-first bias.
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-09 00:34
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 primarily by referencing PowerShell objects and patterns before discussing Azure CLI workflows, and by using Windows-style file paths (e.g., .\OSSPolicy.json) in CLI examples. The explanation of policy modification explicitly contrasts PowerShell object usage (Windows-centric) with CLI file-based editing, but does not provide Linux-specific guidance or examples (such as using forward slashes or Linux-native editors). No Linux shell or tool examples are provided, and the file manipulation instructions assume a Windows environment.
Recommendations
  • Include Linux-specific examples for file paths (e.g., ./OSSPolicy.json) and file manipulation commands.
  • Provide guidance for editing JSON files using common Linux tools (e.g., nano, vim, jq) alongside Windows instructions.
  • Clarify that Azure CLI is cross-platform and demonstrate usage in both Windows and Linux environments.
  • Avoid referring to PowerShell objects as the default or primary workflow; instead, present CLI and PowerShell approaches in parallel, with equal detail.
  • Add notes or sections for Linux/macOS users, highlighting any differences in command syntax, file handling, or environment setup.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-flexible-server-arm.md .../backup/quick-backup-postgresql-flexible-server-arm.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 ARM template, referencing Azure PowerShell modules, and omitting equivalent Azure CLI or Bash examples. The 'Next steps' section also directs users to a PowerShell-based restore guide, further reinforcing the preference for Windows tooling and workflows.
Recommendations
  • Add Azure CLI and Bash examples for deploying the ARM template to ensure Linux users have clear, platform-agnostic instructions.
  • Mention both Azure PowerShell and Azure CLI tools in the prerequisites, with installation links for each.
  • Provide parity in the 'Next steps' section by linking to restore instructions using Azure CLI or Bash.
  • Explicitly state that the process can be performed on any OS and clarify tool choices for cross-platform compatibility.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-terraform.md ...blob/main/articles/backup/quick-backup-vm-terraform.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively demonstrates backing up an Azure Windows virtual machine, with no mention or example of Linux VM backup. The language and examples focus solely on Windows, and the 'Next steps' section directs users to Windows VM articles. There is no parity for Linux users, and Linux-specific patterns, tools, or considerations are absent.
Recommendations
  • Add equivalent examples and instructions for backing up an Azure Linux virtual machine using Terraform.
  • Update the checklist and implementation steps to mention both Windows and Linux VM scenarios, or clarify that the process applies to both where appropriate.
  • Provide sample Terraform code and Azure CLI commands for Linux VM backup, including any differences in resource configuration or backup policy.
  • Include links to further reading about Azure Linux VMs and backup strategies in the 'Next steps' section.
  • Review terminology throughout the document to ensure it is inclusive of both Windows and Linux VM users.
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-09 00:34
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 strong Windows bias by exclusively providing Azure PowerShell examples for deploying and managing VM backups with ARM templates. The template referenced is for a Windows VM, and all code samples use PowerShell cmdlets. There are no equivalent Azure CLI or Bash examples, nor any mention of Linux VM deployment or management. Windows tools and patterns are presented first and exclusively, with Linux alternatives only briefly referenced in passing.
Recommendations
  • Add Azure CLI and Bash examples for deploying the ARM template and managing VM backups.
  • Include instructions and template references for Linux VM deployment and backup.
  • Present both Windows and Linux options in parallel, rather than focusing on Windows first.
  • Explicitly mention cross-platform compatibility and provide guidance for users on Linux or macOS.
  • Ensure that cleanup and monitoring steps include CLI/Bash alternatives, not just PowerShell.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-install-backup-extension.md ...main/articles/backup/quick-install-backup-extension.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily describes installation of the Azure Backup extension in AKS using the Azure portal, which is platform-neutral. However, in the 'Next steps' section, Azure PowerShell is listed before Azure CLI, ARM, Bicep, and Terraform, suggesting a Windows-first approach. There are no explicit Linux-specific instructions or examples, nor any mention of Linux-native tools or shell commands. No screenshots or steps reference Linux environments, and there is no parity for Linux users in the main walkthrough.
Recommendations
  • List Azure CLI before Azure PowerShell in the 'Next steps' section to prioritize cross-platform tooling.
  • Add explicit Linux shell (bash) examples for installing and configuring the backup extension, especially for users working outside the Azure portal.
  • Include screenshots or terminal output from Linux environments to demonstrate parity.
  • Mention that both Azure CLI and PowerShell are supported and provide links to installation guides for each on both Windows and Linux.
  • Ensure that any referenced scripts or commands are tested and documented for both Windows and Linux platforms.
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-09 00:34
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 strong Windows bias. All operational examples, screenshots, and instructions assume the SQL Server is running on Windows-based Azure VMs. Windows-specific tools (e.g., PsExec, NT AUTHORITY\SYSTEM shell) are referenced exclusively, and file paths use Windows conventions (C:\, network shares). There are no examples or guidance for restoring SQL Server databases on Linux-based Azure VMs, nor any mention of Linux tools, shell commands, or file system paths. The documentation implicitly assumes the use of Windows and does not address Linux parity.
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 mentioned (e.g., alternatives to PsExec for privilege escalation, guidance for mounting Azure File Shares on Linux).
  • Include screenshots and walkthroughs using Linux environments and SQL Server on Linux.
  • Clarify which steps are Windows-specific and which are applicable to both Windows and Linux, or provide separate sections for each OS.
  • Reference Linux documentation and troubleshooting guides where appropriate.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows Server VMs for individual file recovery, omitting Linux VM support and examples. All instructions and features (such as ILR) are described only for Windows, with no mention of Linux equivalents or alternative procedures. Registry key configuration is also presented in a Windows-centric format, with no Linux alternative or parity discussed.
Recommendations
  • Explicitly state whether individual file recovery is supported for Linux VMs, and if not, clarify the limitation.
  • If Linux VM file-level recovery is possible via other means (e.g., mounting VMDK on a Linux system), provide step-by-step instructions or reference relevant tools.
  • Include examples and screenshots for Linux VM recovery scenarios, or note their absence and suggest workarounds.
  • When describing registry key changes, mention if there are equivalent configuration steps for Linux environments, or clarify that MABS is Windows-only if applicable.
  • Ensure that all features and limitations are documented for both Windows and Linux VMs to provide parity and transparency.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific procedures and tools before Linux equivalents, notably in the disk swap instructions and VM creation steps. PowerShell is mentioned as the primary automation method for creating a VM from restored disks, with no Linux CLI or Azure CLI example provided. The Linux-specific restore instructions are brief and lack step-by-step guidance or code samples, unlike the Windows sections.
Recommendations
  • Provide Azure CLI or Bash examples for creating a VM from restored disks, alongside PowerShell instructions.
  • Include detailed, step-by-step instructions for restoring encrypted Linux VMs, including how to reinstall and reconfigure the ADE extension.
  • Ensure that references to Windows-specific documentation (e.g., OS disk swap) are balanced with Linux equivalents, or provide cross-platform guidance.
  • Present Windows and Linux procedures in parallel, rather than listing Windows steps first or exclusively.
  • Add troubleshooting tips and common errors specific to Linux VM restores.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways. All examples and resource names reference SQL Server (a Windows-centric database), and all file paths in restore examples use Windows-style (C:\) notation. There are no examples or guidance for restoring SQL Server databases on Linux-based Azure VMs, nor any mention of Linux file path conventions or differences in restore procedures for Linux environments. The documentation implicitly assumes the reader is working with Windows VMs and SQL Server on Windows, omitting Linux parity.
Recommendations
  • Add explicit examples and instructions for restoring SQL Server databases on Linux-based Azure VMs, including differences in REST API usage or restore request bodies.
  • Include Linux-style file path examples (e.g., /var/opt/mssql/data) in restore request bodies and clarify when to use Windows vs. Linux paths.
  • Mention any prerequisites or configuration steps unique to SQL Server on Linux (such as service names, directory structures, or permissions).
  • Clarify in the introduction and prerequisites sections whether the guidance applies to both Windows and Linux SQL Server deployments, and provide links to Linux-specific documentation if available.
  • Ensure resource naming and container examples do not exclusively reference Windows conventions or names.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows Missing Linux Only Explicit Windows Exclusion
Summary
The documentation page exhibits a strong Linux bias: backup support is explicitly limited to SAP ASE databases running on Azure Linux VMs, with Windows configurations marked as unsupported. All examples, scripts, and operational instructions are Linux-centric (bash, shell scripts, sudo usage), and there is no mention of Windows tools, PowerShell, or Windows-specific patterns. Azure CLI/PowerShell support is noted as unavailable, further reinforcing the lack of Windows parity.
Recommendations
  • Clearly state the rationale for Linux-only support and whether Windows support is planned.
  • If possible, provide a roadmap or timeline for Windows VM support for SAP ASE backup.
  • Add a dedicated section for Windows users, outlining alternative backup strategies or workarounds.
  • Include explicit guidance for Windows administrators on how to monitor or manage SAP ASE backups if running on unsupported platforms.
  • Ensure future updates consider parity in tooling (e.g., PowerShell, Windows scripts) and operational patterns.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/scripts/set-file-folder-backup-policy.md ...ticles/backup/scripts/set-file-folder-backup-policy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides a PowerShell script for managing backup policies with the MARS agent, which is a Windows-centric tool. There are no examples or guidance for Linux environments, nor are Linux tools or scripting languages mentioned. The instructions and next steps reinforce a Windows-first approach by focusing solely on PowerShell and MARS agent usage.
Recommendations
  • Add equivalent Linux shell script examples (e.g., Bash) for creating or modifying backup policies, if supported.
  • Mention and document Linux-compatible backup tools or agents, such as Azure Backup for Linux or other cross-platform solutions.
  • Provide clear guidance on how Linux administrators can automate backup scheduling and retention, including relevant commands and configuration files.
  • Ensure that introductory and instructional sections reference both Windows and Linux environments, or clarify platform limitations if Linux is not supported.
  • Include a comparison table or section outlining differences and similarities in backup policy management between Windows and Linux.
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-09 00:34
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 equal prominence and detailed coverage. Windows-specific terminology and tools (e.g., drive C, BitLocker) are mentioned before Linux equivalents, and some technical details (such as logical volumes, ADE encryption) are described with a Windows-first approach. There are no Linux shell script examples, and Linux-specific instructions are limited to brief notes about required utilities (lsblk, lsscsi) and package installation. No explicit Linux command-line walkthroughs or parity with PowerShell scripting are provided.
Recommendations
  • Add Linux shell (bash) script examples for common operations, such as configuring selective disk backup and restore using the Azure CLI.
  • Provide explicit Linux-centric instructions and troubleshooting steps, including how to verify disk LUNs and manage logical volumes.
  • Ensure that Linux tools and terminology (e.g., root filesystem, dm-crypt) are mentioned with equal prominence and detail as Windows equivalents.
  • Include Linux-specific screenshots of the Azure portal where relevant, or clarify any UI differences for Linux VMs.
  • Reorder sections or examples so that Windows and Linux instructions are presented in parallel, rather than Windows-first.
  • Expand the FAQ and limitations sections to address common Linux scenarios and issues, not just Windows.
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-09 00:34
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 for managing soft delete of VM backups, referencing Windows-centric tools and modules (Az.RecoveryServices), and omitting equivalent Linux CLI (Azure CLI, Bash) examples. The PowerShell workflow is described in depth, while Linux-native approaches are not mentioned. The structure also places PowerShell instructions before REST API, reinforcing Windows-first patterns.
Recommendations
  • Add equivalent Azure CLI (az backup ...) examples for all PowerShell operations, including deleting, undeleting, and resuming VM backups.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or REST API, and provide step-by-step CLI instructions.
  • Include Bash script snippets for automation on Linux systems.
  • Reorder sections so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell, to avoid Windows-first perception.
  • Clarify in notes or introductory text that PowerShell is not required and that Linux users have full parity via CLI and API.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, providing only Windows-specific instructions (registry edits, KB articles, .NET Framework settings) for enabling TLS 1.2 in Azure Backup. There are no examples or guidance for Linux systems, nor any mention of Linux tools or configuration patterns. All troubleshooting and verification steps are Windows-centric, and references are exclusively to Windows documentation and tools.
Recommendations
  • Add a dedicated section for enabling and verifying TLS 1.2 on Linux systems, including instructions for common distributions (e.g., Ubuntu, CentOS).
  • Provide Linux-specific examples, such as updating OpenSSL or configuring TLS settings in relevant configuration files (e.g., /etc/ssl/openssl.cnf, /etc/apache2/mods-available/ssl.conf).
  • Include troubleshooting steps for Linux environments, such as verifying protocol support with openssl s_client or checking service logs.
  • Reference Linux documentation and tools alongside Windows equivalents, ensuring parity in guidance and resources.
  • Clarify whether Azure Backup supports Linux clients and, if so, provide explicit instructions for those platforms.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Powershell Heavy Windows First
Summary
The documentation is heavily focused on the MARS agent, which is a Windows-only backup solution. All operational examples, screenshots, and automation references are centered around Windows tools (MARS console, PowerShell cmdlets, Set-OBMachineSetting, etc.). There are no Linux equivalents or cross-platform alternatives mentioned, and the workflow assumes a Windows environment throughout. PowerShell is given equal or greater prominence than Azure CLI, and the documentation does not clarify platform limitations up front.
Recommendations
  • Explicitly state at the beginning that MARS agent is Windows-only and provide links to Azure Backup solutions for Linux (e.g., Azure Backup for Azure VM Linux, Azure Backup Server, or Recovery Services agent alternatives).
  • Add a comparison table or section that lists backup solutions for Linux and how passphrase/key management is handled for those platforms.
  • Where possible, clarify which steps, tools, or commands are Windows-specific, and suggest Linux alternatives (e.g., using Azure CLI, REST API, or other cross-platform tools for Key Vault operations).
  • If automation is discussed, mention scripting options for Linux (Bash, Python, etc.) for interacting with Azure Key Vault, even if MARS is not supported.
  • Ensure that readers on Linux are guided to appropriate documentation so they do not attempt to use unsupported Windows-only tooling.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/soft-delete-azure-file-share.md ...b/main/articles/backup/soft-delete-azure-file-share.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias by referencing a 'Undelete File Share Script' that is specifically a PowerShell script, without mentioning or providing equivalent Linux/bash/CLI examples. The instructions and links consistently refer to the Azure Portal and PowerShell, with no mention of cross-platform tools or Linux-native approaches. There are no bash, Azure CLI, or REST API examples, and the documentation assumes the use of Windows-centric tools and workflows.
Recommendations
  • Provide equivalent examples using Azure CLI and/or bash scripts for undeleting file shares and other operations.
  • Explicitly mention and link to cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell scripts.
  • Ensure that instructions for enabling/disabling soft delete and restoring file shares include both Windows and Linux workflows.
  • Add notes clarifying that all operations can be performed from Linux, macOS, and Windows, and provide platform-agnostic guidance.
  • Reorder examples so that cross-platform methods (e.g., Azure CLI) are presented before or alongside Windows/PowerShell methods.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/soft-delete-sql-saphana-in-azure-vm.md ...articles/backup/soft-delete-sql-saphana-in-azure-vm.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 instructions and examples only for the Azure Portal and Azure PowerShell (a Windows-centric tool). There are no CLI, Bash, or Linux-native examples or references. PowerShell is presented as the only scripting/automation interface, and no mention is made of Azure CLI or REST API alternatives, which are more platform-agnostic and commonly used on Linux. This may disadvantage Linux users or those preferring cross-platform tooling.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell operations (delete, undelete, restore, resume backup), using Bash syntax.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or REST API, and provide links or examples.
  • Reorder sections or provide tabs so that PowerShell and CLI/Linux examples are presented with equal prominence.
  • Where screenshots or UI steps are shown, clarify that the Azure Portal is platform-agnostic.
  • Consider including REST API sample calls for advanced users or automation scenarios.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. Only Windows Server operating systems are listed as supported, with Linux explicitly marked as unsupported. All examples and tooling references (e.g., PowerShell) are Windows-centric, with no mention of Linux equivalents or cross-platform CLI support. Windows tools and patterns (such as IIS file extension filtering) are discussed without Linux alternatives.
Recommendations
  • Clearly indicate plans or timelines for Linux support, if any, or provide a rationale for its absence.
  • Add equivalent examples and instructions for Linux environments if/when support is added.
  • Expand tooling support to include cross-platform options such as Azure CLI or REST API, and document their usage.
  • Avoid Windows-first language; present platform support in a neutral, comparative manner.
  • If features are unavailable on Linux, explicitly state limitations and suggest workarounds or alternatives.
GitHub Create Pull Request
← Previous Page 29 of 65 Next →