755
Total Pages
562
Linux-Friendly Pages
193
Pages with Bias
25.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

520 issues found
Showing 276-300 of 520 flagged pages
Backup Create and use private endpoints for Azure Backup ...re-docs/blob/main/articles/backup/private-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Most automation and scripting examples are provided using PowerShell, with explicit references to uploading and running .ps1 scripts in the Azure Cloud Shell (which defaults to PowerShell). File paths use Windows conventions (e.g., C:\<filepath>), and there are no Bash, CLI, or Linux/macOS shell equivalents for key tasks such as role creation, DNS entry management, or private endpoint approval. The documentation also references Windows-centric tools (MARS agent, DPM server) and patterns before mentioning alternatives. Linux/macOS users are left to infer how to adapt these steps, creating friction and potential confusion.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell for all automation and scripting tasks, especially for role/permission creation, DNS entry management, and private endpoint approval.
  • Use cross-platform file path conventions or clarify when Windows paths are used; provide Linux/macOS equivalents.
  • Explicitly mention that Cloud Shell supports Bash and provide instructions/scripts for both Bash and PowerShell.
  • Reference Linux-compatible backup agents and tools where relevant, or clarify platform requirements.
  • Ensure that all critical steps (such as creating resources, managing permissions, and DNS configuration) have Linux/macOS-friendly instructions and examples.
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Servers with a Bicep file ...ackup/quick-backup-postgresql-flexible-server-bicep.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing only PowerShell deployment instructions for the Bicep template and referencing Azure PowerShell for subsequent operations. There are no CLI (az) or Bash examples, and the instructions for pasting code reference Windows shell conventions. This creates friction for Linux/macOS users who typically use Bash and Azure CLI.
Recommendations
  • Add Azure CLI (az deployment group create) examples for deploying the Bicep template.
  • Include Bash shell instructions for copying and running commands.
  • Reference both PowerShell and CLI documentation in 'Next steps' and throughout the page.
  • Explicitly mention cross-platform compatibility and provide links to Linux/macOS setup guides.
Backup Quickstart - Resource Manager template VM Backup .../blob/main/articles/backup/quick-backup-vm-template.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The main deployment example uses Azure PowerShell exclusively, with no equivalent Azure CLI or Bash example provided. The template itself is described as deploying a Windows VM, and PowerShell commands are used for both deployment and cleanup. Linux/macOS users are only briefly mentioned as being able to use Azure CLI or REST API, but no concrete examples or guidance are given for those platforms.
Recommendations
  • Add step-by-step Azure CLI and Bash examples for template deployment and resource cleanup, shown alongside PowerShell examples.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users.
  • Include a note or section on how to deploy Linux VMs with the template, or link to Linux-specific templates.
  • Reorder examples so that CLI/Bash instructions are presented before or alongside PowerShell, not after.
  • Ensure all referenced scripts and commands have Linux/macOS equivalents.
Backup Quickstart - Configure vaulted backup for an Azure Kubernetes Service (AKS) cluster using Azure Backup via Azure Resource Manager ...ob/main/articles/backup/quick-kubernetes-backup-arm.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell deployment instructions for the ARM template, with no equivalent Azure CLI or Bash example for Linux/macOS users. Prerequisites and next steps also emphasize PowerShell first, and do not offer Linux-native alternatives for the main deployment workflow.
Recommendations
  • Add Azure CLI and Bash examples for deploying the ARM template, shown alongside or before PowerShell.
  • Explicitly mention that Azure CLI is cross-platform and provide installation instructions for Linux/macOS.
  • Ensure that all critical workflows (deployment, restore, management) have Linux/macOS-friendly instructions and examples.
  • Reorder next steps to present CLI and PowerShell equally, or alternate which is listed first.
Backup Soft delete for SQL server in Azure VM and SAP HANA in Azure VM workloads ...articles/backup/soft-delete-sql-saphana-in-azure-vm.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for the Azure portal and Azure PowerShell, with all CLI examples using PowerShell cmdlets. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or REST API. The PowerShell instructions are presented as the only scripting option, and the portal instructions do not mention OS-specific considerations, but PowerShell is Windows-centric.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, enabling Linux/macOS users to perform soft delete operations from the command line.
  • Include REST API references or examples for advanced users who may not use PowerShell.
  • Explicitly state OS compatibility for each method (portal, PowerShell, CLI) and recommend alternatives for non-Windows environments.
  • Reorder or parallelize examples so that PowerShell and CLI/REST are presented together, not with PowerShell first.
  • Add a note clarifying that PowerShell can be installed on Linux/macOS, but Azure CLI is the preferred cross-platform solution.
