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 1401-1425 of 1604 flagged pages
Backup About the SAP ASE (Sybase) database backup on Azure VMs ...cs/blob/main/articles/backup/sap-ase-database-about.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page consistently refers to Azure VMs and backup procedures without specifying or providing examples for Linux environments, despite SAP ASE being commonly run on both Windows and Linux. References to VM creation link to Windows-specific guides, and there are no explicit Linux or cross-platform command-line examples (e.g., Bash, Linux VM creation, or Linux-specific prerequisites). The documentation does not mention Linux tools, patterns, or provide parity in instructions for Linux users.
Recommendations
  • Add explicit instructions and examples for both Windows and Linux VM environments, including links to Linux VM creation guides.
  • Include Linux-specific prerequisites and commands (e.g., running the preregistration script in Bash, using Linux user management tools).
  • Provide parity in troubleshooting and backup/restore examples for Linux, such as using Azure CLI in Bash and referencing Linux file paths.
  • Clarify that the backup solution supports both Windows and Linux, and highlight any OS-specific considerations.
  • Ensure that all referenced scripts and plugins are tested and documented for Linux environments, with clear guidance for Linux administrators.
Backup Support matrix for Azure Elastic SAN Backup (preview) ...cles/backup/azure-elastic-san-backup-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
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 operations, without mentioning or providing examples for command-line tools such as Azure CLI or Azure PowerShell. There is no mention of Linux-specific workflows, nor are there examples or instructions for performing backup and restore operations from Linux environments. This suggests a subtle Windows bias, as the Azure portal is often associated with Windows-centric workflows and administrators, and Linux users may prefer CLI-based or automation-friendly approaches.
Recommendations
  • Add examples and instructions for configuring, restoring, and managing Azure Elastic SAN backups using Azure CLI, which is cross-platform and widely used in Linux environments.
  • Explicitly mention support for Linux-based administration and clarify any platform-specific requirements or limitations.
  • Provide parity in documentation by including both Azure PowerShell and Azure CLI examples, ensuring that Linux users are not excluded.
  • Reference automation and scripting options that work natively on Linux, such as Bash scripts using Azure CLI.
  • Include a section or note on platform compatibility, highlighting that all backup and restore operations can be performed from Linux, macOS, and Windows.
Backup Troubleshoot Azure Kubernetes Service backup ...backup/azure-kubernetes-service-backup-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a 'Windows-first' bias by consistently referencing the Azure portal UI for troubleshooting and configuration steps, with no mention of Linux-native tools or workflows. All command-line examples use Azure CLI and kubectl, which are cross-platform, but there are no explicit Linux shell examples, nor is there any mention of Linux-specific troubleshooting patterns or alternatives to the Azure portal. The screenshots and step-by-step instructions are focused on the Azure portal, which is most commonly accessed from Windows environments, and there is no guidance for users who may prefer or require Linux-native approaches.
Recommendations
  • Add explicit Linux shell (bash) command examples for common troubleshooting and configuration tasks, such as scaling node pools, updating extension configuration, and managing resource limits.
  • Include instructions for performing tasks via the Azure CLI on Linux, such as using az aks nodepool update, az aks k8s-extension, and kubectl, with sample bash scripts.
  • Provide parity for portal-based steps by offering equivalent CLI or YAML-based workflows, especially for resource configuration and extension management.
  • Clarify that all CLI commands are cross-platform and provide notes or links for Linux users where UI steps are described.
  • Add troubleshooting tips for Linux environments, such as checking system logs, using journalctl, or handling permissions and networking issues specific to Linux.
Backup Troubleshoot data recovery from Microsoft Azure Backup Server by using Azure Backup ...ckup/backup-azure-alternate-dpm-server-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively references Microsoft Azure Backup Server (MABS), which is a Windows-based product, and its troubleshooting steps are tailored to Windows environments (e.g., references to Windows Server, Windows Client, DPM server). There are no examples, recommendations, or mentions of Linux environments, tools, or recovery processes, indicating a Windows-centric bias.
Recommendations
  • Clarify in the introduction that MABS is a Windows-only product, and provide guidance or links for Linux-based backup and recovery solutions in Azure (such as Azure Backup for Linux VMs).
  • Include troubleshooting steps or references for data recovery from Azure Backup in Linux environments, if applicable.
  • Add parity in documentation by mentioning equivalent Linux backup agents or processes, or explicitly state their absence if not supported.
  • Ensure that future documentation pages on Azure Backup cover both Windows and Linux scenarios where possible, or clearly delineate platform-specific guidance.
