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 676-700 of 1604 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-database-azure-vms.md ...rticles/backup/backup-sql-server-database-azure-vms.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. The prerequisites and operational steps focus exclusively on Windows environments, referencing the AzureBackupWindowsWorkload extension, NT Service accounts, and Windows-specific troubleshooting scripts. There is no mention of Linux-based SQL Server VMs, nor are Linux equivalents or examples provided. The connectivity test scripts are only for Windows, and all extension and agent references are Windows-centric. The documentation does not address Linux SQL Server VM scenarios, tools, or patterns.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server databases on Linux-based Azure VMs, including any differences in prerequisites, agent/extension installation, and supported features.
  • Provide Linux-specific troubleshooting scripts or commands (e.g., Bash, shell scripts) for connectivity testing and backup diagnostics.
  • Clarify whether features such as auto-protection, backup policies, and the AzureBackupWindowsWorkload extension are available or have equivalents for Linux SQL Server VMs.
  • Reference the Azure Virtual Machine Agent for Linux and link to its documentation alongside the Windows agent.
  • Include notes or tables comparing Windows and Linux support for SQL Server backup in Azure, highlighting any limitations or differences.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-on-availability-groups.md ...les/backup/backup-sql-server-on-availability-groups.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example πŸ”§ Windows Tools Windows First
Summary
The documentation page focuses exclusively on backing up SQL Server Always On Availability Groups in Azure, but implicitly assumes a Windows environment throughout. There are no examples, instructions, or mentions of Linux-based SQL Server deployments, nor any guidance for Linux-specific tools or patterns. The language and scenarios described (such as VM registration, backup extensions, and failover) are tailored to Windows VMs, with no parity for Linux. Windows tools and patterns (Recovery Services vault, backup extension) are mentioned without Linux equivalents, and there is no indication that Linux is supported or considered.
Recommendations
  • Explicitly state support or lack thereof for SQL Server on Linux Always On AGs in Azure.
  • If Linux is supported, provide parallel instructions and examples for Linux-based deployments, including registration, backup extension installation, and failover handling.
  • Mention Linux-specific tools, commands, or troubleshooting steps where applicable (e.g., systemd services, Linux file paths, shell commands).
  • Add a section comparing Windows and Linux support for AG backups, highlighting any differences or limitations.
  • Ensure all diagrams, tables, and examples include Linux nodes or clarify platform applicability.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-azure-troubleshoot.md ...rticles/backup/backup-sql-server-azure-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All examples, file paths, and troubleshooting steps reference Windows-specific locations (e.g., C:\Program Files\...), Windows services, and NT AUTHORITY accounts. The AzureBackupWindowsWorkload extension is mentioned exclusively, with no mention of Linux equivalents. Troubleshooting steps and error resolutions reference Windows tools (Control Panel, Local Security Policy) and PowerShell for automation, with no Bash or Linux command alternatives. There is no guidance for SQL Server running on Linux VMs, nor any mention of Linux file paths, services, or backup extensions.
Recommendations
  • Add equivalent troubleshooting steps and examples for SQL Server running on Linux VMs, including Linux file paths (e.g., /opt/...), service management (systemctl), and user accounts.
  • Mention and document the AzureBackupLinuxWorkload extension (if available) or clarify Linux support status.
  • Provide Bash or shell script examples alongside PowerShell for automation tasks.
  • Reference Linux-specific tools (e.g., package managers, system logs) where appropriate.
  • Clarify in the introduction whether the guidance applies only to Windows VMs, or update to include Linux VM scenarios.
  • Ensure error messages and recommended actions include Linux-specific advice where relevant.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-database-from-azure-vm-blade.md ...ckup/backup-sql-server-database-from-azure-vm-blade.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows-based SQL Server VMs. It exclusively references Windows-specific extensions (AzureBackupWindowsWorkload, SqlIaaSExtension), Windows service accounts (NT Service\AzureWLBackupPluginSvc), and does not mention Linux-based SQL Server VMs or provide any Linux-specific instructions, examples, or tool references. All screenshots and steps assume a Windows environment, and there is no guidance for users running SQL Server on Linux VMs.