Backup Quickstart - Configure vaulted backup for Azure Data Lake Storage using ARM or Bicep template ...ata-lake-storage-backup-configure-quickstart-arm-bicep.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell deployment examples for both ARM and Bicep templates, with no Azure CLI, Bash, or Linux-native instructions. PowerShell is a Windows-centric tool, and while Azure Cloud Shell supports PowerShell, many Linux/macOS users prefer Azure CLI or Bash. The lack of cross-platform deployment examples creates friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI deployment instructions for both ARM and Bicep templates.
  • Provide Bash script examples for template deployment.
  • Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and clarify that PowerShell is not required.
  • List Azure CLI instructions before or alongside PowerShell to avoid Windows-first perception.
Backup Create backup policies via REST API in Azure Backup ...up/backup-azure-arm-userestapi-createorupdatepolicy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation consistently uses 'Pacific Standard Time' as the default time zone in example request bodies, which is a Windows-specific time zone identifier. This is shown before 'UTC', which is the cross-platform standard. No PowerShell, Windows tools, or Windows-only patterns are present, and all examples are REST API calls (platform-agnostic). However, the repeated use of 'Pacific Standard Time' may cause friction for Linux/macOS users, as their systems typically use IANA time zones (e.g., 'America/Los_Angeles') and may not recognize Windows time zone names.
Recommendations
  • Add a note clarifying that time zone identifiers must use Windows time zone names, and provide a mapping or reference to convert IANA time zones to Windows time zones.
  • Show examples using both 'Pacific Standard Time' and 'UTC', and recommend 'UTC' for maximum cross-platform compatibility.
  • Consider including a table or link to resources for converting between Windows and IANA time zone identifiers.
  • Explicitly state any platform limitations or requirements for time zone values in the API.
Backup Create backup policies for Azure database for PostgreSQL - Flexible server using data protection REST API in Azure Backup ...base-postgresql-flex-use-rest-api-create-update-policy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy
Summary
The documentation page contains a notable Windows bias by referencing the 'default PowerShell object' for PostgreSQL - Flexible servers as the baseline for backup scheduling and retention. There are no Linux/macOS-specific examples, nor is there mention of equivalent Linux tools or command-line patterns (such as Bash, curl, or Azure CLI). The only tooling context provided is PowerShell, which is primarily associated with Windows environments.
Recommendations
  • Replace or supplement references to 'default PowerShell object' with cross-platform alternatives, such as Azure CLI commands or REST API calls using curl.
  • Provide explicit examples for Linux/macOS users, such as sample curl commands to invoke the REST API.
  • Clarify that PowerShell is not required and that the REST API can be accessed from any platform.
  • Add a section or note highlighting platform-agnostic approaches to policy creation and management.
Backup Troubleshoot encrypted Azure VM backup errors ...icles/backup/backup-azure-encrypted-vm-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias by referencing PowerShell as the only command-line automation method for configuring permissions and restoring VMs. There are no examples or instructions for Linux/macOS users (e.g., using Azure CLI or Bash), and PowerShell is mentioned before any cross-platform alternatives. This may create friction for users managing Azure VMs from non-Windows environments.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all PowerShell instructions, especially for permission configuration and VM restore operations.
  • Explicitly state that steps can be performed from Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
  • Ensure that automation and scripting guidance is platform-neutral or includes both Windows and Linux/macOS options.
  • Review all referenced links to confirm Linux parity in step-by-step guides.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is primarily focused on using the Azure Portal, which is cross-platform, but in the 'Install the VM agent' section, Windows instructions are given in detailed, step-by-step fashion (including download links, file paths, and verification steps), while Linux instructions are brief and lack concrete command examples. Windows instructions are listed first, and Linux instructions are less actionable for users unfamiliar with package management.
Recommendations
  • Provide explicit Linux command-line examples for installing/updating the Azure Linux agent (e.g., apt/yum commands).
  • Include verification steps for Linux agent installation, such as checking agent version via command line.
  • Consider listing Linux instructions before or alongside Windows instructions to avoid implicit prioritization.
  • Clarify which steps are identical across platforms and which differ, to help users on macOS/Linux.
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific backup mechanisms (VSS) are described in detail, with Windows examples and terminology (VSS, PowerShell) presented before Linux equivalents. Linux instructions are less detailed, referencing custom scripts without concrete examples. PowerShell is mentioned for restore operations, but no Linux CLI or automation alternatives are provided. This may create friction for Linux users seeking parity in guidance and tooling.
Recommendations
  • Provide Linux CLI (az CLI, Bash) examples alongside PowerShell for backup and restore automation.
  • Include detailed Linux backup workflow examples, such as sample pre/post scripts for application consistency.
  • Present Windows and Linux instructions in parallel, rather than Windows-first.
  • Reference Linux-native tools (e.g., fsfreeze) with usage examples, not just brief mentions.
  • Clarify any differences in supported features or limitations between Windows and Linux VMs.
