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 226-250 of 1604 flagged pages
Backup Automation in Azure Backup support matrix ...blob/main/articles/backup/backup-support-automation.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation consistently lists PowerShell as the first automation method for nearly every operation and workload, reflecting a Windows-centric approach. PowerShell examples are always present, even for workloads where CLI or REST API are more cross-platform. There is little mention of Linux-specific tools, patterns, or scripting environments (e.g., Bash, shell scripts), and no explicit Linux examples or guidance. The structure and example links reinforce PowerShell as the primary automation tool, which may disadvantage Linux users or those preferring non-Windows environments.
Recommendations
  • Alternate the order of PowerShell and CLI in tables and examples, or list CLI first for workloads where Linux is common (e.g., SAP HANA, PostgreSQL).
  • Add explicit Linux/Bash shell script examples for common automation scenarios, especially for VM, disk, and file operations.
  • Where PowerShell is referenced, clarify that Azure CLI commands work natively on Linux/macOS and provide equivalent Bash examples.
  • Include notes or sections on Linux automation best practices, such as using cron jobs, shell scripting, or integrating with Ansible.
  • Review example links to ensure parity between PowerShell and CLI, and avoid PowerShell-only deep dives.
  • Highlight cross-platform compatibility for REST API, Terraform, and other tools, and provide sample scripts for Linux environments.
GitHub Create Pull Request
Backup Back up the MABS server ...cs/blob/main/articles/backup/backup-the-mabs-server.md
High 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 for backing up the Microsoft Azure Backup Server (MABS) is heavily biased towards Windows environments. All examples, instructions, and tooling references are Windows-centric, including exclusive use of Windows command-line tools (psexec.exe, mountvol.exe, diskshadow.exe, Vssadmin), PowerShell commands, and Windows file paths. There is no mention of Linux equivalents, nor any guidance for performing these operations on non-Windows platforms. The documentation assumes the administrator is using Windows Server and Windows-based management tools throughout.
Recommendations
  • Explicitly state platform requirements and limitations at the top of the documentation, clarifying if MABS is Windows-only.
  • If Linux support is possible (e.g., for SQL Server, backup storage, or Azure agent), provide parallel instructions and examples for Linux environments.
  • Where possible, mention cross-platform alternatives to Windows tools (e.g., using native SQL backup commands, Azure CLI, or REST APIs from Linux).
  • Avoid using only Windows file paths and commands; include generic or Linux-compatible examples where applicable.
  • If MABS is strictly Windows-only, make this clear to avoid confusion for Linux administrators.
GitHub Create Pull Request
Backup Configure and manage backup for Azure Blobs using Azure Backup ...b/main/articles/backup/blob-backup-configure-manage.md
High 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 primarily describes backup configuration and management for Azure Blobs using the Azure portal, with references to Azure PowerShell and REST API. While Azure CLI is mentioned in the 'Related content' section, the main body of the documentation does not provide CLI examples or Linux-specific instructions. PowerShell is referenced before CLI, and there are no explicit Linux shell or cross-platform command examples. The instructions and screenshots are focused on the Azure portal, which is platform-agnostic, but the scripting and automation references favor Windows tools.
Recommendations
  • Include Azure CLI examples alongside PowerShell in the main documentation body, not just in 'Related content'.
  • Add explicit Linux shell instructions or notes where relevant, especially for automation scenarios.
  • Present CLI and PowerShell options together, or alternate which is shown first, to avoid Windows-first bias.
  • Reference cross-platform tools and patterns, such as Bash scripting, where applicable.
  • Ensure that all automation and scripting guidance is platform-neutral, or provide parity for Linux users.
