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 1026-1050 of 1604 flagged pages
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong bias towards Windows and PowerShell. All deployment and cleanup examples are provided exclusively in PowerShell, with no equivalent Azure CLI or Bash examples. The template specifically deploys a Windows VM, and Linux alternatives are not mentioned or demonstrated. Although the Azure CLI and portal are referenced as options, practical guidance and code samples are only given for PowerShell, which is more familiar to Windows users.
Recommendations
  • Add equivalent Azure CLI (bash) examples for deploying the ARM template, including parameter input and resource group creation.
  • Provide a sample template or instructions for deploying a Linux VM, or clarify how to modify the template for Linux.
  • Include cleanup instructions using Azure CLI commands.
  • When referencing multiple tools (PowerShell, CLI, portal), provide code samples for at least PowerShell and CLI, and present them in parallel or with equal prominence.
  • Explicitly mention cross-platform compatibility and provide guidance for users on macOS/Linux environments.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing individual file recovery instructions for Windows Server VMs, omitting Linux VM scenarios. The only registry key example for parallel restore is Windows-specific, and there are no references to Linux tools, file systems, or recovery workflows. The documentation assumes the use of Windows-based management tools and environments throughout.
Recommendations
  • Add explicit guidance and examples for restoring individual files from Linux-based VMs, including any limitations or alternative workflows if direct item-level restore is not supported.
  • Mention Linux file system compatibility and any required steps for Linux VM recovery (e.g., mounting VMDKs on a Linux system, using third-party tools, or exporting files via NFS/Samba).
  • Clarify in the documentation whether item-level restore is supported for Linux VMs, and if not, provide workarounds or references to relevant tools.
  • Where registry edits are mentioned, note that this is a Windows-only operation and provide equivalent configuration steps for Linux environments if applicable.
  • Balance the documentation by including Linux terminology, screenshots, and examples where possible, or explicitly state platform limitations.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-restore-using-cli.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-restore-using-cli.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily focuses on Azure CLI commands, which are cross-platform, but it introduces Windows bias by mentioning Azure PowerShell as an alternative in the introduction and linking to a PowerShell-specific guide. There are no explicit Linux- or macOS-specific instructions, nor are there examples of shell environments or command differences for non-Windows platforms. The use of redirection operators (e.g., '>restoreconfig.json') is compatible with both Windows and Unix shells, but there is no discussion of shell-specific nuances, environment variable syntax differences, or prerequisites for Linux/macOS users. The documentation implicitly assumes a Windows-first perspective by mentioning PowerShell before any Linux alternatives and not providing parity guidance for Linux users.
Recommendations
  • Add explicit notes or sections for Linux/macOS users, including any prerequisites (e.g., az CLI installation, shell compatibility, jq usage for JSON parsing, etc.).
  • If PowerShell is mentioned as an alternative, also mention Bash or other common Linux shells as alternatives for scripting.
  • Provide example commands using both Windows (PowerShell) and Linux/macOS (Bash) syntax where there are differences (e.g., environment variable usage: $VAR vs. $env:VAR).
  • Clarify that the Azure CLI commands are cross-platform and highlight any platform-specific considerations.
  • Link to Linux/macOS-specific guides or troubleshooting pages if available.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure Portal (a GUI tool most familiar to Windows users) for installation steps, mentioning Azure PowerShell before Azure CLI in the 'Next steps' section, and not providing any Linux shell or cross-platform command-line examples directly in the main flow. The focus on Azure Portal and PowerShell, both of which are more commonly used in Windows environments, may make Linux users feel secondary or unsupported.
Recommendations
  • Add step-by-step instructions for installing the Azure Backup extension using Azure CLI directly in the main guide, not just as a link in 'Next steps'.
  • Ensure that Azure CLI (which is cross-platform) examples are given equal or higher prominence than PowerShell examples.
  • Include Linux shell (bash) command examples where relevant, especially for DevOps engineers who may be working in Linux environments.
  • Balance screenshots and instructions to reflect both Windows and Linux user experiences, or clarify that the steps are platform-agnostic.
  • Explicitly state that the procedures work on all platforms, and provide any platform-specific notes if necessary.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation is heavily oriented towards Windows environments, specifically the Microsoft Azure Recovery Services (MARS) agent, which is a Windows-only backup tool. All operational instructions, screenshots, and automation references are based on the MARS agent console, PowerShell cmdlets, and Windows-centric patterns. There are no examples or guidance for Linux systems or cross-platform backup agents, and the automation references (e.g., Set-OBMachineSetting) are PowerShell-specific. The documentation assumes the user is operating in a Windows environment throughout.