Backup Back Up Azure VMs with the Enhanced Policy ...in/articles/backup/backup-azure-vms-enhanced-policy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for configuring Enhanced backup policies, with step-by-step cmdlets and explanations. PowerShell is a Windows-centric tool, and no equivalent Bash or Linux shell examples are given. The CLI section is present, but it is less detailed and appears after the PowerShell section. There are no explicit Linux/macOS-specific instructions, nor are there notes about cross-platform usage for scripting or automation.
Recommendations
  • Add Bash/Linux shell scripting examples for key tasks, especially for configuring policies and scheduling backups.
  • Clarify that Azure CLI commands work cross-platform and provide sample Bash scripts for Linux/macOS users.
  • Reorder sections so that CLI examples appear before PowerShell, or present them side-by-side to avoid Windows-first bias.
  • Explicitly mention platform compatibility for each tool (Azure CLI, PowerShell) and link to installation guides for Linux/macOS.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., authentication, environment setup).
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Server with an Azure Resource Manager template .../backup/quick-backup-postgresql-flexible-server-arm.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell deployment instructions and referencing Azure PowerShell modules, with no mention of Azure CLI or Bash equivalents. The deployment example and next steps are PowerShell-centric, which may hinder Linux/macOS users who typically use Bash or Azure CLI.
Recommendations
  • Add Azure CLI and Bash examples for template deployment, showing equivalent commands.
  • Mention that PowerShell is available cross-platform, but clarify how Linux/macOS users can install and use it if preferred.
  • Provide links to Azure CLI documentation alongside PowerShell references.
  • Ensure next steps include both PowerShell and CLI/Bash restore instructions.
Backup Quickstart - Resource Manager template VM Backup .../blob/main/articles/backup/quick-backup-vm-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing Azure PowerShell examples for deploying and cleaning up the ARM template, with no equivalent Azure CLI or Bash examples. The template itself is described as deploying a Windows VM, and PowerShell is presented as the primary method for deployment and backup operations. Linux/macOS users must infer how to adapt the instructions for their platforms, creating friction.
Recommendations
  • Add Azure CLI and Bash examples for deploying the ARM template and cleaning up resources.
  • Explicitly mention cross-platform alternatives (Azure CLI, Bash) alongside PowerShell in each procedural section.
  • Provide a template variant or instructions for deploying a Linux VM, or clarify how to modify the template for Linux workloads.
  • Reorder or parallelize example sections so Windows and Linux approaches are presented together, not Windows-first.
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell scripts for key troubleshooting actions (such as finding Recovery Services vaults and undeleting file shares), without providing equivalent Bash, Azure CLI, or Linux/macOS instructions. The scripts and tools mentioned are Windows-centric, and there are no Linux/macOS alternatives or parity in examples.
Recommendations
  • Provide Azure CLI or Bash script equivalents for all referenced PowerShell scripts, and link to them alongside the PowerShell versions.
  • Explicitly mention that the troubleshooting steps can be performed on Linux/macOS using Azure CLI, and provide example commands.
  • Add guidance for Linux/macOS users on how to perform undelete and vault discovery operations without relying on PowerShell.
  • Ensure screenshots and portal instructions are OS-agnostic or clarify any OS-specific requirements.
Backup About the Azure Virtual Machine restore process ...cs/blob/main/articles/backup/about-azure-vm-restore.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Restore an encrypted VM' scenario, which explicitly mentions using PowerShell and links only to Windows-specific encrypted VM guides. There are no references to Linux VM encryption restore processes or Linux-specific tooling, and the examples and links focus on Windows VMs first. This may create friction for Linux users seeking parity in restore guidance.
Recommendations
  • Add equivalent instructions and links for restoring encrypted Linux VMs, including any required tools (e.g., Azure CLI, Bash scripts) and Linux-specific considerations.
  • Ensure that restore scenarios and examples are presented for both Windows and Linux VMs, or clarify when a scenario is Windows-only.
  • Include references to Linux documentation in the 'Restore an encrypted VM' row and throughout the page where applicable.
  • Where PowerShell is mentioned, also provide Azure CLI or Bash alternatives for Linux/macOS users.