Recommendations
  • Add explicit guidance and steps for backing up SQL Server running on Linux-based Azure VMs, including any differences in process, prerequisites, and supported features.
  • Mention and document Linux-specific extensions or agents if available, or clarify if Azure Backup does not support Linux SQL Server VMs.
  • Include Linux command-line examples (e.g., using Azure CLI or REST API from a Linux shell) and screenshots from Linux environments where applicable.
  • Clearly state Windows-only limitations at the beginning of the article if Linux is not supported, or provide links to Linux-specific documentation.
  • Ensure parity in terminology and instructions for both Windows and Linux users, including service account setup, permissions, and backup/restore workflows.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix-iaas.md ...lob/main/articles/backup/backup-support-matrix-iaas.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows scenarios and tools (such as PowerShell, MARS agent, DPM, MABS) are described first and in greater detail, with Linux support often relegated to separate sections or marked as unsupported. Restore and backup examples frequently reference Windows-specific tooling (e.g., PowerShell) without Linux CLI equivalents. Many advanced backup features (file/folder-level backup, use of MARS agent, DPM, MABS) are available only for Windows, with Linux support either missing or explicitly called out as unsupported. Where restore methods are described, Windows-centric approaches (PowerShell, templates) are mentioned, but Linux CLI or automation approaches are not. The documentation also lacks parity in example commands and workflows for Linux users.
Recommendations
  • Provide Linux CLI (az, bash) examples wherever PowerShell is referenced for restore or backup operations.
  • Introduce Linux-first or Linux-parallel sections for backup and restore workflows, matching the detail given to Windows scenarios.
  • Clarify and expand support for Linux backup tooling, including any available alternatives to MARS agent, DPM, or MABS.
  • Where features are Windows-only, explicitly state the lack of Linux support and suggest workarounds or roadmap for parity.
  • Add more detailed Linux restore scenarios, including automation and scripting options, and reference Linux-specific documentation where available.
  • Ensure that advanced features (e.g., file-level restore, compression, encryption) are described for both platforms, or the limitations are clearly documented.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix-mars-agent.md ...in/articles/backup/backup-support-matrix-mars-agent.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows Only πŸ”§ Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation for the MARS agent is exclusively focused on Windows environments. All examples, supported operating systems, installation instructions, and tooling references pertain only to Windows (including Windows Server, Windows desktop editions, and Windows-specific management tools like PowerShell, MMC, and DISM.exe). There is no mention of Linux support, Linux equivalents, or cross-platform scenarios. The documentation assumes a Windows-first (and only) audience, with no parity for Linux users.
Recommendations
  • Explicitly state in the introduction and support matrix whether Linux is supported or not, and if not, suggest alternative Azure Backup solutions for Linux workloads.
  • If Linux support is planned or available via other agents or extensions, provide links and guidance for Linux users.
  • Include a comparison table or section that clarifies backup options for both Windows and Linux environments, including supported agents and features.
  • Avoid exclusive references to Windows tools (e.g., PowerShell, MMC, registry edits) without noting their lack of applicability to Linux.
  • If possible, provide parity in examples, troubleshooting, and backup/restore scenarios for Linux systems, or direct users to Linux-specific documentation.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-automation.md ...blob/main/articles/backup/backup-support-automation.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First πŸ”§ Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently listing PowerShell as the first automation method, providing explicit PowerShell examples and links for nearly every operation, and referencing Windows-centric tooling (PowerShell) even for workloads that are cross-platform (e.g., Azure Files, Blobs, Disks, PostgreSQL). CLI and REST API options are present, but PowerShell is always prioritized, and there is no mention of Bash, Linux shell scripting, or native Linux automation tools. In some cases, operations are only supported via PowerShell, reinforcing the Windows-centric approach.