Recommendations
  • Clearly state at the beginning that the MARS agent is Windows-only, and provide links to equivalent Linux backup solutions (such as Azure Backup for Linux VMs or Azure Backup Server).
  • Where possible, include parity guidance for Linux-based backup agents, or explicitly mention that the described workflow does not apply to Linux.
  • If Azure CLI or REST API alternatives exist for agent registration or passphrase management, provide those examples to support automation from non-Windows platforms.
  • Add a comparison table or section outlining backup and passphrase management options for both Windows and Linux environments in Azure.
  • Review automation script references to clarify their platform dependencies and suggest alternatives for Linux users where available.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates several forms of Windows bias. Windows-specific tools and patterns (such as PowerShell and OS disk swap documentation linking to Windows-specific pages) are mentioned before or instead of Linux equivalents. Step-by-step instructions and automation examples reference PowerShell, but there are no corresponding CLI or Linux-native examples. The Linux-specific restore process is relegated to a separate, brief step, and lacks detailed guidance or parity with the Windows instructions.
Recommendations
  • Provide equivalent Linux examples alongside Windows/PowerShell instructions, such as using Azure CLI or Bash scripts for restoring VMs and creating new instances from restored disks.
  • When referencing features like OS disk swap, include links and instructions for both Windows and Linux VMs, or clarify any differences.
  • Avoid presenting Windows tools (e.g., PowerShell) as the default or only automation method; always offer cross-platform alternatives.
  • Expand the Linux restore section to include detailed, step-by-step instructions, matching the depth provided for Windows.
  • Ensure that all screenshots, notes, and linked resources are inclusive of both operating systems, or clearly indicate when a process is OS-specific.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and all scripting examples are in PowerShell and Azure CLI, with no Linux shell or bash-specific examples. Windows-specific terminology (e.g., C: drive, BitLocker) is mentioned before Linux equivalents (e.g., root filesystem, dm-crypt). There are no explicit bash or Linux shell command examples for managing selective disk backup, and the only Linux-specific guidance is limited to ensuring the presence of 'lsblk' and 'lsscsi' tools. The documentation assumes familiarity with Windows tools and patterns, and Linux is treated as an afterthought in several sections.
Recommendations
  • Add bash/Linux shell command examples for all CLI operations, demonstrating usage in a typical Linux environment (e.g., using variables, jq for parsing output, etc.).
  • When discussing OS-specific details (e.g., used space calculation), present Linux and Windows information in parallel, not Windows first.
  • Include troubleshooting steps and examples specific to common Linux distributions (e.g., Ubuntu, CentOS) for disk enumeration and backup validation.
  • Expand the section on required Linux tools (lsblk, lsscsi) with installation instructions for multiple distributions, and provide sample output to help users verify correct setup.
  • Where PowerShell is referenced, explicitly note cross-platform availability or provide equivalent bash/Linux shell alternatives.
  • Ensure that any references to Windows tools (e.g., BitLocker, C: drive) are matched with Linux equivalents (e.g., dm-crypt, / root filesystem) in the same context and order.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. It references Azure PowerShell alongside Azure CLI for authentication, even though only Azure CLI is supported for Terraform authentication. In the 'Next steps' section, PowerShell is consistently mentioned before Azure CLI and REST API, and there is no mention of Linux-specific shells or tooling. All command-line examples use generic 'Console' blocks, but the narrative and tool ordering favor Windows/PowerShell users.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and provide example commands for both Windows (PowerShell/CMD) and Linux/macOS (Bash) environments where relevant.
  • In all lists (such as 'Next steps'), alternate or randomize the order of PowerShell and CLI, or mention CLI first to reflect its cross-platform nature.
  • Clarify that Azure PowerShell is not supported for Terraform authentication, and remove or de-emphasize PowerShell references in that context.
  • Where possible, include example shell commands (e.g., export environment variables) for both Bash and PowerShell.
  • Add a note or section highlighting that all steps are fully supported on Linux/macOS as well as Windows.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows/Azure Portal-centric bias. It exclusively describes restore operations using the Azure Portal UI, with no command-line examples for Linux environments. Where scripting is mentioned, only PowerShell or CLI scripts are referenced, but no explicit Linux shell (bash) examples are provided. The workflow and permissions guidance are oriented around Azure patterns familiar to Windows administrators, and there is no mention of Linux-native tools or commands for mounting disks or handling SAP HANA restores outside the Azure Portal.
