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 1426-1450 of 1604 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-backup-troubleshoot.md ...backup/azure-kubernetes-service-backup-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows/Azure Portal bias by consistently presenting troubleshooting steps and configuration changes using the Azure Portal UI first, with no mention of Linux-native or cross-platform CLI alternatives for critical operations (e.g., scaling node pools, updating extension configuration). There are no PowerShell-specific examples, but the lack of Linux CLI (kubectl, az, YAML editing) parity for portal-based instructions and screenshots suggests a bias towards Windows/GUI workflows. All command-line examples provided are platform-neutral (kubectl, az), but the step-by-step guides for resource management are portal-centric.
Recommendations
  • For every Azure Portal-based instruction (e.g., scaling node pools, updating extension configuration), provide equivalent az CLI and kubectl commands with example syntax.
  • Add explicit Linux CLI workflows for resource management tasks, such as scaling node pools, updating extension configuration, and assigning roles.
  • Include notes or sections highlighting cross-platform compatibility of CLI commands, and clarify that kubectl/az CLI can be used on Linux, macOS, and Windows.
  • Where screenshots are used, consider providing terminal output examples for CLI workflows to support Linux users.
  • Review all troubleshooting steps to ensure that Linux-native and CLI-first options are presented at parity with portal/GUI instructions.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-manage-backups.md ...kup/azure-kubernetes-service-cluster-manage-backups.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily provides Azure CLI commands and Azure portal instructions for managing AKS backups. While Azure CLI is cross-platform, there is a notable absence of Linux-specific shell examples, troubleshooting steps, or references to Linux-native tools and patterns. The 'Next steps' section lists Azure PowerShell before Linux alternatives, and there are no bash or Linux shell command examples, nor any mention of Linux-specific considerations. This results in a subtle Windows bias, as Linux users may expect parity in examples and guidance.
Recommendations
  • Add explicit bash/Linux shell examples for all CLI commands, including environment variable usage and command chaining.
  • Include troubleshooting steps and patterns relevant to Linux environments (e.g., checking pod status with kubectl, using grep, tail, etc.).
  • Mention that Azure CLI works on Linux, macOS, and Windows, and provide installation instructions for Linux.
  • In the 'Next steps' section, list Linux/bash guidance before or alongside PowerShell, and link to Linux-specific documentation if available.
  • Add notes or sections on using AKS and Azure Backup from Linux workstations, including common issues and solutions.
  • Where screenshots are shown, include examples from Linux terminals or desktop environments, not just the Azure portal.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-userestapi-restoreazurevms.md .../backup/backup-azure-arm-userestapi-restoreazurevms.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page exhibits a subtle Windows bias. In example responses for recovery points, the 'osType' property is consistently set to 'Windows', and metadata such as <OsType>Windows</OsType> is shown in sample payloads. There is no mention or example of Linux VMs or their restore scenarios, nor any Linux-specific considerations. Windows terminology and metadata are present, but Linux is not referenced, which may lead users to assume the process is Windows-centric or that Linux is unsupported.
Recommendations
  • Include example responses and request bodies for Linux VMs, showing 'osType': 'Linux' and relevant metadata.
  • Explicitly state that the REST API supports both Windows and Linux VMs, and note any differences in restore behavior or requirements.
  • Add a section or note describing Linux-specific restore considerations (e.g., handling SSH keys, disk formats, boot diagnostics).
  • Ensure parity in documentation by alternating or combining Windows and Linux examples where VM OS type is referenced.
  • Review linked documents to ensure Linux scenarios are equally represented.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-cloud-as-tape.md ...n/articles/backup/backup-azure-backup-cloud-as-tape.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses on Azure Backup for tape replacement but demonstrates Windows bias by referencing System Center DPM (a Windows-only tool) and providing links and examples that are specific to Windows (e.g., 'backup-windows-with-mars-agent.md'). There are no mentions of Linux backup tools, Linux-specific instructions, or examples for Linux environments.