Recommendations
  • Alternate the order of PowerShell and CLI in tables and examples, or list CLI first in some cases to balance visibility.
  • Explicitly mention Linux/Bash shell scripting options where applicable, and provide example scripts for Linux environments.
  • Clarify that Azure CLI is cross-platform and provide guidance for running CLI commands on Linux and macOS.
  • Add notes or callouts for Linux users, including installation instructions for CLI and REST tools on Linux.
  • Where PowerShell is the only supported method, provide information on using PowerShell Core on Linux, or roadmap for CLI/REST parity.
  • Avoid language that implies PowerShell is the default or preferred method unless it is truly the only supported option.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix.md ...ocs/blob/main/articles/backup/backup-support-matrix.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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, with Linux support often mentioned as 'not supported' or as a secondary consideration. Windows-specific tools and features (e.g., MARS agent, DPM, MABS, Active Directory backup, BitLocker) are referenced without Linux equivalents or alternatives. Linux backup support is limited and often described in terms of what is not supported, with few concrete examples or guidance for Linux users.
Recommendations
  • Provide Linux-first or Linux-parity examples and scenarios alongside Windows ones, especially in tables and feature lists.
  • Include Linux-specific backup tools, workflows, and best practices where Windows tools (MARS, DPM, MABS) are mentioned.
  • Offer detailed guidance and examples for configuring app-consistent backups on Linux, including scripts and automation patterns.
  • Clarify limitations for Linux support and suggest alternative approaches or third-party solutions where Azure-native support is lacking.
  • Ensure that documentation sections (e.g., security, compression, retention) explicitly address Linux scenarios and not just Windows.
  • Add parity in visual aids, code samples, and step-by-step instructions for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-the-mabs-server.md ...cs/blob/main/articles/backup/backup-the-mabs-server.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation is heavily Windows-centric, with all examples, tools, and procedures assuming a Windows environment. Windows-specific utilities (PowerShell, mountvol.exe, diskshadow.exe, psexec.exe, Net Share) are used exclusively, and there are no Linux or cross-platform alternatives or examples provided. The instructions and recovery steps rely on Windows features (VSS, Previous Versions, Windows Explorer), and the documentation never mentions Linux or non-Windows environments, nor does it provide guidance for administrators using Linux-based systems.
Recommendations
  • Add explicit statements about platform requirements and clarify if MABS is Windows-only, or provide guidance for cross-platform scenarios if possible.
  • Where feasible, provide Linux equivalents or alternatives for backup and restore operations (e.g., using SMB/CIFS mounts, Linux SQL Server tools, or Azure CLI on Linux).
  • Include examples using Linux command-line tools for file copying, mounting VHDs (if supported), and accessing network shares.
  • Reference Azure Backup and SQL Server documentation for Linux, and provide links or brief instructions for performing similar operations on Linux systems.
  • If certain steps are only possible on Windows, clearly state this and suggest workarounds or alternatives for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/disk-backup-overview.md ...docs/blob/main/articles/backup/disk-backup-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 more prominently than Linux equivalents. There are references to Windows-specific backup scenarios and unsupported OS configurations, but Linux scenarios are only mentioned in passing and lack concrete examples. No Linux-specific backup tools, patterns, or examples are provided, and there is no parity in describing how Linux users should approach application-consistent backups or agentless backups beyond generic statements.
Recommendations
  • Provide explicit Linux examples and scenarios, such as how to achieve application-consistent backups on Linux (e.g., using fsfreeze, pre/post scripts, or other Linux-native tools).
  • Mention Linux clustering technologies (e.g., Pacemaker, Corosync) alongside Windows Server Failover Cluster, and describe any differences in backup support or requirements.
  • Include references to Linux-specific challenges and solutions, such as handling file system quiescence, supported distributions, and unsupported configurations.
  • Add Linux-first or Linux-parity examples in the 'Key benefits' and 'Scenarios' sections, ensuring Linux is not an afterthought.
  • Clarify any limitations or best practices for Linux environments, such as supported file systems, agentless backup caveats, or integration with Linux-native backup workflows.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/encryption-at-rest-with-cmk.md ...ob/main/articles/backup/encryption-at-rest-with-cmk.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First πŸ”§ Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently as a primary automation example alongside the Azure portal and CLI, with detailed command sequences and outputs. The use of PowerShell, a Windows-centric tool, is presented at parity with Azure CLI, but often appears first in tabbed examples and warnings. There are multiple warnings and notes about PowerShell-specific behaviors, and the documentation references BitLocker for Windows before DM-Crypt for Linux when discussing Azure Disk Encryption. There are no explicit Linux shell examples (e.g., bash scripts), and the overall pattern assumes familiarity with Windows tooling and conventions.