GitHub Create Pull Request
Backup Overview of Azure Disk Backup ...docs/blob/main/articles/backup/disk-backup-overview.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows Server Failover Cluster is mentioned before Linux clusters in the cluster scenario example. Windows-specific technologies (Volume Shadow Copy Service, VSS) are referenced for application-consistent backup, with no Linux equivalent (such as fsfreeze or LVM snapshots) mentioned. There are no concrete Linux-specific examples, tools, or patterns provided, and no Linux command-line or scripting references (e.g., Bash, CLI) are present. The examples and scenarios tend to mention Windows first or exclusively, with Linux only as a secondary consideration.
Recommendations
  • Provide Linux-specific examples and scenarios, such as using Azure Disk Backup with Linux clusters (e.g., Pacemaker, Corosync) and Linux file systems.
  • Mention Linux tools and patterns for application-consistent backup (e.g., fsfreeze, LVM snapshots) alongside VSS for Windows.
  • Include references to Linux scripting or automation (e.g., Bash scripts, Azure CLI) in the 'Related content' or example sections.
  • Ensure parity in the order of mention: alternate between Windows and Linux or group them together, rather than listing Windows first.
  • Add troubleshooting or best practices sections for both Windows and Linux environments.
GitHub Create Pull Request
Backup Encrypt backup data by using customer-managed keys ...ob/main/articles/backup/encryption-at-rest-with-cmk.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. PowerShell is featured prominently and in detail throughout all procedural sections, often with more elaborate examples than Azure CLI. There are multiple warnings and notes about PowerShell-specific behaviors, and the use of PowerShell is recommended for key management tasks. The documentation references Windows-specific tools (e.g., BitLocker) before mentioning Linux equivalents (DM-Crypt), and PowerShell is often listed before CLI in tabbed instructions. There are no explicit Linux shell examples (e.g., bash scripts), nor is there discussion of Linux-specific considerations for backup encryption workflows.
Recommendations
  • Add bash and Linux shell script examples for all CLI procedures, demonstrating parity with PowerShell workflows.
  • Include explicit references to Linux environments and any unique considerations for Linux users (e.g., file permissions, integration with DM-Crypt, SELinux contexts).
  • Balance the order of examples in tabbed instructions, sometimes listing CLI or bash before PowerShell to avoid 'windows_first' bias.
  • Expand documentation of Linux backup agents and clarify limitations or alternatives to the MARS agent for Linux users.
  • Provide troubleshooting and FAQ sections that address Linux-specific scenarios and common issues.
GitHub Create Pull Request
Backup Install the Microsoft Azure Recovery Services (MARS) agent ...e-docs/blob/main/articles/backup/install-mars-agent.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased toward Windows environments. All instructions, examples, and prerequisites are specific to Windows, including references to Windows-only installers (.exe), Windows PowerShell, and Windows-specific tools (MABS, DPM). There are no Linux equivalents, examples, or mentions, and the documentation does not address cross-platform scenarios. The customer intent and all workflow steps assume the user is operating on Windows, with no guidance for Linux users.
Recommendations
  • Clearly state in the introduction that the MARS agent is only supported on Windows, and provide links to Linux backup solutions (e.g., Azure Backup for Linux VMs).
  • Add a comparison table or section that explains backup options for both Windows and Linux, including which agent or extension to use on each platform.
  • If possible, provide parity in documentation by including Linux backup workflows, or link to relevant Linux documentation.
  • Avoid using 'Windows machines' as the default context throughout; instead, specify platform limitations and alternatives.
  • Include a FAQ or guidance for users seeking to back up Linux machines, directing them to appropriate Azure solutions.
GitHub Create Pull Request
Backup Encrypt backup data in a Backup vault by using customer-managed keys ...backup/encryption-at-rest-with-cmk-for-backup-vault.md
High 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 step-by-step instructions and code samples for Azure portal, PowerShell, and Azure CLI. PowerShell examples are prominent and detailed, with explicit parameter lists and sample commands, while CLI examples are present but less detailed. There is a notable absence of Linux-specific shell examples (e.g., Bash scripts), and no mention of Linux-native tools or workflows. The documentation implicitly prioritizes Windows/PowerShell by presenting PowerShell examples before CLI, and by not acknowledging Linux environments or shell differences.
Recommendations
  • Add explicit Bash shell examples for all CLI commands, including environment variable usage and scripting patterns common on Linux.
  • Include notes or sections on running Azure CLI commands in Linux environments, addressing authentication, file paths, and shell differences.
  • Provide parity in example detail between PowerShell and CLI, ensuring CLI examples are as comprehensive and annotated as PowerShell ones.
  • Mention cross-platform compatibility for Azure CLI and clarify that all CLI commands work on Linux, macOS, and Windows.
  • Consider adding troubleshooting steps or tips specific to Linux environments (e.g., handling permissions, environment setup).