Recommendations
  • Include equivalent Linux backup solutions (such as Azure Backup integration with Linux workloads or agents).
  • Provide Linux-specific examples and screenshots for scheduling and retention policies.
  • Add links to documentation pages for backing up Linux servers with Azure Backup.
  • Mention cross-platform compatibility and clarify any differences in setup or features between Windows and Linux environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-database-postgresql-flex-use-rest-api-create-update-policy.md ...base-postgresql-flex-use-rest-api-create-update-policy.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias by referencing the 'default PowerShell object' for PostgreSQL - Flexible servers as the primary example of backup policy scheduling and retention. No equivalent Linux CLI, Bash, or cross-platform tooling is mentioned, and PowerShell is referenced before any other automation or scripting options. All examples focus on REST API and JSON, which are platform-neutral, but the only explicit tooling reference is to PowerShell, suggesting a Windows-centric approach.
Recommendations
  • Replace or supplement references to 'default PowerShell object' with cross-platform alternatives, such as Azure CLI, Bash scripts, or Python SDK examples.
  • Explicitly mention that the REST API and JSON examples can be used from any OS, and provide sample commands for Linux/macOS environments (e.g., using curl, az CLI, or Python requests).
  • Add a section or note on how to automate these REST API calls from Linux environments, including example scripts.
  • Ensure that any tooling references (such as PowerShell) are balanced with Linux-native or cross-platform tools, and avoid implying that PowerShell is the default or only option.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-restore-disks.md ...backup-azure-dataprotection-use-rest-api-restore-disks.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references Windows-centric tools (Azure PowerShell) before mentioning Azure CLI, and does not provide any Linux-specific examples or guidance. All examples are generic REST API calls, but the introduction and cross-references prioritize Windows tools and do not mention Linux shell usage or patterns. There is no evidence of PowerShell-heavy content or exclusive use of Windows tools, but the ordering and lack of Linux parity are notable.
Recommendations
  • Mention Azure CLI before or alongside Azure PowerShell when listing alternative restore methods, as CLI is cross-platform and preferred by many Linux users.
  • Add explicit Linux shell (bash) examples for invoking REST API calls, such as using curl or az rest, to demonstrate parity and usability for Linux administrators.
  • Include notes or sections on how Linux users can authenticate and interact with Azure REST APIs, e.g., using service principals and environment variables.
  • Ensure that references to tools and patterns are platform-neutral, or provide both Windows and Linux equivalents where applicable.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-integrate-microsoft-defender-using-logic-apps.md ...up-azure-integrate-microsoft-defender-using-logic-apps.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on Azure Virtual Machines without specifying OS, but all examples and workflows implicitly assume Windows environments. There is no mention of Linux-specific considerations, tools, or examples, nor any guidance for Linux VMs. The integration steps (e.g., Defender for Cloud, Logic Apps, Office 365 email) are presented in a way that aligns with typical Windows/enterprise patterns, and there is no parity for Linux backup or alerting workflows.
Recommendations
  • Explicitly state whether the solution applies to both Windows and Linux Azure VMs, or clarify any limitations.
  • Provide examples or notes for Linux VM scenarios, including how ransomware detection and backup protection work for Linux workloads.
  • Include references to Linux-compatible email solutions (e.g., SMTP, SendGrid) in addition to Office 365.
  • Add troubleshooting or configuration steps specific to Linux VMs (e.g., permissions, Defender agent installation, backup agent differences).
  • Mention any differences in alerting, backup retention, or automation for Linux VMs, if applicable.
  • Ensure parity in documentation by including screenshots or CLI examples relevant to Linux environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-sql-vm-rest-api.md ...b/main/articles/backup/backup-azure-sql-vm-rest-api.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-centric resource names (e.g., SQLServer2012, MSSQLSERVER), VM names, and examples that imply SQL Server on Windows. There are no examples or guidance for Linux-based SQL Server VMs, nor any mention of Linux-specific considerations, tools, or patterns. The documentation does not clarify whether the REST API process applies equally to SQL Server on Linux VMs, nor does it provide Linux-oriented sample resource names or scenarios.