Recommendations
  • Add explicit Linux (bash) command-line examples for mounting and attaching restored disks to Linux-based Azure VMs.
  • Provide step-by-step instructions for performing SAP HANA restores using Azure CLI and shell scripts, not just via the Azure Portal.
  • Include references to Linux-native tools (such as mount, lsblk, etc.) for disk operations post-restore.
  • Ensure that scripting examples are cross-platform, showing both PowerShell and bash equivalents where relevant.
  • Clarify in each section whether the instructions apply to both Windows and Linux VMs, or specify any OS-specific steps.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example Windows First 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. It explicitly states that Linux is not supported for SQL Server backup in Azure VMs, only lists Windows Server versions as supported operating systems, and references Windows-specific tools and frameworks (e.g., PowerShell, .NET Framework). There are no Linux equivalents or examples provided, and the documentation does not address Linux users or scenarios at all.
Recommendations
  • Clearly state the roadmap or plans for Linux support, if any, and provide guidance or alternatives for Linux users.
  • If partial Linux support exists or is planned, include Linux-specific instructions, examples, and supported distributions.
  • Mention cross-platform tools (such as Azure CLI) where possible, and avoid referencing only Windows tools like PowerShell unless absolutely necessary.
  • Provide a comparison table or section outlining feature parity (or lack thereof) between Windows and Linux environments for SQL Server backup in Azure VMs.
  • If Linux is not supported, suggest alternative backup strategies or products for Linux-based SQL Server deployments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/troubleshoot-azure-files.md .../blob/main/articles/backup/troubleshoot-azure-files.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by providing troubleshooting scripts and automation examples exclusively in PowerShell, with no mention of Linux or cross-platform alternatives. References to scripts (such as for finding Recovery Services vaults or undeleting file shares) link only to PowerShell-based solutions, and there are no CLI, Bash, or Linux-native instructions or examples. This may hinder Linux or cross-platform administrators from efficiently following the guidance.
Recommendations
  • Provide equivalent troubleshooting scripts and automation examples using Azure CLI and Bash, ensuring they are cross-platform and runnable on Linux, macOS, and Windows.
  • When referencing scripts, clearly indicate if they are PowerShell-specific and offer alternative links or code snippets for Linux/CLI users.
  • Include examples and instructions for performing common tasks (such as undeleting file shares or finding Recovery Services vaults) using Azure CLI commands.
  • Review all troubleshooting steps to ensure that any tool or script mentioned has a Linux-compatible alternative, and document both options side by side.
  • Add a section or note at the beginning of the document clarifying that all examples are available for both Windows (PowerShell) and Linux (CLI/Bash), with links to the relevant sections.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows a bias towards Windows by referencing a PowerShell script for undeleting file shares and not providing equivalent CLI or Linux-native examples. The only script-based automation mentioned is a PowerShell script, and there are no instructions or links for performing the same tasks using Azure CLI, Bash, or other cross-platform tools. This may hinder Linux or cross-platform users from following the guidance efficiently.
Recommendations
  • Provide equivalent Azure CLI and Bash script examples for undeleting file shares and other automation tasks, alongside PowerShell.
  • When referencing scripts (such as the 'Undelete File Share Script'), include links or instructions for both PowerShell and Azure CLI/Bash versions.
  • Avoid referencing only Windows-specific tools (like PowerShell) in automation scenarios; always mention cross-platform alternatives.
  • Explicitly state that all operations can be performed from any OS using Azure CLI, and provide relevant command examples.
  • Review linked documentation to ensure Linux and macOS users are not excluded from automation or management scenarios.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides a PowerShell script sample for managing backup policies with the MARS agent, referencing Windows-specific tools and environment variables. There are no examples or instructions for Linux environments, nor is there any mention of Linux-compatible tools or scripting alternatives.
Recommendations
  • Add equivalent script samples for Linux environments, using Bash, Python, or other common Linux scripting languages.
  • Clearly state the platform limitations of the MARS agent and whether Linux is supported or not.
  • If Linux is supported, provide guidance on how to automate backup policy management on Linux, including relevant tools and commands.
  • If only Windows is supported, explicitly mention this at the beginning of the documentation to set user expectations.
  • Consider including a comparison table or section outlining differences in backup policy management between 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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All examples, file paths, and tool references (e.g., PsExec, NT AUTHORITY\SYSTEM, C:\Program Files, SSMS) are Windows-specific. There are no Linux-specific instructions, examples, or mentions of restoring SQL Server databases on Linux-based Azure VMs, despite SQL Server being supported on Linux. The use of Windows command-line tools and patterns is pervasive, and there is no parity in guidance for Linux users.