GitHub Create Pull Request
Backup Guidance and best practices ...s/blob/main/articles/backup/guidance-best-practices.md
High 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 demonstrates a Windows bias in several ways: examples and automation references prioritize PowerShell, Windows-centric tools (MARS agent, DPM/MABS) are mentioned exclusively or first, and there are no explicit Linux or cross-platform CLI examples. The guidance and scenarios focus on workloads and management patterns typical of Windows environments, with little attention to Linux-specific backup needs or tools.
Recommendations
  • Include CLI (az) examples alongside or before PowerShell examples for all automation scenarios.
  • Explicitly mention Linux workloads and provide guidance/examples for backing up Linux VMs and files.
  • Reference Linux-native backup agents or integration options (e.g., Azure Backup for Linux, integration with rsync, tar, etc.) where applicable.
  • Ensure that cross-platform tools and patterns (such as REST API, SDKs) are given equal prominence to Windows-specific tools.
  • Add sections or callouts for Linux-specific considerations (e.g., file system consistency, application-consistent backups for Linux apps).
  • When mentioning automation, alternate between PowerShell and CLI, or show both in parallel.
  • Review all tool references (MARS, DPM/MABS) and clarify their OS compatibility, or suggest Linux alternatives if available.
GitHub Create Pull Request
Backup Manage Backup vaults ...-docs/blob/main/articles/backup/manage-backup-vault.md
High 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 exhibits Windows bias primarily by referencing PowerShell as a method for moving Backup vaults before mentioning Azure CLI, and by not providing explicit Linux/bash examples or guidance. The use of 'PowerShell' as a named tool and the lack of parity in command-line examples for Linux users suggest a preference for Windows tooling and workflows.
Recommendations
  • Provide explicit bash/Azure CLI examples for all operations where PowerShell is mentioned, including full command syntax and usage notes for Linux/macOS environments.
  • When listing command-line options, mention Azure CLI before or alongside PowerShell, and clarify cross-platform compatibility.
  • Add screenshots or walkthroughs using Azure CLI in a Linux terminal for parity with portal and PowerShell instructions.
  • Include notes or links for installing and using Azure CLI on Linux/macOS.
  • Review all references to scripts and tools to ensure examples are not Windows-centric (e.g., avoid only referencing .ps1 scripts or Windows paths).
GitHub Create Pull Request
Backup What Azure Backup Server V3 RTM can back up .../backup/microsoft-azure-backup-server-protection-v3.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Azure Backup Server V3 RTM is heavily Windows-centric. The protection matrix almost exclusively lists Windows operating systems, Windows-based workloads (SQL Server, Exchange, SharePoint, Hyper-V), and Windows file systems (NTFS, ReFS). Linux is mentioned only briefly as a guest VM, with limited support (entire VM backup only, file-consistent snapshots), and there are no Linux-specific examples, tools, or recovery scenarios. Windows tools and patterns (e.g., VSS, NTFS, Windows Management Framework) are referenced throughout, with no Linux equivalents or parity.
Recommendations
  • Add explicit Linux workload support details, including supported distributions, file systems, and backup/recovery scenarios.
  • Provide Linux-specific examples for backup and recovery, including item-level recovery if supported.
  • Mention Linux tools and patterns (e.g., LVM snapshots, ext4/xfs file systems) where applicable.
  • Clarify limitations for Linux and provide guidance or alternatives for Linux users.
  • Ensure Linux is represented in the protection matrix with equal detail as Windows workloads.
  • If Azure Backup Server does not support Linux workloads beyond VM-level backup, state this clearly and suggest alternative Azure backup solutions for Linux.