Backup Create backup policies via REST API in Azure Backup ...up/backup-azure-arm-userestapi-createorupdatepolicy.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Windows Timezones
Summary
The documentation page demonstrates a subtle Windows bias primarily through the use of 'Pacific Standard Time' as the default timezone in example request bodies and responses, which is a Windows-specific timezone identifier. This is used alongside 'UTC', but 'Pacific Standard Time' appears first and is repeated in multiple examples. There are no explicit references to Windows tools, PowerShell, or command-line examples, and the REST API usage is platform-agnostic. However, the use of Windows timezone nomenclature may cause confusion for Linux users, who typically use IANA timezones (e.g., 'America/Los_Angeles').
Recommendations
  • Clarify in the documentation which timezone formats are supported (Windows vs IANA) and provide guidance for Linux users.
  • Provide example request bodies using both Windows and IANA timezone formats, or explicitly state if only Windows timezones are supported.
  • Add a note or link to a conversion table between Windows and IANA timezones.
  • Ensure that examples do not default to Windows-centric identifiers unless required by the API, and if so, explain the rationale.
  • If the API only supports Windows timezones, recommend a method for Linux users to convert IANA timezones to Windows timezones.
Backup Restore Azure Disks using Azure Data Protection REST API ...backup-azure-dataprotection-use-rest-api-restore-disks.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by mentioning Windows-centric tools (Azure PowerShell) before Linux-friendly alternatives (Azure CLI) and by not providing any OS-specific command-line examples for either platform. While both Azure PowerShell and Azure CLI are referenced, no concrete examples are given for either, and there is no mention of Linux-specific patterns, tools, or considerations. The REST API usage is platform-neutral, but the introductory section lists Windows tools first and does not provide parity in example walkthroughs for Linux users.
Recommendations
  • Provide explicit examples using both Azure PowerShell and Azure CLI, with clear instructions for running CLI commands on Linux and macOS.
  • When listing options, alternate or balance the order (e.g., mention Azure CLI before PowerShell in some places, or group them together).
  • Add a section or note highlighting that the REST API can be used from any OS, and provide sample scripts or curl commands for Linux/macOS users.
  • Include troubleshooting or environment setup notes for Linux users (e.g., authentication, installing Azure CLI, using bash scripts).
  • Ensure parity in documentation by offering step-by-step guides for both Windows and Linux command-line environments.
Backup Integrate Microsoft Defender's ransomware alerts to protect Azure Backup recovery points ...up-azure-integrate-microsoft-defender-using-logic-apps.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Azure Virtual Machines without specifying or providing examples for Linux VMs. All workflow steps, permissions, and alerting mechanisms are described in a generic Azure context, but there is no mention of Linux-specific considerations, tools, or examples. The integration assumes familiarity with Microsoft Defender for Cloud and Office 365, both of which are more commonly used in Windows-centric environments. No Linux command-line, automation, or alerting examples are provided, and there is no discussion of Linux-specific ransomware detection or backup nuances.
Recommendations
  • Explicitly state support for both Windows and Linux Azure VMs if applicable.
  • Provide Linux-specific examples for deploying and managing Azure Backup and Defender integrations (e.g., using Azure CLI or Bash).
  • Include references to Linux ransomware detection capabilities within Defender for Cloud.
  • Offer guidance on configuring email alerts and workflow automation for Linux administrators, possibly using non-Office 365 mail systems.
  • Mention any differences in backup retention, policy suspension, or recovery point handling for Linux VMs.
Backup Manage SQL server databases in Azure VMs using Azure Backup via CLI ...ob/main/articles/backup/backup-azure-sql-manage-cli.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently refers to SQL Server databases running on Azure VMs, implicitly assuming Windows-based SQL Server deployments. There is no mention of Linux-based SQL Server VMs, nor are there any examples or notes about differences when using SQL Server on Linux. All resource and container naming conventions (e.g., mssqlserver) and operational instructions are tailored to Windows SQL Server, with no guidance for Linux users.
Recommendations
  • Explicitly mention support for SQL Server on Linux VMs, if applicable, and clarify any differences in backup/restore operations.
  • Provide examples or notes for managing SQL Server on Linux VMs, including any differences in resource/container naming or CLI usage.
  • Add a section or callout highlighting platform-specific considerations (Windows vs. Linux) for SQL Server in Azure VMs.
  • Ensure terminology and instructions are inclusive of both Windows and Linux SQL Server deployments.
  • If certain features are Windows-only, clearly state this and provide alternatives or workarounds for Linux users.
