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 376-400 of 1604 flagged pages
Backup Azure Backup support matrix ...ocs/blob/main/articles/backup/backup-support-matrix.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several ways: Windows backup scenarios and tools (MARS agent, DPM, MABS) are described first and in greater detail, while Linux support is often noted as 'not supported' or only available in limited scenarios. Windows-specific tools and features (MARS agent, DPM, MABS, System State, Active Directory, BitLocker) are mentioned and explained, but Linux equivalents are either absent or only briefly referenced. Examples and feature tables frequently prioritize Windows, with Linux support relegated to footnotes or exceptions.
Recommendations
  • Provide Linux-first or Linux-parity examples and tables, ensuring Linux scenarios are described with equal detail and clarity.
  • Include Linux-specific backup tools and workflows, or clearly state alternatives for Linux users where Windows tools are not available.
  • Add explicit Linux support matrices for on-premises and Azure VM scenarios, including guidance for agentless and app-consistent backups.
  • Where features are Windows-only, offer context or workarounds for Linux environments (e.g., third-party tools, scripts, or Azure-native alternatives).
  • Ensure that documentation sections do not default to Windows terminology or tools, and that Linux support is not only mentioned as an exception.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions Windows-specific technologies (e.g., Windows Server Failover Cluster, Volume Shadow Copy Service (VSS), Windows 2008 32-bit Server) before or in more detail than Linux equivalents. While Linux is referenced (e.g., Linux clusters, freeze/thaw scripts), there are no concrete Linux-specific examples, tools, or patterns provided. Windows scenarios and limitations are described with more specificity, and there is a lack of parity in Linux-focused guidance or examples.
Recommendations
  • Provide explicit Linux examples and scenarios, such as common Linux clustering solutions (e.g., Pacemaker, Corosync) and how Azure Disk Backup interacts with them.
  • Include guidance or references for achieving application-consistent backups on Linux (e.g., using fsfreeze, pre/post scripts), with sample scripts or best practices.
  • Balance scenario descriptions by giving equal detail for both Windows and Linux, including unsupported OS versions for Linux (e.g., specific distributions or kernel versions).
  • Mention Linux-specific backup challenges and solutions, such as handling file system consistency for ext4/xfs/btrfs.
  • Add links to Linux-focused documentation or community resources for Azure Disk Backup.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides step-by-step instructions and code samples for Azure portal, PowerShell, and Azure CLI. PowerShell examples are prominent and detailed, with full command syntax and interactive blocks. The CLI examples are present, but there is no mention of Linux-specific shell environments, nor are there any Bash or Linux-native scripting examples. The documentation does not reference Linux tools or workflows, and the order of examples consistently places PowerShell (a Windows-centric tool) before CLI, which is more cross-platform. There are no explicit Linux or Bash examples, and no mention of Linux-specific considerations, which may make the documentation less approachable for Linux users.
Recommendations
  • Add explicit Bash examples for each CLI command, showing usage in a Linux shell environment.
  • Include notes or sections addressing Linux-specific considerations (e.g., environment variables, authentication methods, file paths).
  • Alternate the order of PowerShell and CLI examples, or present CLI (cross-platform) examples first to avoid implicit Windows-first bias.
  • Reference Linux-native tools or scripting approaches where relevant, such as using environment variables, jq for JSON parsing, or curl for REST API calls.
  • Clarify that Azure CLI commands work equally on Windows, macOS, and Linux, and provide sample outputs from Linux terminals.
  • Consider adding troubleshooting steps or screenshots from Linux environments to improve parity.
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-11 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 prioritizing Windows-centric tools, terminology, and examples. PowerShell is frequently mentioned as a primary automation channel, and Windows-specific backup agents (such as MARS) are referenced without Linux equivalents. There is a lack of explicit Linux or cross-platform command-line examples, and Windows/PowerShell patterns are presented before or instead of Linux alternatives. The documentation also references tools and features (like DPM/MABS) that are Windows-only, and does not provide guidance for Linux workloads or mention Linux-native backup strategies.
Recommendations
  • Include explicit Linux CLI (az CLI, bash) examples alongside or before PowerShell examples for all automation scenarios.
  • Reference Linux-native backup agents and solutions where applicable, and clarify support for Linux workloads (e.g., Azure Backup for Linux VMs, PostgreSQL on Linux).
  • Mention Linux-specific considerations for network, security, and backup policy design, such as file system types, encryption, and authentication differences.
  • Provide parity in documentation for Linux and Windows workloads, including troubleshooting, monitoring, and alerting steps.
  • Avoid using Windows-centric terminology as the default; use cross-platform language and clarify when features/tools are Windows-only.
  • Add links to Linux-focused documentation and best practices for Azure Backup.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is exclusively focused on installing and using the MARS agent for Windows machines, with all instructions, screenshots, prerequisites, and examples tailored to Windows environments. There are no references to Linux systems, Linux tools, or cross-platform alternatives, and PowerShell is mentioned as a required component. The documentation assumes the user is working in a Windows context throughout.