Recommendations
  • Ensure CLI examples are presented before or at parity with PowerShell examples in tabbed sections.
  • Add bash shell script examples for common tasks, especially for Linux administrators.
  • Reference Linux tools (e.g., DM-Crypt) before or alongside Windows tools (e.g., BitLocker) when discussing encryption technologies.
  • Include notes or sections clarifying cross-platform support and differences, especially for Linux users.
  • Avoid PowerShell-specific warnings unless equivalent CLI or bash caveats are also provided.
  • Consider adding troubleshooting or FAQ entries relevant to Linux environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/guidance-best-practices.md ...s/blob/main/articles/backup/guidance-best-practices.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell is frequently mentioned as an automation channel, and example procedures reference PowerShell before CLI or other cross-platform tools. Windows-centric backup agents (MARS, DPM/MABS) are discussed in detail, while Linux-specific backup scenarios, agents, or commands are not addressed. There are no explicit Linux examples, and the documentation assumes familiarity with Windows tools and patterns, such as PowerShell and Windows backup agents, without providing equivalent guidance for Linux environments.
Recommendations
  • Provide Linux-specific examples and procedures alongside PowerShell, such as Azure CLI or Bash scripts for backup operations.
  • Explicitly mention and document Linux workload backup scenarios, including supported distributions and any required agents or configurations.
  • Highlight cross-platform automation options (Azure CLI, REST API, SDKs) equally or before PowerShell, and ensure example commands are available for both Windows and Linux users.
  • Include guidance for Linux administrators, such as best practices for backing up Linux VMs, files, and databases, and reference Linux-native tools where applicable.
  • Clarify any limitations or differences in backup features between Windows and Linux workloads, and provide parity where possible.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/encryption-at-rest-with-cmk-for-backup-vault.md ...backup/encryption-at-rest-with-cmk-for-backup-vault.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 for enabling and managing encryption with customer-managed keys in Azure Backup vaults. While it offers both Azure CLI and PowerShell examples, the PowerShell examples are prominent and detailed, reflecting a Windows-centric approach. There are no explicit Linux shell (bash) examples, nor are there references to Linux-specific tools or workflows. The ordering of examples sometimes places PowerShell before CLI, and the screenshots and UI references are tailored to the Azure portal, which is platform-neutral but often more familiar to Windows users. Overall, the documentation assumes familiarity with Windows tools and patterns, with limited consideration for Linux users beyond the CLI.
Recommendations
  • Add explicit bash shell examples for all CLI commands, showing usage in a Linux environment (e.g., variable assignment, piping, jq for JSON parsing).
  • Where PowerShell is referenced, provide equivalent bash or shell scripting examples, especially for tasks like fetching principal IDs and manipulating output.
  • Ensure CLI examples are given equal prominence and detail as PowerShell, including full command sequences and expected output.
  • Include notes or tips for Linux users regarding authentication, environment setup, and differences in command-line behavior.
  • Consider reordering sections so that CLI and bash examples appear before PowerShell, or present them side-by-side.
  • Reference Linux tools (e.g., curl, jq) where appropriate for REST API or scripting scenarios.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/install-mars-agent.md ...e-docs/blob/main/articles/backup/install-mars-agent.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 focused on Windows environments and tools. All examples, instructions, and screenshots are specific to Windows, including references to Windows executables (.exe), Windows-specific prerequisites (PowerShell, .NET Framework), and Windows UI elements. There is no mention of Linux support, nor are there any Linux-specific instructions or examples. The use of PowerShell is highlighted as a scripting option, and Windows tools and patterns are referenced exclusively.