Recommendations
  • Explicitly state whether the documented REST API process supports SQL Server running on Linux VMs in Azure.
  • Add Linux-based example resource names (e.g., SQLServerLinux, MSSQLSERVER on Linux) and VM names to demonstrate parity.
  • Include a note or section describing any differences, prerequisites, or limitations when backing up SQL Server databases on Linux VMs.
  • Provide sample REST API calls and responses for Linux-based SQL Server VMs, if applicable.
  • Reference Linux tools (e.g., Azure CLI, Bash scripts) for automation alongside any Windows/PowerShell references.
  • Ensure terminology and instructions are OS-neutral where possible, or clearly call out OS-specific steps.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-sql-manage-cli.md ...ob/main/articles/backup/backup-azure-sql-manage-cli.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently refers to managing SQL Server databases on Azure VMs, implicitly assuming Windows-based SQL Server deployments. There are no explicit mentions of Linux-based SQL Server VMs, nor examples or notes for Linux-specific considerations. All resource/container names and examples use conventions typical of Windows SQL Server (e.g., 'mssqlserver', 'master'), and there is no guidance for users running SQL Server on Linux VMs.
Recommendations
  • Add explicit notes clarifying whether the instructions apply to both Windows and Linux SQL Server VMs, or only Windows.
  • Include examples and resource naming conventions for SQL Server on Linux VMs (e.g., container names, database names, file paths).
  • Highlight any differences in backup/restore operations or prerequisites for SQL Server on Linux VMs.
  • If Azure Backup supports SQL Server on Linux VMs, provide parity in CLI examples and troubleshooting steps.
  • Reference documentation for managing SQL Server on Linux in Azure, if available.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-enhanced-policy.md ...in/articles/backup/backup-azure-vms-enhanced-policy.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed PowerShell examples for configuring Enhanced backup policies, with step-by-step cmdlets and explanations. The PowerShell section is significantly more comprehensive than the Azure CLI section, which only lists basic commands without detailed parameter breakdowns or sample JSON payloads. PowerShell is a Windows-centric tool, and its prominence suggests a bias toward Windows users. Additionally, the PowerShell instructions are presented before the CLI section, reinforcing a 'Windows-first' pattern. There are no Linux-specific tools (e.g., Bash scripts) or explicit Linux usage patterns mentioned.
Recommendations
  • Expand the Azure CLI section to include detailed, step-by-step examples equivalent to those provided for PowerShell, including sample JSON policy payloads and parameter explanations.
  • Add Bash script examples for common backup operations, demonstrating how Linux users can automate tasks using the CLI.
  • Explicitly mention cross-platform compatibility for CLI commands and clarify that PowerShell examples are primarily for Windows, while CLI is recommended for Linux/macOS.
  • Consider adding a table comparing PowerShell and CLI usage for common tasks, highlighting Linux parity.
  • Review screenshots and UI instructions to ensure they do not assume a Windows environment (e.g., file paths, shell conventions).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-center-actions.md ...ocs/blob/main/articles/backup/backup-center-actions.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently presents backup and restore examples for Azure Virtual Machines (VMs) without specifying or differentiating between Windows and Linux VMs. Linked articles and screenshots focus on generic VM backup, but do not provide Linux-specific guidance, CLI commands, or examples. There is no mention of Linux tools, shell commands, or considerations unique to Linux workloads. The documentation implicitly assumes parity but does not demonstrate it, potentially leaving Linux administrators without clear instructions.
Recommendations
  • Explicitly mention support for both Windows and Linux VMs in all relevant sections.
  • Provide Linux-specific examples, such as using Azure CLI or shell commands, alongside any PowerShell or Windows-centric instructions.
  • Include screenshots or walkthroughs that show Linux VM backup and restore processes.
  • Add notes or links to documentation that address Linux-specific backup/restore scenarios, such as file system differences or application consistency.
  • Ensure that references to VM backup do not default to Windows terminology or tools, and clarify any differences in process for Linux workloads.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-center-support-matrix.md ...b/main/articles/backup/backup-center-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently listing Windows-centric workloads (such as SQL in Azure VM, SAP HANA in Azure VM, System Center Data Protection Manager, Azure Backup Agent (MARS), and Azure Backup Server (MABS)) before Linux or cross-platform equivalents. Windows-specific backup tools are mentioned (MARS, MABS, DPM) without Linux alternatives or parity. There are no explicit Linux examples, and Linux workloads (e.g., Linux VMs, Linux databases) are not directly referenced, even though Azure supports Linux VMs and workloads.