Recommendations
  • Add explicit instructions and examples for restoring SQL Server databases on Linux-based Azure VMs, including file paths (e.g., /var/opt/mssql/), permissions, and service management.
  • Provide Linux equivalents for Windows tools and commands, such as using 'sudo' for permissions, and alternatives to PsExec for privilege escalation.
  • Include examples using sqlcmd or Azure CLI for Linux environments, and clarify any differences in process or prerequisites.
  • Mention and demonstrate how to mount Azure File Shares on Linux VMs, including necessary package installations and mount commands.
  • Ensure that all references to SSMS are supplemented with Linux-compatible tools or instructions (e.g., Azure Data Studio, sqlcmd).
  • Clearly state at the beginning of the article whether the instructions apply to both Windows and Linux SQL Server VMs, and provide links to Linux-specific documentation if available.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-the-mabs-server.md ...cs/blob/main/articles/backup/backup-the-mabs-server.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments. All operational examples, tool references, and recovery procedures are specific to Windows, using tools such as PowerShell, mountvol.exe, diskshadow.exe, psexec.exe, and referencing Windows file paths and sharing mechanisms. There are no examples or guidance for performing these tasks on Linux systems, nor are cross-platform alternatives mentioned. The documentation assumes the administrator is working exclusively in a Windows environment.
Recommendations
  • Provide explicit statements clarifying platform support (e.g., if MABS is Windows-only, state this clearly at the top).
  • If any components can be managed or accessed from Linux (e.g., SQL Server backups, Azure Backup), provide equivalent Linux command-line examples (e.g., using sqlcmd, Azure CLI, or mounting VHDs on Linux).
  • Mention cross-platform tools or alternatives where possible, such as using SMB shares from Linux, or restoring SQL Server databases using Linux tools.
  • Where Windows-specific tools are required, explain why and suggest any possible workarounds for non-Windows environments.
  • Add a section summarizing platform limitations and supported scenarios, so Linux administrators are aware of any constraints.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/use-archive-tier-support.md .../blob/main/articles/backup/use-archive-tier-support.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell-based (Windows-centric) instructions and tools. PowerShell is presented as the primary scripting interface, with detailed, step-by-step examples and explanations. The CLI section is present but less detailed and is positioned after the PowerShell section. There is no mention of Linux-native tools, shell scripting, or Linux-specific considerations, and the CLI examples do not reference Linux explicitly. The documentation assumes familiarity with Windows/PowerShell paradigms and does not provide parity for Linux users.
Recommendations
  • Add explicit Linux shell/bash scripting examples alongside PowerShell, especially for automation scenarios.
  • Clarify that Azure CLI commands are cross-platform and provide Linux-specific usage notes (e.g., shell syntax, environment variables, file paths).
  • Include Linux-native troubleshooting tips or references (e.g., common issues with az CLI on Linux, package dependencies, permissions).
  • Balance the order of presentation: alternate or parallelize PowerShell and CLI/Linux instructions, or provide a clear navigation structure for both audiences.
  • Mention and link to Linux installation and environment setup guides for Azure CLI and related tools.
  • Where screenshots or UI references are given, note any differences in experience for Linux users (if applicable).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-postgresql-backup.md ...lob/main/articles/backup/tutorial-postgresql-backup.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows environments by providing PowerShell scripts as the primary or only automation example for granting privileges to database users. There are no equivalent Linux shell or cross-platform command-line examples (e.g., Bash, psql). PowerShell is mentioned first and repeatedly, and Linux-native tools or workflows are only referenced as alternatives, not as first-class instructions. This may make the tutorial less accessible to Linux users or those managing PostgreSQL on non-Windows platforms.