Recommendations
  • Clearly state the platform support for the MARS agent at the beginning (e.g., if Linux is not supported, explain why and suggest alternatives).
  • If Linux support exists, provide equivalent Linux installation instructions, examples, and screenshots.
  • Mention Linux backup solutions (such as Azure Backup for Linux VMs) and link to relevant documentation.
  • Avoid assuming the reader is using Windows by default; use neutral language and clarify platform-specific steps.
  • If PowerShell scripts are provided, offer Bash or shell script equivalents for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-backup-vault.md ...-docs/blob/main/articles/backup/manage-backup-vault.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 primarily through its examples and tool references. When mentioning command-line management options for moving Backup vaults, PowerShell is listed first and in detail, while Linux-specific alternatives (such as Bash or Azure CLI on Linux) are only briefly referenced and not exemplified. There are no explicit Linux shell or CLI examples, and the documentation does not address platform-specific considerations for Linux users. The screenshots and workflow descriptions are focused on the Azure portal, which is platform-neutral, but the command-line references and lack of parity in examples suggest a preference for Windows tools and patterns.
Recommendations
  • Provide explicit Azure CLI examples for Linux/macOS users alongside PowerShell examples.
  • Ensure that references to command-line tools mention Azure CLI and Bash equally with PowerShell, and present them in parallel or with equal prominence.
  • Add notes or sections addressing any platform-specific considerations for Linux users (e.g., authentication, environment setup).
  • Include sample scripts or commands for common operations using Azure CLI/Bash, not just PowerShell.
  • Review and update documentation to avoid listing Windows tools first unless there is a technical reason.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/microsoft-azure-backup-server-protection-v3.md .../backup/microsoft-azure-backup-server-protection-v3.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation page exhibits a strong Windows bias: all examples and supported workloads are Windows-centric, with extensive detail on Windows versions, features, and tools (e.g., NTFS, VSS, Hyper-V, Windows Management Framework). Linux support is mentioned only briefly and as a guest VM, with no details on Linux-specific backup scenarios, filesystems, or recovery options. There are no Linux command or tool references, and Windows tools and patterns (NTFS, VSS, ReFS, system state/bare metal recovery) are discussed exclusively.
Recommendations
  • Add explicit examples and guidance for Linux workloads, including supported filesystems (e.g., ext4, xfs), backup and recovery scenarios, and limitations.
  • Include Linux-specific backup and restore instructions, such as using native Linux tools or Azure Backup Server's integration with Linux.
  • Clarify whether item-level recovery is possible for Linux VMs, and document any differences compared to Windows.
  • List supported Linux distributions and versions directly in the matrix, not just as a link.
  • Discuss Linux-specific requirements, such as agent installation, snapshot mechanisms, and compatibility issues.
  • Balance the documentation by presenting Linux support details alongside Windows, rather than relegating Linux to a single row.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/monitor-azure-backup-with-backup-explorer.md ...es/backup/monitor-azure-backup-with-backup-explorer.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias by exclusively referencing Azure virtual machines (VMs) and backup monitoring in a way that implicitly prioritizes Windows environments. There are no examples or mentions of Linux-specific backup scenarios, tools, or patterns. Export functionality is described only in terms of Excel, a Windows-centric tool, and navigation references (such as 'Configure Backup' panes) are tailored to the Azure portal experience, which is more familiar to Windows users. No PowerShell examples are given, but the overall framing and examples assume a Windows-first context.
Recommendations
  • Include explicit examples and instructions for monitoring Linux VM backups, including any differences in backup item details, job statuses, or alert types.
  • Mention and provide examples for exporting data in open formats (such as CSV) and using Linux-compatible tools for analysis.
  • Clarify whether Backup Explorer supports Linux VMs and, if so, highlight any Linux-specific considerations or features.
  • Provide parity in documentation by referencing both Windows and Linux environments when discussing backup configuration, monitoring, and remediation steps.
  • Add screenshots or walkthroughs that show Linux VM backup monitoring in the Azure portal.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-telemetry.md ...ure-docs/blob/main/articles/backup/manage-telemetry.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation is heavily focused on Windows environments, specifically referencing the Microsoft Azure Backup Server (MABS) console, which is a Windows-only tool. 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 any references to Linux tools or patterns.