GitHub Create Pull Request
Backup Manage telemetry settings in Microsoft Azure Backup Server (MABS) ...ure-docs/blob/main/articles/backup/manage-telemetry.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively references the Microsoft Azure Backup Server (MABS) console, which is a Windows-only application. All instructions and screenshots pertain to the Windows GUI, with no mention of Linux equivalents, command-line alternatives, or cross-platform considerations. There are no examples or guidance for managing telemetry settings on Linux systems, nor are any Linux tools or patterns referenced.
Recommendations
  • Clarify in the introduction that MABS is a Windows-only product, if applicable. If cross-platform support exists, include instructions for Linux environments.
  • Provide command-line alternatives (e.g., PowerShell, CMD, or CLI) for managing telemetry settings, and note whether these are available on Linux.
  • If telemetry management is possible via configuration files, document the file location and format for both Windows and Linux systems.
  • Add explicit statements about platform support and limitations, so Linux administrators are aware of their options.
  • If there is no Linux support, consider linking to equivalent Azure Backup solutions for Linux and their telemetry management documentation.
GitHub Create Pull Request
Backup MABS (Azure Backup Server) V3 UR1 protection matrix ...kup/microsoft-azure-backup-server-protection-v3-ur1.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. Windows workloads, tools, and filesystems (NTFS, VSS, ReFS) are mentioned exclusively or before Linux equivalents. Linux support is limited to guest VM backup with minimal detail, and there are no Linux-specific examples, recovery scenarios, or parity in feature descriptions. Windows tools and patterns (e.g., Volume Shadow Copy Service, NTFS, ReFS, Windows Management Framework) are referenced throughout, while Linux tools and filesystems are not discussed.
Recommendations
  • Provide Linux-specific protection and recovery examples, including supported filesystems (e.g., ext4, xfs) and backup scenarios beyond VM-level protection.
  • Include parity in feature descriptions for Linux workloads, such as item-level recovery, application-aware backup, and supported distributions.
  • Mention Linux tools or backup patterns where relevant (e.g., LVM snapshots, integration with Linux backup agents).
  • List Linux limitations and supported features in the same detail as Windows, and avoid presenting Windows as the default or only scenario.
  • Where Windows tools (e.g., VSS, NTFS) are referenced, provide Linux equivalents or clarify their applicability.
GitHub Create Pull Request
Backup Monitor your backups with Backup Explorer ...es/backup/monitor-azure-backup-with-backup-explorer.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Backup Explorer demonstrates a Windows bias by focusing exclusively on Azure virtual machines (VMs) without specifying support for Linux VMs. Examples and references are generic but implicitly assume Windows environments, such as exporting to Excel (a Windows-centric tool) and referencing Azure VM actions without clarifying Linux support. There are no examples or mentions of Linux-specific backup scenarios, tools, or workflows, and no parity guidance for Linux administrators.
Recommendations
  • Explicitly state whether Backup Explorer supports both Windows and Linux Azure VMs, and provide examples for each.
  • Include screenshots or walkthroughs that demonstrate monitoring and managing backups for Linux VMs.
  • Mention Linux-friendly export formats (e.g., CSV, JSON) alongside Excel, and provide instructions for using them.
  • Clarify whether actions such as configuring backup or responding to alerts work identically for Linux VMs, and note any differences.
  • Add references to Linux command-line tools or automation options (such as Azure CLI or Bash scripts) for interacting with Backup Explorer data.
GitHub Create Pull Request
Backup Backup Classic Alerts using Azure Backup ...b/main/articles/backup/move-to-azure-monitor-alerts.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (MARS agent, SC-DPM, MABS) and patterns (PowerShell, portal) without mentioning Linux equivalents or providing Linux-specific examples. Notification exceptions and job status are described in terms of portal/PowerShell/CLI, but PowerShell is listed first and no Linux shell commands or workflows are shown. There are no examples or guidance for Linux-based backup agents or workflows, and the alert scenarios focus on Windows-centric backup solutions.
Recommendations
  • Include examples and references for Linux-based backup agents and workflows, such as Azure Backup for Linux VMs.
  • Provide CLI and Bash shell command examples alongside PowerShell, especially for alert management and job status checking.
  • Mention Linux-specific backup scenarios and tools where relevant, and ensure parity in alerting and notification documentation.
  • Avoid listing Windows tools and interfaces (PowerShell, portal) before cross-platform or Linux alternatives; present them together or in parallel.
  • Clarify whether features and notifications apply equally to Linux workloads and agents, and document any differences.