Recommendations
  • Clearly state in the introduction that the MARS agent is only supported on Windows, and provide links or references to equivalent backup solutions for Linux machines (such as Azure Backup for Linux VMs or Azure Backup Server alternatives).
  • Add a comparison table or section that outlines backup options for both Windows and Linux, helping users choose the right solution for their platform.
  • If possible, mention any cross-platform tools or APIs that can be used for backup on Linux, or direct users to documentation for those tools.
  • Avoid using 'machines' generically when referring only to Windows; specify 'Windows machines' to reduce ambiguity.
  • Ensure parity in documentation by providing links to Linux backup agent installation guides in the 'Next steps' or related resources section.
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-11 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 are tailored to the Windows GUI, with no mention of Linux equivalents, CLI commands, or cross-platform alternatives. The tools and terminology used are specific to Windows environments, and there is no guidance for Linux users or administrators.
Recommendations
  • Clarify platform support: Explicitly state whether MABS is Windows-only or if Linux support exists.
  • If Linux support exists, provide equivalent instructions for managing telemetry settings on Linux, including CLI commands or configuration file edits.
  • Include examples using cross-platform tools (e.g., PowerShell Core, Bash) if applicable.
  • Add a section comparing Windows and Linux management options for telemetry settings.
  • If MABS is Windows-only, make this clear at the start of the documentation to avoid confusion for Linux users.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a strong Windows bias: Windows workloads and tools are described in detail and listed first, with extensive coverage of Windows-specific features, file systems (NTFS, ReFS), and backup scenarios. Linux support is limited to guest VM backup, with no mention of application-level or file-level backup for Linux, and Linux is only discussed after Windows and VMware. Windows tools and patterns (e.g., VSS, NTFS, Windows domains, Control Panel) are referenced exclusively, and there are no Linux-specific examples or guidance.
Recommendations
  • Provide parity in documentation by including Linux-specific backup scenarios, such as file-level and application-level backup for Linux workloads.
  • Add examples and guidance for Linux environments, including supported file systems, backup/restore procedures, and any required Linux tools or agents.
  • List Linux support and scenarios alongside Windows and VMware in all relevant tables and sections, not as a separate or last section.
  • Reference Linux authentication and domain/workgroup equivalents where relevant, and clarify any differences in agent installation or management.
  • If limitations exist for Linux support, explicitly state them and provide guidance or workarounds for Linux administrators.
GitHub Create Pull Request
Backup Manage Backup vaults ...-docs/blob/main/articles/backup/manage-backup-vault.md
High Priority View Details →
Scanned: 2026-01-11 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 mild Windows bias. While most instructions focus on the Azure portal (which is cross-platform), the only command-line examples referenced for moving Backup vaults mention PowerShell and Azure CLI, with PowerShell listed first. There are no explicit Linux shell (bash) examples, nor are Linux-specific tools or patterns mentioned. The documentation does not provide parity in command-line instructions for Linux users, and PowerShell is referenced before CLI, which is more commonly used on Linux.
Recommendations
  • Provide explicit bash/Azure CLI examples alongside PowerShell for all command-line operations, especially for moving Backup vaults.
  • When referencing command-line tools, list Azure CLI first or equally with PowerShell to avoid implying Windows preference.
  • Include notes or sections clarifying that all operations can be performed from Linux, macOS, and Windows, and provide sample commands for each platform where relevant.
  • Add troubleshooting tips for Linux users if there are platform-specific caveats.
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-11 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 Windows bias by referencing Windows-specific tools and patterns, such as the Microsoft Azure Recovery Services (MARS) agent, System Center Data Protection Manager (SC-DPM), and Microsoft Azure Backup Server (MABS), all of which are Windows-centric. The mention of PowerShell and the Azure portal as primary management interfaces further reinforces this bias, with no equivalent Linux CLI or automation examples provided. There is no mention of Linux-specific backup agents, nor are there examples or instructions for Linux users. Notification configuration is stated as only available via the Azure portal, with PowerShell/CLI/REST API not supported, which may disadvantage Linux administrators who prefer command-line or automation approaches.
Recommendations
  • Add examples and instructions for managing backup alerts using Azure CLI and REST API, which are cross-platform and commonly used on Linux.
  • Reference Linux-compatible backup agents or clarify support for Linux workloads in Azure Backup.
  • Include parity in documentation for notification configuration, such as CLI or automation options, and note any limitations for Linux users.
  • Avoid listing Windows tools (MARS, SC-DPM, MABS) without mentioning Linux equivalents or alternatives, or explicitly state their platform limitations.
  • Provide sample workflows or screenshots from Linux environments where relevant.