Backup Back Up an Azure Virtual Machine with Azure Extended Zones Portal ...ain/articles/backup/backup-azure-vms-extended-zones.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page generally avoids OS-specific bias except in the 'Install the VM agent' section, where Windows instructions are listed first and in more detail, including explicit download links and file paths. Windows installation steps use a direct MSI installer and reference Windows file locations, while Linux instructions are less detailed and refer to distribution repositories without specific commands or examples. No PowerShell or CLI examples are present, and the portal-based workflow is OS-neutral.
Recommendations
  • Present Linux and Windows agent installation instructions with equal detail and prominence, possibly side-by-side or in separate subsections.
  • Provide explicit Linux installation commands (e.g., apt, yum, zypper) for common distributions, similar to the Windows MSI link.
  • List Linux instructions before Windows, or alternate the order in different documentation sections to avoid implicit prioritization.
  • Include troubleshooting and verification steps for Linux agent installation, analogous to the Windows file path and version check.
  • Add links to official Linux agent documentation and update instructions, matching the Windows agent update guidance.
Backup Perform actions using Backup center in Azure Backup ...ocs/blob/main/articles/backup/backup-center-actions.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
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 consistently prioritizing Azure Virtual Machine (VM) backup scenarios, which are typically associated with Windows workloads, and referencing VM backup examples before Linux or cross-platform equivalents. There is a lack of explicit Linux-specific examples, such as restoring or backing up Linux VMs, and no mention of Linux-specific tools, commands, or considerations. The documentation also omits PowerShell or Windows tool references, but the overall pattern still favors Windows-centric scenarios.
Recommendations
  • Add explicit examples and instructions for backing up and restoring Linux VMs in Azure, including any differences in process or options compared to Windows VMs.
  • Include references to Linux tools (such as CLI commands, shell scripts) where relevant, and provide parity with any Windows/PowerShell instructions.
  • Ensure screenshots and walkthroughs show both Windows and Linux VM scenarios, or clarify that the process applies equally to both.
  • Mention any Linux-specific considerations (e.g., file system types, application consistency, agent installation) in backup and restore workflows.
  • Review linked articles to ensure Linux parity and cross-platform inclusivity.
Backup Support matrix for Backup center for Azure Backup ...b/main/articles/backup/backup-center-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by 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 equivalents or without explicit mention of Linux support. Windows backup tools are referenced (MARS, MABS, DPM) without Linux alternatives, and examples or scenarios for Linux VMs or Linux-specific backup agents are missing.
Recommendations
  • Explicitly mention support for Linux-based Azure VMs and workloads where applicable.
  • Include Linux-specific backup scenarios and tools in the supported workloads and examples.
  • Add parity for backup agents and servers available for Linux, or clarify limitations if Linux alternatives do not exist.
  • Ensure that workload lists do not prioritize Windows workloads over Linux; consider alphabetical or platform-neutral ordering.
  • Reference documentation for Linux backup procedures and support matrices alongside Windows-focused links.
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias in its discussion of encryption for Azure VM backups. Specifically, it mentions BitLocker for Windows VMs first and provides more detail about SQL Server (a Microsoft/Windows-centric database) and its TDE encryption and restore process, without equivalent detail for Linux workloads or databases. The Linux equivalent (DM-Crypt) is mentioned only as an aside, with no further explanation or links. There are no Linux-specific examples, tools, or restore instructions provided.
Recommendations
  • Provide equal detail for Linux VM encryption, including links to DM-Crypt documentation and examples of restoring encrypted Linux VM backups.
  • Include examples or references for restoring backups of Linux workloads/databases, such as MySQL or PostgreSQL, especially when encrypted.
  • When listing encryption technologies, avoid listing Windows tools first; instead, present both Windows and Linux options together or in parallel.
  • Add Linux-specific FAQ entries or troubleshooting steps for common encryption scenarios.