GitHub Create Pull Request
Backup Monitoring and reporting solutions for Azure Backup ...main/articles/backup/monitoring-and-alerts-overview.md
High 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 demonstrates Windows bias by consistently mentioning Azure PowerShell before Azure CLI, listing Windows-centric backup solutions (such as Azure Backup Agent, DPM, Azure Backup Server) prominently, and omitting explicit Linux-focused examples or tools. While Azure CLI is referenced, there are no Linux-specific usage patterns, troubleshooting, or monitoring scenarios provided. The documentation does not address Linux backup agents or provide parity in example commands or tool recommendations for Linux environments.
Recommendations
  • Include Linux-specific examples and usage patterns for monitoring and reporting Azure Backup, such as using Azure CLI on Linux, Bash scripts, or REST API calls from Linux environments.
  • Explicitly mention Linux-compatible backup agents or solutions where relevant, and clarify which monitoring features are available for Linux workloads.
  • Provide troubleshooting and alerting scenarios for Linux-based Azure VMs and workloads, including any differences in alert categories or supported features.
  • Ensure that CLI and REST API examples are given equal prominence to PowerShell, and avoid listing PowerShell first unless there is a technical reason.
  • Add documentation sections or notes highlighting best practices for monitoring Azure Backup in Linux environments, including integration with Linux-native tools (e.g., cron jobs, syslog, etc.).
GitHub Create Pull Request
Backup Configure Multi-user authorization using Resource Guard .../blob/main/articles/backup/multi-user-authorization.md
High 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 provides command-line examples for both Azure PowerShell and Azure CLI, but PowerShell examples are consistently presented before CLI examples. There is no mention of Linux-specific tools, shell environments, or considerations, and no explicit Linux/Bash examples are given. The documentation assumes familiarity with PowerShell, which is primarily a Windows tool, and does not address Linux users' needs or provide parity in example ordering or environment-specific guidance.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI (which is cross-platform) first to avoid implicit Windows-first bias.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash) where appropriate.
  • Add notes or sections for Linux users, such as prerequisites for installing Azure CLI on Linux, and troubleshooting tips specific to Linux environments.
  • Include screenshots or walkthroughs using Linux terminals where applicable, not just Azure portal or PowerShell.
  • Clarify that PowerShell Core is available on Linux, but most users on Linux will prefer Azure CLI, and link to installation guides for both tools on Linux.
GitHub Create Pull Request
Backup Offline backup by using Azure Data Box .../main/articles/backup/offline-backup-azure-data-box.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows environments. All supported platforms listed are Windows SKUs, with no mention of Linux or macOS. All examples and instructions use Windows-specific tools (PowerShell, Control Panel, PsExec, Windows command prompt), and there are no Linux equivalents or alternatives provided. The MARS Agent and backup workflow are described exclusively for Windows, and troubleshooting steps rely on Windows-only features (registry, certificate manager).
Recommendations
  • Explicitly state whether Linux and macOS are unsupported, or provide instructions for those platforms if support exists.
  • If possible, add Linux-compatible backup agent instructions or clarify the absence of such support.
  • Provide parity in examples: include Linux shell commands and tools (e.g., Bash, CLI, NFS mounting on Linux) where applicable.
  • Mention Linux alternatives for PowerShell commands (e.g., Azure CLI) and provide step-by-step instructions for Linux environments.
  • If the MARS Agent is Windows-only, suggest or link to alternative backup solutions for Linux users in Azure.