GitHub Create Pull Request
Backup Offline Backup with Azure Data Box for DPM and MABS ...icles/backup/offline-backup-azure-data-box-dpm-mabs.md
High Priority View Details →
Scanned: 2026-01-11 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
This documentation is heavily biased towards Windows environments. All instructions, examples, and prerequisites are specific to Windows Server, DPM, and MABS, with no mention of Linux support or equivalents. The use of Windows-specific tools (PSExec, registry edits, Windows certificate manager), reliance on PowerShell modules, and references to Windows file paths and features (NFS client on Windows, mounting drives as X:) reinforce this bias. There are no Linux examples, nor any indication that Linux-based backup servers or agents are supported or can participate in this workflow.
Recommendations
  • Explicitly state platform limitations at the beginning (e.g., 'Windows only'), or add Linux support if available.
  • If Linux support exists, provide equivalent instructions for Linux environments, including mounting Data Box via NFS, certificate management, and agent installation.
  • Include Linux command-line examples (e.g., using mount, certificate tools, Azure CLI) alongside Windows/PowerShell examples.
  • Reference Linux tools and patterns (e.g., systemd, cron, bash scripts) where appropriate.
  • Clarify whether DPM/MABS or MARS agent can run on Linux, and if not, suggest alternative Azure backup solutions for Linux workloads.
  • Ensure troubleshooting steps and error messages include Linux scenarios if supported.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits significant Windows bias. All examples and supported workloads are Windows-centric, with detailed breakdowns for various Windows versions and applications (e.g., NTFS, VSS, Hyper-V, Exchange, SharePoint, SQL Server). Linux support is mentioned only briefly and generically, with no specific Linux distributions, file systems, or application workloads detailed. Windows tools and patterns (NTFS, VSS, ReFS, FAT, FAT32, Windows Management Framework, Hyper-V, etc.) are referenced exclusively, and Linux is only supported as a guest VM with limited recovery options.
Recommendations
  • Provide a detailed matrix for Linux workloads, including supported distributions, file systems (e.g., ext4, xfs, btrfs), and application types.
  • Include Linux-specific backup and recovery scenarios, such as item-level recovery, application-aware backups (e.g., MySQL, PostgreSQL), and support for Linux-native tools.
  • List Linux limitations and requirements as clearly as those for Windows (e.g., minimum volume size, snapshot mechanisms).
  • Reference Linux documentation and best practices for backup and recovery, similar to the detailed Windows guidance.
  • Clarify whether features like deduplication, system state/bare metal recovery, and cluster support are available for Linux workloads.
  • Add examples and guidance for Linux users, including command-line instructions and integration with Linux authentication and security models.
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-11 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 exclusively referencing Azure virtual machines (VMs) and workflows that are typically associated with Windows environments. There is no mention of Linux-specific backup scenarios, nor are there examples or guidance for Linux VM users. Export options focus on Excel, a Windows-centric tool, and there is an absence of parity for Linux-friendly formats or tools. The documentation does not provide Linux command-line or automation examples, nor does it mention Linux backup agents or integration patterns.
Recommendations
  • Include explicit references to Linux VM backup monitoring, and clarify whether Backup Explorer supports Linux VMs.
  • Provide examples and screenshots that show Linux VM backup items and workflows.
  • Offer export options in Linux-friendly formats, such as CSV or JSON, and mention how to use these with common Linux tools.
  • Add guidance for Linux users on how to interact with Backup Explorer via CLI (e.g., Azure CLI) and automation scripts.
  • Clarify any limitations or differences in monitoring backups for Linux versus Windows VMs.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools and patterns (such as PowerShell and Azure Backup Agent) are mentioned before their Linux equivalents, and PowerShell is listed as a primary non-portal client for monitoring and reporting. Windows workloads (e.g., Azure Backup Agent, DPM, Azure Backup Server) are referenced in alert tables, but Linux-specific examples, tools, or patterns are not explicitly highlighted. There are no Linux command-line examples or references to Linux-native tooling, and the documentation does not address Linux-specific monitoring scenarios or parity.