Recommendations
  • Include explicit references to Linux VM backup scenarios and their support in the matrix.
  • Add examples or notes for Linux workloads (e.g., backup/restore for Linux VMs, PostgreSQL on Linux, SAP HANA on Linux).
  • Mention Linux-compatible backup agents or tools if available, or clarify Windows-only tool applicability.
  • Ensure ordering of workloads alternates or groups by platform rather than listing Windows workloads first.
  • Provide parity in documentation for Linux-specific limitations, features, and supported actions.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-postgresql-cli.md ...ocs/blob/main/articles/backup/backup-postgresql-cli.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits Windows bias by referencing Azure PowerShell and its object model before discussing Linux/CLI workflows. The policy object explanation is framed in terms of PowerShell objects, and modifications are described as being more natural in PowerShell (Windows) than in Azure CLI (Linux/macOS). While CLI examples are provided, the narrative and conceptual framing prioritize Windows tools and patterns, and PowerShell is mentioned first in multiple sections. There are no explicit Linux-specific examples or parity notes.
Recommendations
  • Reframe conceptual explanations to be CLI-first or platform-neutral, avoiding PowerShell-centric language.
  • Provide explicit Linux/macOS workflow notes, such as file path conventions (e.g., ./ vs .\), and clarify cross-platform compatibility.
  • Add examples or notes for common Linux tools (e.g., jq, sed) that can assist with JSON manipulation in CLI workflows.
  • Ensure that references to PowerShell are balanced with equivalent Bash/Linux shell guidance, especially in sections discussing object vs file-based modifications.
  • Consider adding a parity table or section that lists differences and equivalencies between Windows/PowerShell and Linux/CLI approaches.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-rm-template-samples.md ...lob/main/articles/backup/backup-rm-template-samples.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by featuring a template specifically for deploying a Windows Server VM with backup enabled, while lacking equivalent examples for Linux VMs. There are no templates or examples that explicitly mention Linux VM backup scenarios, nor is there parity in showcasing Linux-specific backup configurations alongside Windows ones.
Recommendations
  • Add templates and examples for deploying and backing up Linux VMs, similar to the Windows Server VM example.
  • Ensure that backup policy templates and descriptions explicitly mention support for both Windows and Linux VMs where applicable.
  • Provide guidance or links for Linux-specific backup scenarios, such as backing up Linux workloads or configuring backup for Linux-based SQL servers.
  • Review all examples and ensure that Linux is represented equally in scenarios and sample templates, not just Windows.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/blob-backup-configure-tutorial.md ...main/articles/backup/blob-backup-configure-tutorial.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page shows mild Windows bias. In the 'Related content' section, Azure PowerShell is listed first for restore operations, ahead of Azure CLI and REST API. This ordering may suggest a preference for Windows-centric tooling. Additionally, PowerShell is a Windows-native tool, and its prominence can disadvantage Linux users. However, the page does mention Azure CLI and REST API, which are cross-platform, and the main tutorial focuses on the Azure portal, which is OS-agnostic. There are no explicit examples or instructions that are exclusive to Windows or missing Linux equivalents.
Recommendations
  • List Azure CLI before Azure PowerShell in 'Related content' to promote cross-platform parity.
  • Ensure that examples and walkthroughs for CLI and REST API are as detailed and prominent as those for PowerShell.
  • Explicitly mention that Azure CLI and REST API are cross-platform and suitable for Linux/macOS users.
  • Where PowerShell is referenced, clarify its availability on Linux and macOS, or provide equivalent CLI commands.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/modify-vm-policy-cli.md ...docs/blob/main/articles/backup/modify-vm-policy-cli.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a file path example using Windows-style (C:\temp2\Policy.json) and does not mention or show Linux/macOS equivalents (e.g., /home/user/Policy.json). All CLI examples use generic Azure CLI commands, but the only file path shown is Windows-specific, which may confuse or exclude Linux users. There is no mention of Linux shell usage, nor are there examples of saving or editing the JSON file on Linux.