Recommendations
  • Clarify platform support: Explicitly state if MABS is Windows-only, or provide guidance for Linux users if applicable.
  • Add Linux parity: If telemetry settings can be managed on Linux, include equivalent instructions, such as command-line steps or configuration file edits.
  • Provide PowerShell and CLI alternatives: If only GUI instructions are given, add PowerShell or command-line examples for automation and remote management, and note their platform compatibility.
  • Mention cross-platform tools: If relevant, reference any cross-platform backup solutions or telemetry management tools.
  • Order of presentation: If both Windows and Linux are supported, present examples for both, or alternate which platform is shown first.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/monitoring-and-alerts-overview.md ...main/articles/backup/monitoring-and-alerts-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 in several ways. Windows-centric tools and patterns (such as PowerShell and Azure Backup Agent) are mentioned explicitly and often listed before cross-platform or Linux alternatives. Examples and references to PowerShell are given, but there are no explicit Linux shell (bash) or Linux-specific usage examples. Windows workloads (Azure Backup Agent, DPM, Azure Backup Server) are referenced, while Linux equivalents (such as Linux VM backup scenarios or Linux CLI usage) are not highlighted or exemplified. The documentation does not provide parity in examples or guidance for Linux users.
Recommendations
  • Include explicit Linux CLI (bash) examples alongside PowerShell, especially for common monitoring and reporting tasks.
  • Mention Linux VM backup scenarios and provide guidance or references for monitoring and reporting in Linux environments.
  • Ensure that Azure CLI usage is demonstrated with Linux shell syntax, not just referenced generically.
  • Add documentation sections or notes that address Linux-specific considerations, such as log locations, troubleshooting steps, and integration with Linux-native tools.
  • List cross-platform tools (Azure CLI, REST API) before Windows-specific tools (PowerShell) to avoid ordering bias.
  • Highlight any differences in monitoring and reporting workflows between Windows and Linux environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/multi-user-authorization.md .../blob/main/articles/backup/multi-user-authorization.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 consistently lists PowerShell examples before CLI, which can be interpreted as a 'Windows-first' bias. There are no explicit Linux shell (bash) examples, nor any mention of Linux-specific considerations, even though Azure CLI is cross-platform and commonly used on Linux. The documentation does not reference any Linux tools or patterns, and screenshots and UI instructions are focused on the Azure Portal, which is platform-agnostic, but the ordering and emphasis of PowerShell over CLI may disadvantage Linux users.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support Linux users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample shell environments (e.g., bash) where appropriate.
  • Add notes or sections for Linux users, such as installation prerequisites for Azure CLI on Linux, or troubleshooting tips specific to Linux environments.
  • Include screenshots or terminal output examples from Linux shells to demonstrate parity.
  • Where possible, avoid assuming PowerShell as the default scripting environment, and clarify that both PowerShell and CLI are supported equally.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/move-to-azure-monitor-alerts.md ...b/main/articles/backup/move-to-azure-monitor-alerts.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 primarily by referencing PowerShell and the Azure portal as the main interfaces for alert visibility and management, with no mention of Linux-specific tools or workflows. The exceptions section explicitly lists 'portal/PowerShell/the CLI clients' as the means by which users are immediately aware of job results, but PowerShell is mentioned before CLI, and there are no examples or instructions for Linux users. Notification configuration is stated to be available only via the Azure portal, with no guidance for Linux command-line users. There are no Linux-specific examples, nor are cross-platform CLI commands provided.
Recommendations
  • Add Azure CLI examples for alert management and notification configuration, highlighting cross-platform compatibility.
  • Explicitly mention Linux support and provide instructions for Linux users where applicable.
  • Ensure that CLI commands (az backup, etc.) are presented before or alongside PowerShell examples.
  • Clarify any platform limitations and provide alternative workflows for Linux users if certain features are portal-only.
  • Include screenshots or terminal output from Linux environments to demonstrate parity.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-azure-data-box.md .../main/articles/backup/offline-backup-azure-data-box.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 toward Windows environments. All supported platforms listed are Windows SKUs, with no mention of Linux or macOS. All examples, prerequisites, and troubleshooting steps use Windows-specific tools (PowerShell, Control Panel, PsExec, registry editor, etc.), and the MARS Agent is referenced exclusively in the context of Windows. There are no Linux equivalents or instructions, and Windows tools and patterns are mentioned exclusively and first throughout the guide.