Backup Back up Azure Managed Disks using Azure CLI .../blob/main/articles/backup/backup-managed-disks-cli.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation is largely cross-platform, using Azure CLI commands that work on both Windows and Linux. However, there are subtle signs of Windows bias: variable assignment examples use PowerShell syntax (e.g., $DiskId = ...), which is not valid in Bash or other Unix shells. Additionally, references to PowerShell documentation (e.g., 'backup-managed-disks-ps.md') are present in the 'Next steps' and 'Assign permissions' sections, and are mentioned before CLI or REST API equivalents. There are no explicit Linux-only examples or Bash shell variable assignments, and the documentation does not clarify shell differences when assigning variables.
Recommendations
  • Provide variable assignment examples in both PowerShell and Bash syntax, or use shell-agnostic approaches where possible.
  • When referencing platform-specific documentation (e.g., PowerShell), ensure CLI and REST API equivalents are mentioned first or equally.
  • Add notes clarifying that Azure CLI commands are cross-platform, and provide guidance for both Windows (PowerShell/CMD) and Linux/macOS (Bash) users.
  • Avoid using PowerShell-specific syntax in generic CLI documentation, or clearly indicate which shell the example is for.
  • Consider including a short section or callout on how to adapt examples for Bash vs. PowerShell environments.
Backup Tutorial - Configure vaulted backup for Azure Blobs using Azure Backup ...main/articles/backup/blob-backup-configure-tutorial.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by listing Azure PowerShell as the first method for restoring Azure Blobs, ahead of Azure CLI and REST API. This ordering subtly prioritizes Windows-centric tooling. There are no explicit Linux examples, nor is there mention of Linux-specific tools or shell commands. However, Azure CLI is referenced, which is cross-platform, and REST API instructions are included.
Recommendations
  • List Azure CLI examples before or alongside Azure PowerShell to avoid implying Windows-first workflows.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Provide example commands for both Azure PowerShell and Azure CLI in the main tutorial, not just in related content.
  • Include a note or section for Linux/macOS users, highlighting any platform-specific considerations or best practices.
  • Ensure that screenshots, if any, represent both Windows and Linux environments.
Backup Manage Azure Files backups with the Azure CLI ...ocs/blob/main/articles/backup/manage-afs-backup-cli.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is largely cross-platform, focusing on Azure CLI commands that work on both Windows and Linux. However, there is evidence of Windows bias: (1) Example output for the Vault-Standard tier backup policy creation shows a Windows file path (C:\Users\testuser\Downloads\CLIForAFS\azure-cli>) and a Windows-style command prompt, (2) There is no mention of Linux-specific shell usage or file paths, and (3) No explicit Linux/Bash examples are provided, nor is there guidance for Linux users on file redirection or environment setup. The references to PowerShell and Azure PowerShell are present but only as alternatives, not in the main content.
Recommendations
  • Provide example outputs and command prompts for both Windows (cmd/PowerShell) and Linux (bash), e.g., show file redirection using '>' in both environments.
  • Include notes or sections for Linux users, such as how to prepare the environment, where files are stored, and how to run Azure CLI commands in bash.
  • Avoid showing only Windows file paths in example outputs; use generic or cross-platform paths, or alternate between Windows and Linux examples.
  • Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and link to platform-specific setup guides.
  • Where alternative tools (PowerShell, REST API) are mentioned, ensure parity by linking to Linux/Bash equivalents or documentation.
Backup Manage and monitor SQL Server DBs on an Azure VM .../articles/backup/manage-monitor-sql-database-backup.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively discusses managing and monitoring SQL Server databases on Azure VMs without specifying or providing examples for Linux-based SQL Server deployments. All instructions, screenshots, and terminology implicitly assume a Windows environment (e.g., 'SQL in Azure VM', 'workload extension', 'Resiliency' portal features), and there are no references to Linux-specific tools, commands, or considerations. While Azure CLI and REST API are mentioned, no examples or guidance are provided for Linux users, nor is there any mention of Linux-specific SQL Server management nuances.
Recommendations
  • Explicitly state whether the instructions apply to both Windows and Linux SQL Server VMs, or clarify any limitations.
  • Add Linux-specific examples, including screenshots and step-by-step instructions for managing SQL Server on Linux VMs.
  • Include references to Linux tools and patterns (e.g., systemd services, Linux file paths, relevant shell commands) where applicable.
  • Provide parity in CLI and REST API usage examples, showing how to execute tasks from both Windows and Linux environments.
  • Mention any differences in backup, restore, and monitoring workflows for SQL Server on Linux VMs, if they exist.
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page focuses exclusively on Microsoft-centric backup tools (MARS Agent, MABS, DPM-A), which are Windows-only solutions. There is no mention of Linux backup agents, Linux-compatible utilities, or examples for Linux environments. All described workflows and architectures assume the use of Windows-based backup software, omitting Linux parity and guidance.
Recommendations
  • Include information about Linux-compatible backup agents or workflows, if available.
  • Provide examples or guidance for performing offline backups from Linux systems, including recommended utilities and disk preparation steps.
  • Clarify whether Azure Data Box and Import/Export workflows can be used from Linux servers, and if so, document the process and any required tools.
  • Add a section comparing Windows and Linux support for offline backup, highlighting any limitations or differences.
  • If Linux is not supported, explicitly state this to inform users and suggest alternative solutions.