Recommendations
  • Include Linux/macOS file path examples alongside Windows paths (e.g., /home/user/Policy.json).
  • Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS.
  • Provide examples for saving and editing the JSON file using Linux commands (e.g., using cat, nano, vi, etc.).
  • Add a note or section clarifying cross-platform usage and any differences in file path syntax.
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Azure portal and PowerShell as client options before CLI, and includes a note about PowerShell authentication, which may suggest a Windows-centric perspective. There are no explicit Linux examples or references to Linux-specific tools or workflows. The documentation does not provide parity in mentioning Linux environments or shell usage, and the troubleshooting and next steps sections do not highlight cross-platform considerations.
Recommendations
  • List Azure CLI before PowerShell and portal when mentioning client options, as CLI is cross-platform and more common on Linux.
  • Add explicit references to Linux environments and shell usage (e.g., bash) in prerequisites and examples.
  • Include troubleshooting steps or notes relevant to Linux users (e.g., common issues with bash or Linux file permissions).
  • Clarify that all Terraform commands and workflows are cross-platform and provide sample shell commands for both Windows (PowerShell) and Linux (bash).
  • Ensure that next steps and links include Linux-friendly instructions, such as restoring using Azure CLI from a Linux shell.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-portal.md ...cs/blob/main/articles/backup/quick-backup-vm-portal.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page exhibits a mild Windows bias, primarily in the VM agent installation section, where Windows instructions are listed first and provide detailed steps (including file paths and MSI installer links), while Linux instructions are more generic and refer to distribution repositories. The initial VM creation link also points to a Windows VM creation guide, with no mention of Linux VM creation. Throughout the rest of the document, examples and instructions are generally platform-neutral, focusing on the Azure portal UI.
Recommendations
  • Provide parallel links and examples for creating Linux VMs in the Azure portal, alongside the Windows VM creation link.
  • In the VM agent installation section, offer equally detailed Linux instructions, including example commands for installing the agent via RPM/DEB (e.g., apt-get or yum), and specify verification steps for Linux agent installation.
  • Ensure that screenshots and UI references do not implicitly assume Windows VM usage, and clarify when instructions apply to both Windows and Linux VMs.
  • Where possible, balance the order of presentation so that Linux instructions are not always listed after Windows 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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Azure PowerShell and linking to PowerShell-based instructions before or alongside CLI and REST API options. The link to create a Backup vault directs users to a PowerShell-centric page, and the 'Next step' section lists Azure PowerShell before Azure CLI for restore operations. There is no explicit Linux example or mention of Linux-specific tools or patterns.
Recommendations
  • Provide direct links to Azure CLI instructions for creating a Backup vault, not just PowerShell.
  • Ensure that CLI and REST API options are listed before or alongside PowerShell in all step lists and 'Next step' sections.
  • Add explicit notes or examples for Linux/macOS users, such as shell commands or environment-specific considerations.
  • Review included files to ensure they do not reference Windows-only tools or patterns.
  • Consider a dedicated section or callout for cross-platform usage to reinforce parity.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-managed-disks.md ...ocs/blob/main/articles/backup/restore-managed-disks.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias by listing Windows VM disk management instructions before Linux equivalents and by referencing Windows-specific documentation links first. There are no CLI or PowerShell examples in this page, but the guidance for attaching/detaching disks and swapping OS disks prioritizes Windows instructions and links before Linux ones. No Linux-specific tools or patterns are highlighted, and the overall structure subtly favors Windows workflows.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which platform is listed first to avoid implicit prioritization.
  • Explicitly mention that both Windows and Linux VMs are supported, and provide equal detail for both.
  • If referencing platform-specific documentation, use a neutral order or group links together for both platforms.
  • Add examples or screenshots for Linux workflows where possible, similar to those provided for Windows.
  • Review related pages (e.g., CLI/PowerShell guides) to ensure Linux parity in examples and instructions.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-hana-database-instance-troubleshoot.md ...cles/backup/sap-hana-database-instance-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently refers to 'Azure VM' and 'system-assigned managed identity' without clarifying whether the guidance applies to both Windows and Linux VMs. There are no OS-specific troubleshooting steps, examples, or commands (e.g., PowerShell, Bash, CLI) provided, and the documentation does not mention Linux tools or patterns. The only filesystem types mentioned are ext3 and xfs, which are Linux filesystems, but no Linux-specific troubleshooting or examples are given. The lack of explicit Linux guidance or parity in examples may hinder Linux users.
Recommendations
  • Explicitly state whether the troubleshooting steps apply to both Windows and Linux Azure VMs.
  • Provide Linux-specific examples, such as Bash/CLI commands for enabling managed identities and assigning roles.
  • Include references to Linux administration tools (e.g., az CLI, shell scripts) alongside any Windows tools if relevant.
  • Clarify any OS-specific differences in backup/restore workflows, especially for SAP HANA on Linux VMs.
  • Add troubleshooting steps or examples for common Linux issues (e.g., permissions, mount operations) in SAP HANA 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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal and PowerShell/CLI scripts for permission management, without providing explicit Linux command-line examples or guidance. The workflow and screenshots are oriented around GUI interactions typical of Windows environments, and there is no mention of Linux-specific tools, commands, or patterns for mounting disks or restoring SAP HANA databases on Linux VMs, which are the most common OS for SAP HANA deployments.