Recommendations
  • Add explicit Linux CLI examples (e.g., Bash, az CLI usage from Linux shells) alongside PowerShell examples.
  • Mention Linux-native monitoring and reporting tools or patterns where relevant (e.g., integration with syslog, cron, or Linux-based automation).
  • Ensure that references to non-portal clients (CLI, REST API) are not Windows-centric and provide parity for Linux users.
  • Include Linux-specific workloads and scenarios in alert tables and documentation sections.
  • Review and update documentation to avoid listing Windows tools or patterns before Linux equivalents unless contextually justified.
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-11 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 are no explicit Linux shell (bash) examples, nor is there any mention of Linux-specific tooling or considerations. The documentation assumes the use of Azure Portal, PowerShell, or Azure CLI, but does not address platform-specific differences or provide parity for Linux users beyond CLI commands.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit Windows-first bias.
  • Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide sample bash scripts for common workflows.
  • Include notes or sections addressing platform-specific considerations, such as differences in authentication or environment setup between Windows and Linux.
  • Add troubleshooting tips for Linux users, especially around authentication and permissions.
  • Where screenshots are provided, clarify that the Azure Portal is accessible from any OS/browser, and note any OS-specific UI differences if applicable.
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-11 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 support. All examples, prerequisites, and troubleshooting steps use Windows-specific tools (PowerShell, MARS Agent, PsExec, Windows Control Panel, Windows registry, etc.), and there are no instructions or alternatives for Linux systems. The documentation assumes the user is operating in a Windows environment from the outset.
Recommendations
  • Explicitly state platform support at the beginning, including whether Linux is supported or not.
  • If Linux is supported, provide equivalent instructions for Linux systems, including installation and usage of any required agents or tools.
  • Include Linux-specific examples for mounting Data Box devices (e.g., using NFS mount commands on Linux).
  • Offer troubleshooting steps for Linux environments, if applicable.
  • If MARS Agent is Windows-only, suggest alternative backup solutions for Linux users and link to relevant documentation.
  • Avoid assuming Windows as the default environment; present platform-agnostic steps where possible.
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-11 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 mild Windows bias. When discussing automation clients for Azure Resource Graph, PowerShell is mentioned first, with a direct link, while the Azure CLI and Python SDK are listed after. There are no explicit Linux-specific examples or references to Linux shell usage (e.g., Bash), nor are there any screenshots or instructions tailored for Linux users. All sample queries are platform-agnostic (Kusto), but the automation context leans toward Windows/PowerShell.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell to ensure parity for Linux users.
  • Include explicit Bash or Linux shell usage examples for running ARG queries.
  • Add screenshots or instructions showing ARG usage on Linux (e.g., via Azure CLI in a terminal).
  • Clarify that all automation clients (PowerShell, CLI, SDK) are cross-platform, and provide links to Linux installation guides.
  • Consider adding a section or note for Linux/macOS users, highlighting any differences or tips for their environments.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page shows evidence of Windows bias, primarily through the repeated mention and prioritization of PowerShell scripts for privilege assignment and configuration tasks. PowerShell is a Windows-centric tool, and while alternatives like PG admin or PSQL are briefly mentioned, they are presented as secondary options. There are no explicit Linux shell (bash) or cross-platform CLI examples, nor are Linux-specific instructions or screenshots provided. This may make it less accessible for users working on Linux or macOS environments.