Backup Query your backups using Azure Resource Graph (ARG) ...les/backup/query-backups-using-azure-resource-graph.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell as the first automation client for Azure Resource Graph queries, with CLI and SDK mentioned afterward. No Linux-specific tools or shell examples (e.g., Bash) are provided, and PowerShell is referenced before cross-platform alternatives. However, the sample queries themselves are platform-agnostic (Kusto), and Azure CLI is mentioned, which is available on Linux. There are no explicit Windows-only tools or missing Linux examples, but the ordering and emphasis favor Windows/PowerShell.
Recommendations
  • List Azure CLI before PowerShell when mentioning automation clients, as CLI is cross-platform and widely used on Linux.
  • Include explicit Bash shell examples for running ARG queries using Azure CLI to demonstrate Linux parity.
  • Clarify that both PowerShell and CLI are cross-platform, and provide links to Linux installation guides for each.
  • Add a note or section highlighting usage from Linux environments, including sample commands and troubleshooting tips.
Backup Quickstart - Configure vaulted backup for Azure Blobs using Azure CLI .../main/articles/backup/quick-blob-vaulted-backup-cli.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
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 'create a backup vault' link points to a PowerShell guide, and the 'Next step' section lists Azure PowerShell before Azure CLI, potentially suggesting a Windows-first approach. There is no explicit Linux example or mention of Linux-specific tools, but the primary focus is on Azure CLI, which is cross-platform.
Recommendations
  • Ensure that all referenced guides (such as 'create a backup vault') include both Azure CLI and PowerShell instructions, or link to CLI-first documentation when CLI is the focus.
  • In the 'Next step' section, list Azure CLI before Azure PowerShell to avoid Windows-first ordering.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide any Linux-specific notes if relevant.
  • Audit included files (e.g., blob-backup-create-policy-cli.md) to confirm they do not contain Windows-specific commands or assumptions.
  • Consider adding a section or note for Linux users, highlighting cross-platform compatibility and any OS-specific considerations.
Backup Troubleshoot SAP HANA databases instance backup errors ...cles/backup/sap-hana-database-instance-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
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 troubleshooting steps in a generic way, but does not provide any OS-specific examples, commands, or guidance. There is no mention of Linux-specific tools, commands, or troubleshooting patterns, despite SAP HANA commonly running on Linux. No PowerShell or Windows-only tools are referenced, but the lack of Linux parity (e.g., CLI commands, Linux disk management, or filesystem troubleshooting) is notable. The examples and recommended actions are platform-agnostic but implicitly assume Windows familiarity by omitting Linux-specific guidance.
Recommendations
  • Add explicit Linux troubleshooting steps and examples, such as Azure CLI commands for role assignment and disk management.
  • Include references to Linux disk and filesystem management tools (e.g., lsblk, mount, parted) where relevant.
  • Clarify that SAP HANA typically runs on Linux and provide OS-specific guidance for common errors (e.g., how to check supported filesystems, move data between volumes, or handle disk attach limits in Linux).
  • Provide example scripts or commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) where role assignment or resource management is required.
  • Mention Linux-specific backup and restore considerations, such as SELinux/AppArmor, systemd services, or permissions.