GitHub Create Pull Request
Backup Overview of offline backup ...s/blob/main/articles/backup/offline-backup-overview.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft Azure Backup Server (MABS), System Center Data Protection Manager (DPM), and the MARS Agent—all Windows-centric backup solutions. There are no mentions of Linux backup tools, nor are there examples or workflows for Linux environments. The documentation assumes the use of Windows-based utilities and patterns, omitting guidance for Linux users or cross-platform scenarios.
Recommendations
  • Include examples and workflows for Linux-based backup solutions compatible with Azure offline backup, such as using Azure CLI or third-party Linux backup tools.
  • Explicitly mention whether Linux servers are supported for offline backup and provide parity documentation for Linux environments.
  • Add instructions for preparing disks and staging locations using Linux tools (e.g., dd, mkfs, cryptsetup for encryption) alongside Windows utilities.
  • Clarify any platform limitations and offer guidance for mixed Windows/Linux environments.
  • Ensure that references to utilities and agents are balanced, mentioning both Windows and Linux options where available.
GitHub Create Pull Request
Backup Using Pre-Backup and Post-Backup Scripts ...main/articles/backup/pre-backup-post-backup-scripts.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows file paths, Windows-specific tools (such as cscript for VBScript), and Windows-centric data source naming conventions. There are no examples or guidance for Linux environments, nor is there mention of Linux-compatible scripting or file locations.
Recommendations
  • Add equivalent instructions and examples for Linux-based protected computers, including typical file paths and script execution methods.
  • Mention Linux shell scripting (e.g., Bash, Python) as supported script types, and clarify any platform-specific limitations.
  • Provide sample ScriptingConfig.xml entries for Linux data sources, using Linux-style paths and conventions.
  • Clarify whether MABS supports Linux agents and, if so, document any differences in script configuration and execution.
GitHub Create Pull Request
Backup Query your backups using Azure Resource Graph (ARG) ...les/backup/query-backups-using-azure-resource-graph.md
High 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 Windows bias by listing PowerShell as the first automation client for Azure Resource Graph queries, referencing a PowerShell-specific guide before mentioning Azure CLI and SDK alternatives. There are no explicit Linux or bash examples, nor is there mention of Linux-specific tooling or patterns. All automation examples are generic or Windows-centric, and there is no guidance for Linux users on running queries or integrating with Linux-native tools.
Recommendations
  • List Azure CLI before PowerShell when mentioning automation clients, or present both equally.
  • Provide explicit Linux/bash examples for running ARG queries, such as using Azure CLI in a bash shell.
  • Reference Linux-specific guides or documentation for ARG usage.
  • Mention cross-platform compatibility and clarify that all tools (PowerShell, CLI, SDK) are available on Linux, macOS, and Windows.
  • Include sample scripts or command lines for Linux users, e.g., using az resource-graph query in bash.
  • Avoid implying PowerShell is the default or preferred method unless justified by technical reasons.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure Bicep ...es/backup/quick-backup-azure-files-vault-tier-bicep.md
High 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 Windows bias by exclusively providing PowerShell deployment instructions and examples, referencing Azure PowerShell modules in prerequisites, and omitting equivalent Azure CLI or Bash instructions. The deployment workflow and next steps prioritize PowerShell, with Linux-friendly alternatives mentioned only as secondary options or not at all in the main walkthrough.
Recommendations
  • Add Azure CLI and Bash deployment instructions alongside PowerShell, especially in the 'Deploy the template' section.
  • Update prerequisites to mention both Azure PowerShell and Azure CLI, with installation links for each.
  • Ensure that examples and code snippets are provided for both Windows (PowerShell) and Linux/macOS (CLI/Bash) users.
  • Reorder next steps to present Azure CLI and REST API options equally or before PowerShell, or group them together for parity.
  • Clearly indicate cross-platform compatibility for all steps, and avoid assuming a Windows environment by default.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure Resource Manager ...cles/backup/quick-backup-azure-files-vault-tier-arm.md