Recommendations
  • Provide equivalent bash/psql command-line examples for privilege assignment and configuration tasks alongside PowerShell scripts.
  • Explicitly mention and document steps for Linux and macOS users, including any required tools or environment setup.
  • Include screenshots or terminal output from Linux environments where relevant.
  • Ensure that references to PowerShell are balanced with references to cross-platform or Linux-native tools (e.g., Azure CLI, psql, bash scripting).
  • Clarify that all steps can be performed on both Windows and Linux, and highlight any platform-specific differences.
GitHub Create Pull Request
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Servers with a Bicep file ...ackup/quick-backup-postgresql-flexible-server-bicep.md
High Priority View Details →
Scanned: 2026-01-11 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 by exclusively providing PowerShell deployment instructions and referencing Windows-centric tools and workflows. There are no examples or guidance for deploying the Bicep template using cross-platform tools such as Azure CLI, nor are Linux or macOS users considered. The 'Next steps' section also directs users to a PowerShell-based restore guide, further reinforcing the Windows-centric approach.
Recommendations
  • Add Azure CLI deployment instructions alongside PowerShell, including sample commands for deploying the Bicep template from Linux/macOS.
  • Explicitly mention that Bicep and Azure CLI are cross-platform and provide links to installation guides for Linux/macOS.
  • Include a note or section for Linux/macOS users, describing how to run the deployment commands in Bash or other common shells.
  • Balance references to PowerShell with equivalent Azure CLI examples throughout the documentation.
  • Update 'Next steps' to include links to restore guides using Azure CLI or other cross-platform tools.
GitHub Create Pull Request
Backup Offline backup for Data Protection Manager (DPM) and Microsoft Azure Backup Server (MABS) - previous versions ...cles/backup/offline-backup-server-previous-versions.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented towards Windows environments, with all examples, tools, and workflows described for Windows Server, Windows client, DPM, and MABS. There are no Linux equivalents or examples provided, and all utilities (such as AzureOfflineBackupDiskPrep.exe and AzureOfflineBackupCertGen.exe) are Windows executables. Registry edits, screenshots, and instructions are specific to Windows, and PowerShell commands are referenced without Bash or Linux alternatives. There is no mention of how to perform offline backup from Linux systems, nor any cross-platform guidance.
Recommendations
  • Provide explicit guidance for Linux environments, including supported workflows and tools for offline backup.
  • Include Linux-specific examples, such as Bash commands, Linux file paths, and screenshots from Linux systems.
  • Clarify whether the described utilities are available for Linux, and if not, suggest alternative methods or tools for Linux users.
  • Mention any limitations or lack of support for Linux, and provide links to relevant documentation for Linux backup solutions.
  • Ensure parity in instructions, presenting Linux and Windows options side-by-side where possible.
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-11 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 a Windows bias by exclusively referencing Windows file paths, tools (such as cscript for VBScript), and conventions (drive letters, Windows-specific application names). There are no examples or instructions for Linux systems, nor any mention of Linux-compatible scripting or file locations. All terminology and examples are Windows-centric.
Recommendations
  • Include Linux-specific instructions and examples, such as file paths, script execution methods, and permissions.
  • Mention Linux equivalents for command-line tools (e.g., bash, sh) and scripting practices.
  • Clarify whether MABS supports Linux clients, and if so, provide parity in documentation for configuring pre- and post-backup scripts on Linux systems.
  • Provide examples using Linux file systems and application data sources (e.g., /mnt/data, MySQL, PostgreSQL).
  • Explicitly state any platform limitations or differences in script support between Windows and Linux.