Recommendations
  • Provide equivalent Bash or shell script examples alongside PowerShell scripts for granting privileges and other automation steps.
  • Include explicit instructions and examples using the psql command-line tool for privilege management.
  • When referencing automation scripts, mention both PowerShell and Bash/psql options together, or default to cross-platform approaches.
  • Clarify that PowerShell is not required and that all steps can be performed on Linux-based systems using standard PostgreSQL tools.
  • Add screenshots or CLI instructions from Linux environments where relevant, not just Windows/Azure Portal UI.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for using the Azure Portal and Azure PowerShell to manage soft delete for SQL Server and SAP HANA backups in Azure VMs. However, it exclusively features PowerShell examples for command-line operations, with no mention of Linux-native tools, Azure CLI, or Bash scripting. The PowerShell section is prominent and detailed, while Linux users are not provided with equivalent guidance, creating a Windows-centric bias.
Recommendations
  • Add equivalent Azure CLI (az backup ...) examples for all PowerShell operations, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that the steps can be performed from Linux environments using Azure CLI or REST API, and provide links or examples.
  • If any operations require PowerShell, clarify whether PowerShell Core (cross-platform) is supported, and provide installation guidance for Linux users.
  • Reorder or parallelize the documentation so that Azure CLI and PowerShell examples are presented together, or allow users to select their preferred environment (PowerShell, CLI, Bash) via tabs.
  • Include a note or section addressing Linux administrators and their typical workflows, ensuring parity in instructions and examples.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/view-reports.md ...s/azure-docs/blob/main/articles/backup/view-reports.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Windows-centric backup solutions (such as DPM and SQL in Azure VM) more prominently and in greater detail than Linux equivalents. There are no explicit Linux or cross-platform command-line examples, and the only workload-specific examples provided are for Windows technologies. Linux workloads (e.g., Azure Database for PostgreSQL) are mentioned only in the context of limitations or unsupported features, not as primary examples. There is also a lack of guidance or examples for Linux-based backup scenarios.
Recommendations
  • Include examples and screenshots for Linux-based workloads (e.g., Azure Backup for Linux VMs, Azure Database for PostgreSQL) alongside Windows examples.
  • Provide parity in explanations for both Windows and Linux workloads, ensuring that Linux scenarios are not only mentioned in the context of limitations.
  • Add command-line examples using both Azure CLI and PowerShell, and ensure that Linux shell commands are represented where relevant.
  • Highlight cross-platform backup scenarios and tools, and avoid referencing only Windows-specific tools (such as DPM) without Linux equivalents.
  • Ensure that any workload-specific optimizations or troubleshooting steps are covered 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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line and scripting examples are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or Linux-native tools. The workflow assumes use of Windows tools (e.g., PowerShell scripts, .ps1 files, Cloud Shell in PowerShell mode), and file paths are shown in Windows format (e.g., C:\<filepath>). There are no Linux/Unix command equivalents or guidance for non-Windows environments, and the documentation refers to Windows-centric patterns and tools before (or instead of) cross-platform alternatives.
Recommendations
  • Provide equivalent Azure CLI (az) commands and Bash script examples alongside PowerShell for all automation and scripting steps.
  • Include Linux/Unix file path examples and instructions for uploading and running scripts from Linux/macOS environments.
  • Mention that Cloud Shell supports both Bash and PowerShell, and show how to perform steps in both environments.
  • Where PowerShell scripts are referenced, provide Bash or Python alternatives, or clarify if the scripts are cross-platform.
  • Explicitly state platform requirements for any scripts or tools, and offer guidance for Linux/macOS users.
  • Add a section or callouts for Linux administrators, highlighting any differences or additional steps required.
  • Ensure screenshots and UI instructions are not Windows-specific unless the UI is identical across platforms.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/encryption-at-rest-with-cmk.md ...ob/main/articles/backup/encryption-at-rest-with-cmk.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is consistently presented as a primary automation/scripting option alongside the Azure CLI and portal, with detailed PowerShell examples and outputs. There is a strong emphasis on PowerShell cmdlets, which are traditionally associated with Windows environments, and no mention of Linux-native scripting tools (e.g., Bash, shell scripts) or Linux-specific considerations. Additionally, the documentation references BitLocker for Windows before DM-Crypt for Linux in the context of Azure Disk Encryption, subtly prioritizing Windows technologies.