Recommendations
  • Add explicit Linux command-line examples for mounting restored disks (e.g., using 'lsblk', 'mount', or 'fdisk').
  • Include Linux shell (bash) scripts for permission management and disk attachment, alongside PowerShell/CLI examples.
  • Clarify steps for restoring SAP HANA databases on Linux VMs, including OS-level commands and SAP HANA tools typically used on Linux.
  • Provide screenshots or walkthroughs for Linux environments, not just Azure portal GUI.
  • Mention and link to SAP HANA documentation relevant to Linux, and highlight any OS-specific considerations.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-restore-disk.md ...ocs/blob/main/articles/backup/tutorial-restore-disk.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily focuses on Azure CLI usage, which is cross-platform, but it exhibits Windows bias by referencing PowerShell documentation before Linux equivalents and linking to Windows-specific VM zone documentation. There is a prominent mention of PowerShell as an alternative, but no similar reference to Bash or Linux shell scripting. Additionally, the cross-zonal restore section links to Windows VM documentation first, even though the tutorial is about restoring Linux VMs.
Recommendations
  • Provide references to Linux/Bash scripting guides for Azure VM backup and restore, alongside PowerShell.
  • Ensure that links to documentation about availability zones or VM creation include both Windows and Linux VM guides, or use a neutral overview page.
  • Explicitly mention that all CLI examples work on both Windows and Linux platforms, and clarify any OS-specific differences if present.
  • Add a section or note about restoring Windows VMs with CLI, for parity with the Linux VM focus.
  • Avoid mentioning Windows tools or documentation before Linux equivalents when the tutorial is Linux-centric.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-elastic-san-backup-support-matrix.md ...cles/backup/azure-elastic-san-backup-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively references the Azure portal for configuration, restore, and management steps, with no mention of CLI, PowerShell, or Linux-specific tools. While no explicit Windows tools are referenced, the lack of examples or guidance for Linux users (such as Azure CLI or Bash) and the portal-centric approach can implicitly favor Windows users, who are more likely to use GUI tools. There is no parity for Linux command-line workflows.
Recommendations
  • Add examples for configuring, restoring, and managing Elastic SAN backup using Azure CLI commands, which are cross-platform and widely used by Linux users.
  • Include references or links to PowerShell and Bash scripts for automation, ensuring both Windows and Linux users are supported.
  • Explicitly mention supported tools and interfaces (Azure portal, Azure CLI, PowerShell) and provide equivalent instructions for each.
  • Where possible, provide screenshots or step-by-step guides for both GUI (portal) and CLI workflows.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-center-actions.md ...ocs/blob/main/articles/backup/backup-center-actions.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently presents backup and restore workflows for Azure VMs, SQL in Azure VMs, and SAP HANA in Azure VMs without specifying or providing examples for Linux-based VMs. The examples and linked tutorials focus on generic 'Azure Virtual Machines', but do not clarify or demonstrate Linux-specific backup/restore scenarios, CLI commands, or considerations. There is no mention of Linux tools, patterns, or parity in the examples, and Windows-centric workloads (SQL Server, SAP HANA) are referenced before Linux equivalents. No PowerShell bias is present, but the lack of explicit Linux guidance and examples indicates a Windows-first approach.
Recommendations
  • Add explicit examples and instructions for backing up and restoring Linux-based Azure VMs, including any differences in process, prerequisites, or limitations.
  • Include CLI (az) and Bash examples alongside any GUI workflows, especially for Linux users.
  • Reference Linux-specific workloads and backup scenarios (e.g., MySQL, file-based backups) where applicable.
  • Clarify in each workflow whether the steps apply equally to Windows and Linux VMs, and note any OS-specific considerations.
  • Ensure linked tutorials and 'Learn more' sections include Linux VM backup/restore documentation.
GitHub Create Pull Request
← Previous Page 58 of 65 Next →