Backup Azure Backup - Archive tier overview ...docs/blob/main/articles/backup/archive-tier-support.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists supported clients as Azure portal, PowerShell, and CLI, with PowerShell (a Windows-centric tool) mentioned before CLI. There are no explicit Linux/macOS examples, nor are Linux-specific tools or workflows discussed. The documentation does not provide parity in examples or guidance for Linux users, and the ordering suggests a Windows-first approach.
Recommendations
  • Provide explicit Linux/macOS examples using Azure CLI, including command-line instructions for common archive tier operations.
  • Clarify that Azure CLI is cross-platform and highlight its usage for Linux/macOS users.
  • Include screenshots or walkthroughs from Linux/macOS environments where relevant.
  • Ensure that CLI instructions are given equal prominence to PowerShell, or list CLI before PowerShell to avoid Windows-first bias.
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page lists multiple automation methods, including PowerShell, CLI, REST API, and SDKs, but PowerShell is consistently mentioned first and is emphasized in key automation scenarios. Example workflows and guidance reference PowerShell and Runbooks prominently, with no explicit Linux/bash examples or parity in scripting approaches. While CLI and SDKs are mentioned, practical examples and step-by-step guidance focus on PowerShell, which is most familiar to Windows users.
Recommendations
  • Provide explicit bash/CLI examples alongside PowerShell for each automation scenario.
  • Include sample scripts using Azure CLI and/or Python SDK for Linux/macOS users.
  • Ensure that video walkthroughs and linked resources demonstrate both PowerShell and CLI-based automation.
  • Reorder automation method lists to avoid always listing PowerShell first.
  • Highlight cross-platform compatibility and note any differences or limitations for Linux/macOS users.
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The glossary page shows moderate Windows bias, primarily through frequent references to Windows-specific backup technologies (VSS, DPM, MABS, MARS agent), and by listing Windows tools (Azure PowerShell) before cross-platform alternatives (Azure CLI). Linux backup patterns are mentioned only briefly (e.g., 'pre or post scripts for Linux'), with no links or examples. Most workload-specific terms and backup agents described are Windows-centric, and the glossary lacks Linux/macOS-specific backup terminology or examples.
Recommendations
  • Add glossary entries for Linux/macOS backup agents, patterns, and technologies (e.g., mention native Linux snapshot tools, Azure Backup support for Linux workloads).
  • Provide links to Linux-specific documentation where relevant (e.g., how Azure Backup interacts with Linux VMs, file systems, and snapshot mechanisms).
  • Ensure parity in examples and tool references, listing Azure CLI before or alongside Azure PowerShell, and clarifying cross-platform support.
  • Expand explanations for Linux backup consistency (e.g., detail how pre/post scripts work, reference Linux backup best practices).
Backup Configure Vaulted Backup for Azure Data Lake Storage using Azure portal, PowerShell, or Azure CLI ...les/backup/azure-data-lake-storage-configure-backup.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parallel instructions for Azure portal, PowerShell, and Azure CLI. However, the PowerShell section is notably more detailed, with step-by-step cmdlets and explanations, while the Azure CLI section is less comprehensive and lacks equivalent depth. PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. Additionally, PowerShell is mentioned before Azure CLI in the title and throughout, indicating a 'Windows-first' approach.
Recommendations
  • Expand the Azure CLI section to match the detail and step-by-step guidance provided in the PowerShell section, including more example commands and explanations.
  • Add explicit notes or links for Linux/macOS users, such as installation instructions for Azure CLI and troubleshooting tips for non-Windows environments.
  • Consider providing Bash or shell script examples for common tasks, where applicable.
  • Ensure that CLI examples are as discoverable and prominent as PowerShell examples, possibly by alternating their order or grouping them together.
  • Clarify that PowerShell is available cross-platform, but highlight CLI as the preferred tool for Linux/macOS users.
Backup Back up Azure Kubernetes Service by using Azure Backup ...cles/backup/azure-kubernetes-service-cluster-backup.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It repeatedly references Azure PowerShell as an alternative to the Azure portal for backup and restore operations, but does not mention or provide examples for Azure CLI (which is cross-platform and preferred on Linux/macOS). The 'Next steps' section lists PowerShell before any Linux-friendly alternatives. There are no explicit Linux/macOS-specific instructions or parity examples, and the only command-line example shown is 'kubectl', which is cross-platform, but no Azure CLI usage is demonstrated.
Recommendations
  • Add Azure CLI instructions and examples alongside or before Azure PowerShell references for all backup and restore operations.
  • In 'Next steps', list Azure CLI documentation links before or alongside PowerShell, or clarify CLI parity.
  • Explicitly state that all steps can be performed on Linux/macOS using Azure CLI and kubectl, and provide sample commands.
  • Where screenshots are shown, ensure they do not imply Windows-only usage (e.g., avoid showing Windows-specific UI elements).