Recommendations
  • Explicitly state platform limitations at the beginning, clarifying if Linux is unsupported or if support is planned.
  • If Linux support is possible, provide equivalent instructions for Linux environments, including supported distributions, required packages, and alternative commands (e.g., Bash, Azure CLI).
  • Offer Linux-based examples for mounting Data Box devices (e.g., using NFS utilities on Linux).
  • Include troubleshooting steps relevant to Linux systems, such as log file locations and certificate management.
  • If the MARS Agent is Windows-only, suggest alternative backup solutions for Linux users and link to relevant documentation.
  • Avoid assuming Windows as the default environment; structure documentation to address cross-platform needs or clarify scope.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-server-previous-versions.md ...cles/backup/offline-backup-server-previous-versions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 strong Windows bias. All examples, instructions, and screenshots are centered on Windows Server, Windows clients, DPM, and MABSβ€”products that are Windows-only. The workflow relies on Windows-specific tools (e.g., AzureOfflineBackupCertGen.exe, AzureOfflineBackupDiskPrep.exe), registry edits, and command prompt usage. There is no mention of Linux equivalents, nor are Linux scenarios or tools discussed. PowerShell commands are referenced for Azure user ID retrieval, further reinforcing the Windows-centric approach.
Recommendations
  • Explicitly state that the workflow is only supported on Windows and clarify Linux is not supported, if that is the case.
  • If Linux support is possible, provide equivalent instructions, tools, and examples for Linux environments (e.g., bash commands, Linux utilities, alternative workflows).
  • Include a section comparing Windows and Linux support for offline backup, listing limitations and alternatives for Linux users.
  • Avoid assuming the use of Windows-only features (e.g., registry edits, .exe utilities, Certlm.msc) without mentioning platform restrictions.
  • If Azure Import/Export can be used from Linux, provide guidance on preparing disks and managing jobs from Linux systems.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-azure-data-box-dpm-mabs.md ...icles/backup/offline-backup-azure-data-box-dpm-mabs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All instructions, examples, and prerequisites are specific to Windows Server (2016/2019) and Windows-based backup solutions (DPM, MABS). The use of Windows-specific tools (PSExec, regedit, Windows registry paths), reliance on Windows features (Client for NFS), and PowerShell modules are pervasive. There are no examples, instructions, or mentions of Linux or cross-platform alternatives, and the supported platforms section lists only Windows Server versions.
Recommendations
  • Add explicit statements about Linux support or lack thereof for DPM/MABS and Azure Data Box workflows.
  • If Linux support is possible, provide equivalent instructions for Linux servers, including mounting Data Box via NFS, certificate management, and Azure CLI usage.
  • Include Linux-specific troubleshooting steps and examples, such as using OpenSSL for certificate management, Linux mount commands, and relevant Azure CLI commands.
  • Mention cross-platform alternatives to Windows-only tools (e.g., alternatives to PSExec, regedit) where possible.
  • Clarify in the prerequisites and supported platforms section whether Linux is unsupported or provide parity guidance for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-azure-files-vault-tier-arm.md ...cles/backup/quick-backup-azure-files-vault-tier-arm.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 and referencing PowerShell for backup management and restoration tasks before mentioning Azure CLI or REST API alternatives. No explicit Linux or cross-platform command-line examples (such as Azure CLI or Bash) are given for template deployment, and PowerShell is presented as the primary method for several operations.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell, showing equivalent commands for Linux/macOS users.
  • Present both PowerShell and CLI examples in parallel, or use CLI as the default for cross-platform parity.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or Bash, and provide links or code snippets.
  • Reorder instructions so that cross-platform tools (CLI, REST API) are mentioned before or alongside PowerShell.
  • Include a table or section summarizing all supported deployment methods (Portal, PowerShell, CLI, REST API) with links and examples.
GitHub Create Pull Request
← Previous Page 28 of 65 Next →