Recommendations
  • Include Bash/shell script examples for key operations, especially for Linux users who may prefer scripting outside of Azure CLI.
  • When mentioning encryption technologies, present Linux (DM-Crypt) and Windows (BitLocker) options in parallel, or alternate their order to avoid implicit prioritization.
  • Where possible, clarify that PowerShell is cross-platform, or provide explicit guidance for Linux users on installing and using PowerShell if it is required.
  • Add notes or links to Linux-specific best practices or troubleshooting tips for common backup and encryption scenarios.
  • Ensure that all automation examples (PowerShell, CLI) are equally detailed and that CLI examples are not less comprehensive than PowerShell ones.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-restore-using-cli.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-restore-using-cli.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. While the main focus is on Azure CLI (which is cross-platform), the only alternative method mentioned is Azure PowerShell, with a direct link to a PowerShell-specific guide. There are no references to Linux- or macOS-specific shell environments, nor are there any examples or notes about running the commands in Bash or other non-Windows shells. Output redirection (e.g., '>restoreconfig.json') is shown in a way that works in both Bash and PowerShell, but there is no explicit mention of Linux or macOS compatibility, nor are there troubleshooting tips or environment notes for those platforms. The documentation does not mention Linux tools or patterns, and the only alternative to CLI is a Windows-centric tool (PowerShell).
Recommendations
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide any platform-specific notes if necessary.
  • When mentioning PowerShell as an alternative, also mention Bash or shell scripting as a valid approach for Linux/macOS users, or clarify that the CLI commands are cross-platform.
  • Include a section or note about running the commands in Bash or other Linux shells, especially if there are differences in variable syntax or output redirection.
  • If possible, provide example commands or troubleshooting tips for Linux/macOS users (e.g., handling environment variables, file permissions, or CLI installation).
  • Avoid implying that PowerShell is the only or primary alternative to Azure CLI by either omitting the PowerShell reference or balancing it with Linux/macOS alternatives.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-azure-data-box-dpm-mabs.md ...icles/backup/offline-backup-azure-data-box-dpm-mabs.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All supported platforms are Windows Server versions, and all setup, configuration, and troubleshooting steps assume a Windows OS. Only Windows tools (e.g., PSExec, regedit, Windows certificate manager) and Windows-specific commands (cmd, PowerShell modules) are referenced. There are no Linux examples, nor is Linux support mentioned or considered.
Recommendations
  • Clearly state if Linux is unsupported, or add a section on Linux support if available.
  • If Linux support is possible, provide equivalent instructions for Linux environments (e.g., mounting NFS shares, managing certificates, using Azure CLI instead of PowerShell).
  • Mention Linux tools and patterns where relevant, and provide parallel examples for both Windows and Linux.
  • Avoid assuming the use of Windows-only utilities (like PSExec, regedit) without alternatives or explanations for non-Windows users.
  • If the feature is truly Windows-only, make this explicit early in the documentation to set user expectations.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-release-notes-v3.md ...b/main/articles/backup/backup-mabs-release-notes-v3.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation for Microsoft Azure Backup Server v3 is heavily oriented towards Windows environments. All examples, tools, and instructions reference Windows-only components such as SQL Server Management Studio (SSMS), SQL Server Reporting Services (SSRS), and Windows file paths. There are no examples or mentions of Linux support, tools, or equivalent procedures, and all troubleshooting steps assume a Windows environment.
Recommendations
  • Clearly state at the beginning of the documentation whether MABS is Windows-only or if Linux workloads/agents are supported.
  • If Linux workloads are supported, provide parallel troubleshooting steps and examples for Linux environments, including command-line instructions and relevant tools.
  • Mention Linux equivalents (if any) for backup/restore operations, database management, and reporting, or clarify their absence.
  • Avoid using only Windows file paths and tools in examples; include Linux paths and commands where applicable.
  • If MABS is not supported on Linux, explicitly state this to set user expectations and avoid confusion.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All supported platforms are Windows-only, and there is no mention of Linux support or examples. All instructions, prerequisites, and troubleshooting steps are written exclusively for Windows, using Windows-specific tools (PowerShell, MARS Agent, Windows command prompt, registry editor, Control Panel, etc.). There are no Linux equivalents or alternative workflows provided, nor is it clarified whether Linux is unsupported or simply omitted.
Recommendations
  • Explicitly state whether Linux is supported or unsupported for this workflow. If unsupported, clarify this early in the documentation.
  • If Linux support is possible, provide equivalent instructions and examples for Linux environments, including installation, configuration, and troubleshooting steps.
  • Include Linux command-line examples (e.g., Bash, az CLI) alongside PowerShell commands where applicable.
  • Reference Linux tools and patterns (e.g., mounting NFS shares on Linux, using Linux backup agents) if available.
  • Ensure screenshots and UI references are not exclusively Windows-centric if cross-platform support is intended.
GitHub Create Pull Request
← Previous Page 42 of 65 Next →