Backup Restore Azure Kubernetes Service (AKS) using Azure Backup ...les/backup/azure-kubernetes-service-cluster-restore.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by explicitly referencing Azure PowerShell as an alternative method for restoring AKS clusters, without mentioning or providing equivalent instructions for Linux/macOS users (e.g., Azure CLI or Bash). The only command-line example is PowerShell, and there is no guidance for Linux-native tools or workflows. The main walkthrough is GUI-based, but the only referenced automation path is Windows-centric.
Recommendations
  • Add equivalent instructions for restoring AKS clusters using Azure CLI (az), which is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that the restore process can be performed from Linux/macOS using Azure CLI, and provide links or examples.
  • If scripting is discussed, provide Bash and/or shell script examples alongside PowerShell.
  • Ensure any references to command-line tools do not prioritize Windows tools unless there is a technical limitation.
Backup Back up Azure Local virtual machines with MABS ...e-stack-hyperconverged-infrastructure-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with exclusive references to Windows tools (PowerShell, .exe installers), Windows-centric terminology (Hyper-V, VSS), and examples that only show Windows commands. Linux support is mentioned briefly and generically, with no concrete examples or step-by-step instructions for Linux VMs. All code samples, screenshots, and recovery procedures are Windows-specific, and there are no Linux/macOS equivalents or guidance for common Linux scenarios.
Recommendations
  • Add explicit Linux backup and recovery walkthroughs, including command-line examples for agent installation and recovery on Linux VMs.
  • Provide Linux-specific troubleshooting and prerequisites, such as supported distributions, required packages, and SELinux/AppArmor considerations.
  • Include screenshots or CLI output from Linux environments where relevant.
  • Clarify any differences in backup/restore workflows for Linux VMs, such as file-consistent vs. application-consistent backups.
  • Mention Linux limitations (e.g., only file-consistent snapshots) more prominently and offer guidance for Linux application backup.
  • If macOS is supported, add notes/examples for macOS as well.
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page for Azure Backup architecture demonstrates a notable Windows bias. It provides detailed backup scenarios and tooling for Windows environments (MARS agent, DPM, MABS), while explicitly stating that Linux machines aren't supported for direct backup with the MARS agent and omitting Linux-specific backup workflows. Windows tools and agents are mentioned exclusively and described in detail, with no Linux equivalents or alternatives presented. The structure and examples prioritize Windows solutions, leaving Linux and macOS users with limited guidance or options.
Recommendations
  • Clearly state Linux backup limitations and provide alternative solutions or workarounds for Linux environments.
  • Include documentation or links for backing up Linux machines, such as using Azure VM backup extension, third-party tools, or scripts.
  • Present backup scenarios for Linux and Windows side-by-side, or in parallel sections, to ensure parity.
  • Add examples and guidance for Linux VM backup, including supported agents, CLI commands, and recovery procedures.
  • Highlight any cross-platform tools or APIs that can be used for both Windows and Linux machines.
Backup Restore VMs by using the Azure portal using Azure Backup ...b/main/articles/backup/backup-azure-arm-restore-vms.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools (PowerShell) and patterns are mentioned repeatedly, especially for tasks like creating VMs from restored disks, restoring VMs with special network configurations, and post-restore steps. Windows examples (e.g., PowerShell, CMD commands, references to Windows-specific features like Hybrid Use Benefit and domain controllers) are provided, while Linux equivalents are either missing or referenced only briefly. Linux users are sometimes directed to generic Azure features (e.g., VMAccess extension), but step-by-step guidance or CLI/bash examples are lacking. Windows-centric links and terminology appear before or instead of Linux alternatives.
Recommendations
  • Add explicit Azure CLI and Bash examples for all restore scenarios, especially where PowerShell is currently referenced.
  • Provide Linux-specific guidance for restoring VMs, including handling SSH keys, cloud-init, and troubleshooting common Linux restore issues.
  • Ensure links to Linux documentation (e.g., restoring disks, attaching disks, network configuration) are present and prioritized alongside Windows links.
  • Include examples and screenshots for Linux VM restore flows in the Azure portal.
  • Clarify any differences in restore behavior or limitations for Linux VMs (e.g., extension handling, password resets, network configuration).