Backup Restore SAP HANA database instances on Azure VMs ...articles/backup/sap-hana-database-instances-restore.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently refers to 'Azure VMs' and restoration workflows via the Azure portal, but does not specify or provide examples for Linux-based SAP HANA deployments, which are the standard for SAP HANA. There are no explicit Linux command-line examples (e.g., bash, Linux tools), nor is there mention of OS-specific steps for Linux, even though SAP HANA is almost exclusively run on Linux. The only script reference is generic ('PowerShell or CLI script'), with no concrete Linux CLI (bash) examples or instructions. The documentation assumes familiarity with Azure portal workflows, which may be more familiar to Windows administrators.
Recommendations
  • Explicitly mention that SAP HANA runs on Linux and clarify any OS-specific steps for Linux VMs.
  • Provide Linux shell (bash) command examples for mounting disks and restoring databases, in addition to Azure CLI and PowerShell.
  • Include instructions or references for Linux tools (e.g., mount, fdisk, SAP HANA command-line utilities) where relevant.
  • Ensure parity by showing both PowerShell and bash/CLI examples for permission assignments and disk operations.
  • Clarify any differences in workflow or prerequisites for Linux-based SAP HANA deployments on Azure.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-aks.md ...ure-docs/blob/main/articles/backup/quick-backup-aks.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 using Azure Portal (GUI) instructions for configuring AKS backups, which is most commonly accessed from Windows environments. There are no command-line examples (e.g., Azure CLI, Bash, or PowerShell) for Linux users in the main configuration steps. Only in the 'Next step' section is Azure CLI mentioned, and even then, no example is provided. There is no mention of Linux-specific tools, shell commands, or parity for users who prefer or require non-GUI workflows.
Recommendations
  • Add step-by-step Azure CLI commands for configuring AKS backups alongside the portal instructions.
  • Include Bash shell examples for Linux users where applicable.
  • Explicitly mention that the Azure Portal is cross-platform, but provide alternatives for users who prefer command-line interfaces.
  • Ensure that any screenshots or instructions do not assume a Windows environment (e.g., file paths, UI conventions).
  • Provide links to both Windows and Linux command-line documentation where relevant.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-sap-hana-database-instance-restore.md ...les/backup/quick-sap-hana-database-instance-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 focuses exclusively on restoring SAP HANA using the Azure portal, without providing any platform-specific examples or guidance. However, it implicitly assumes a Windows-centric workflow by omitting any mention of Linux-specific tools, commands, or restoration patterns, despite SAP HANA commonly running on Linux. There are no CLI, shell, or Linux-native instructions, and no parity for Linux administrators is demonstrated.
Recommendations
  • Add explicit instructions and examples for restoring SAP HANA on Linux, including relevant CLI commands (e.g., Azure CLI, Bash) and Linux mount procedures.
  • Mention and link to Linux-specific troubleshooting steps or tools, such as using native Linux file system commands to mount restored disks.
  • Clarify platform requirements and provide guidance for both Windows and Linux environments, ensuring that Linux administrators have equal clarity and support.
  • If PowerShell or Windows tools are referenced elsewhere, ensure equivalent Linux alternatives are documented and presented with equal prominence.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/scripts/disable-soft-delete-for-file-shares.md .../backup/scripts/disable-soft-delete-for-file-shares.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 bias towards Windows environments by using Windows-style file paths (e.g., .\rqbody-disableSoftDelete.json) in all command examples and omitting Linux/macOS equivalents. There are no bash or shell examples, and the instructions implicitly assume a Windows shell context, which may confuse or hinder Linux users.
Recommendations
  • Provide equivalent command examples using Linux/macOS shell syntax (e.g., ./rqbody-disableSoftDelete.json instead of .\rqbody-disableSoftDelete.json).
  • Explicitly mention cross-platform compatibility of armclient and clarify any OS-specific installation or usage steps.
  • Add notes or tabs for both Windows and Linux/macOS command-line usage to ensure parity and clarity for all users.
  • Include instructions for verifying prerequisites and environment setup on Linux/macOS.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Azure portal-based workflows and does not mention or provide examples for command-line or automation approaches using either Windows (PowerShell) or Linux (CLI). However, the absence of references to Linux tools (such as Azure CLI or Bash) and the lack of parity in example coverage may implicitly favor Windows users, as Azure documentation often defaults to PowerShell or portal instructions, which are more familiar to Windows administrators.
Recommendations
  • Add explicit examples for configuring, restoring, and managing Elastic SAN backup using Azure CLI commands, which are cross-platform and widely used on Linux.
  • Include links to relevant Azure CLI documentation for backup and restore operations.
  • Where possible, provide Bash script snippets for automation scenarios alongside portal instructions.
  • Clarify that all operations can be performed from Linux or macOS environments using Azure CLI, not just from the portal or PowerShell.
  • Ensure future documentation updates maintain parity between Windows and Linux tooling and examples.