GitHub Create Pull Request
Backup Create and use private endpoints for Azure Backup ...re-docs/blob/main/articles/backup/private-endpoints.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias, primarily through the exclusive use of PowerShell scripts and Windows-centric tooling (e.g., MARS agent, DPM server, ARMClient with Windows file paths). All code examples and automation instructions are provided using PowerShell, with no equivalent Bash, Azure CLI, or Linux-native instructions. The guidance for role creation, DNS entry management, and private endpoint setup is Windows/PowerShell-first, and there are no Linux-specific agent or tool references. The documentation assumes the reader is using Windows environments and tools, omitting Linux alternatives and examples.
Recommendations
  • Provide Azure CLI and Bash script equivalents for all PowerShell examples, including role creation, DNS record management, and private endpoint setup.
  • Include instructions for using ARMClient or REST API calls from Linux/macOS environments, avoiding Windows-specific file paths (e.g., C:\<filepath>).
  • Reference Linux-compatible backup agents (such as Azure Backup for Linux VMs) and provide guidance for their use with private endpoints.
  • Add examples for managing permissions, DNS entries, and private endpoints using Linux-native tools and workflows.
  • Ensure that automation scripts and downloadable resources are cross-platform or provide separate versions for Linux users.
  • Explicitly mention platform compatibility and provide parity in troubleshooting steps for both Windows and Linux environments.
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-11 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 referencing Azure PowerShell modules in the prerequisites. There are no examples or instructions for deploying the Bicep template using Azure CLI, Bash, or other Linux-native tools. The deployment workflow and next steps prioritize PowerShell and Windows-centric patterns, with Linux alternatives mentioned only in passing or as links, not as first-class examples.
Recommendations
  • Add step-by-step deployment instructions using Azure CLI (az deployment group create) alongside the PowerShell example.
  • Include Bash script examples for template deployment in the Azure Cloud Shell.
  • In the prerequisites, mention both Azure PowerShell and Azure CLI as options for users on different platforms.
  • Ensure that Linux and cross-platform tools are presented with equal prominence and detail as Windows/PowerShell tools.
  • Where possible, provide side-by-side examples for PowerShell and CLI/Bash to improve parity and accessibility.
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-11 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 mentioning Azure PowerShell as an authentication option before clarifying that only Azure CLI is supported for Terraform. There are references to Azure PowerShell in the 'Next steps' section, with no mention of Linux-specific tools or shell environments (e.g., Bash). No Linux or cross-platform shell examples are provided for authentication or command execution, and the troubleshooting section does not reference Linux-specific issues or guidance.
Recommendations
  • Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and provide Bash shell examples for authentication and command execution.
  • Remove or clarify the Azure PowerShell references in authentication steps, emphasizing that only Azure CLI is supported for Terraform workflows.
  • In 'Next steps', balance PowerShell references with Bash/CLI examples, or link to Linux-specific guides where available.
  • Add troubleshooting guidance for common Linux issues (e.g., permissions, environment variables) when using Terraform on Azure.
  • Where possible, use neutral language (e.g., 'shell' instead of 'PowerShell') and ensure parity in examples for both Windows and Linux users.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2026-01-11 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 by exclusively providing PowerShell deployment instructions, referencing Azure PowerShell modules, and omitting any Azure CLI or Bash examples. The 'Next steps' section also links only to PowerShell-based restore guidance. No Linux-native tools or cross-platform instructions are provided, which may hinder Linux users or those preferring CLI/Bash workflows.
Recommendations
  • Add Azure CLI deployment instructions alongside PowerShell, including example commands for deploying the ARM template from Bash or Linux shells.
  • Reference both Azure PowerShell and Azure CLI modules in prerequisites, with installation links for each.
  • Include cross-platform notes clarifying that both Windows and Linux environments are supported.
  • Update 'Next steps' to include links to restore guides using Azure CLI or Bash, not just PowerShell.
  • Consider providing sample scripts for Bash and/or Linux shell environments to ensure parity.
GitHub Create Pull Request
Backup Quickstart - Create a backup policy for Azure Database for PostgreSQL - Flexible Server using Azure CLI .../backup/quick-backup-postgresql-flexible-server-cli.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias in several ways. It references PowerShell and Windows-style file paths (e.g., .\OSSPolicy.json), describes PowerShell object manipulation before mentioning CLI file-based workflows, and refers to the 'default PowerShell object' as the baseline for backup policy behavior. There are no explicit Linux shell examples, and Windows conventions (backslashes, PowerShell objects) are presented first or exclusively.
Recommendations
  • Provide explicit Linux shell (bash) examples alongside or before Windows/PowerShell examples, using Linux file paths (e.g., ./OSSPolicy.json) and conventions.
  • Clarify that Azure CLI commands work cross-platform and show examples in both Windows and Linux environments.
  • Avoid referring to PowerShell objects as the default baseline; instead, describe both PowerShell and CLI approaches equally.
  • Add notes or sections for Linux users, including tips for file manipulation and scripting in bash.
  • Use neutral file path separators (forward slashes) or show both styles where relevant.
GitHub Create Pull Request
← Previous Page 16 of 65 Next →