High 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 Windows bias by providing only Azure PowerShell deployment examples, mentioning PowerShell before other methods, and omitting explicit Linux/CLI deployment instructions. The 'Next steps' section also lists PowerShell-based management tasks before CLI or REST API alternatives, reinforcing a Windows-centric approach.
Recommendations
  • Add explicit Azure CLI deployment instructions alongside PowerShell examples, including sample commands for Linux/macOS users.
  • Reorder 'Next steps' to present Azure CLI and REST API options before or alongside PowerShell, ensuring equal visibility.
  • Include a note clarifying that ARM template deployment can be performed from any OS using Azure CLI, and provide links to cross-platform instructions.
  • Where PowerShell is referenced, also mention Bash/CLI equivalents to avoid implying PowerShell is the preferred or only method.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure Terraform ...ackup/quick-backup-azure-files-vault-tier-terraform.md
High 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 demonstrates a Windows bias by mentioning Azure PowerShell alongside Azure CLI for authentication, despite Terraform only supporting Azure CLI. The references to Azure PowerShell are frequent and often listed before Azure CLI in 'Next steps', and there are no explicit Linux shell or Bash examples. The troubleshooting and implementation steps do not mention Linux-specific patterns or tools, and the use of 'Console' for command blocks is ambiguous but leans toward Windows conventions.
Recommendations
  • Remove or clarify references to Azure PowerShell in authentication steps, emphasizing that only Azure CLI is supported for Terraform.
  • Provide explicit Bash/Linux shell examples for all command-line instructions, including authentication and Terraform commands.
  • In 'Next steps', list Azure CLI and REST API before Azure PowerShell to avoid Windows-first ordering.
  • Add troubleshooting tips for common Linux-specific issues with Terraform on Azure.
  • Use 'Bash' or 'Shell' as the code block language for command-line examples where appropriate, and clarify cross-platform compatibility.
GitHub Create Pull Request
Backup Quick start - Back up Azure Database for PostgreSQL server ...cles/backup/quick-backup-postgresql-database-portal.md
High 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 Windows bias by referencing PowerShell scripts as the primary method for granting privileges to database users, both in the prerequisites and in the main configuration flow. While alternatives like PG admin or PSQL are mentioned, they are listed after PowerShell and lack concrete examples or guidance. There are no Linux shell (bash) or cross-platform CLI examples provided, and the documentation does not address how to perform these steps on non-Windows environments, which may leave Linux users at a disadvantage.
Recommendations
  • Provide explicit bash/psql command examples for granting database privileges, alongside PowerShell.
  • Include step-by-step instructions for using PG admin and psql on Linux, not just mention them as alternatives.
  • Ensure that any ARM template or script references include cross-platform instructions for running them (e.g., via Azure CLI or bash).
  • Reorder examples so that Windows and Linux methods are presented with equal prominence, or group them together under platform-specific headings.
  • Add a note clarifying that all operations can be performed from Linux, macOS, or Windows, and link to platform-specific setup guides if needed.
GitHub Create Pull Request
Backup Quickstart - Bicep file VM Backup ...lob/main/articles/backup/quick-backup-vm-bicep-file.md
High 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 strong Windows bias. All deployment and management instructions use Azure PowerShell, with no mention of Azure CLI or Bash alternatives suitable for Linux or cross-platform users. The Bicep template provisions only Windows VMs, with no Linux VM options or examples. References to tools and follow-up steps (such as cleanup) are exclusively PowerShell-based, and the template's OS selection is limited to Windows versions.
Recommendations
  • Provide Azure CLI/Bash examples for deploying the Bicep template, in addition to PowerShell.
  • Include a Linux VM option in the Bicep template (e.g., Ubuntu, CentOS) and show how to select it.
  • Add instructions for starting and monitoring backup jobs using Azure CLI, not just PowerShell.
  • Offer cleanup steps using Azure CLI commands (e.g., az group delete) alongside PowerShell.
  • Balance references to Windows and Linux in both the template and procedural steps, ensuring parity for cross-platform users.
GitHub Create Pull Request
← Previous Page 10 of 65 Next →