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 951-975 of 1604 flagged pages
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: 2025-08-18 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While most instructions are GUI/portal-based and thus platform-agnostic, the only explicit command-line references for moving Backup vaults mention PowerShell first, and the linked PowerShell module, with the CLI mentioned second. There are no explicit Linux/bash examples, nor are there references to Linux-native tools or scripting patterns. The absence of bash or Linux shell examples, and the ordering of PowerShell before CLI, may subtly prioritize Windows users.
Recommendations
  • When referencing command-line options, provide both Azure CLI (az) and PowerShell examples side by side, or list Azure CLI first as it is cross-platform.
  • Include explicit bash/Linux shell script examples where scripting is discussed or implied.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide sample commands in bash syntax.
  • Avoid listing PowerShell before CLI unless there is a technical reason; consider alternating order or grouping both under 'Command-line options'.
  • Add a section or note for Linux/macOS users to ensure parity in scripting and automation guidance.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/troubleshoot-azure-files.md .../blob/main/articles/backup/troubleshoot-azure-files.md
High Priority View Details →
Scanned: 2025-08-18 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows environments by providing PowerShell scripts (with no Bash or CLI equivalents), referencing scripts and tools that are typically Windows-centric, and omitting Linux or cross-platform command-line examples. There are no instructions or troubleshooting steps tailored for Linux users, and all automation references are to PowerShell scripts.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for all PowerShell script references, especially for tasks like finding the Recovery Services vault or undeleting file shares.
  • When mentioning scripts, explicitly state if they are cross-platform or provide separate instructions for Windows (PowerShell) and Linux/macOS (Bash/CLI).
  • Include Linux-specific troubleshooting steps or notes where relevant, such as for file share access, permissions, or automation.
  • Review all links to scripts and tools to ensure Linux users are not excluded, and add parity where gaps exist.
  • In general, avoid assuming the user is on Windows; use neutral language and cross-platform tools (like Azure CLI) as the primary example, or present both Windows and Linux options side by side.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/whats-new.md ...Docs/azure-docs/blob/main/articles/backup/whats-new.md
High Priority View Details →
Scanned: 2025-08-18 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page for Azure Backup service release notes shows some evidence of Windows bias. Several features and updates reference Windows-specific tools (such as MARS agent and Microsoft Azure Backup Server), and Windows terminology is used without always providing Linux equivalents. In some cases, PowerShell is mentioned as a primary automation method, and Windows-based backup solutions (like MABS) are highlighted. While the page covers many cross-platform workloads (e.g., PostgreSQL, SAP HANA, AKS), the documentation tends to mention Windows tools and patterns first or exclusively, with less emphasis on Linux-native tooling or examples.
Recommendations
  • Wherever Windows-specific tools (e.g., MARS agent, MABS) are mentioned, clarify their platform limitations and provide equivalent Linux-native solutions or alternatives if available.
  • When referencing automation or scripting (e.g., PowerShell), also mention Azure CLI and provide example commands for both Windows and Linux environments.
  • Ensure parity in documentation by highlighting Linux support and tools (such as native Linux backup agents, shell scripts, or integration with Linux backup utilities) alongside Windows tools.
  • Add explicit notes or links to Linux documentation for features that are available cross-platform, to make it clear that Linux is equally supported.
  • Review the order of feature descriptions to avoid always listing Windows/PowerShell options first; alternate or group by platform where appropriate.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/modify-vm-policy-cli.md ...docs/blob/main/articles/backup/modify-vm-policy-cli.md
High Priority View Details →
Scanned: 2025-07-17 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing a file path example (C:\temp2\Policy.json) that is specific to Windows, without offering a Linux or cross-platform alternative. There are no Linux or macOS file path examples, and no mention of Linux-specific considerations for file handling. The documentation assumes a Windows environment for file operations, which may confuse or exclude Linux users.
Recommendations
  • Provide both Windows and Linux/macOS file path examples when referencing files (e.g., C:\temp2\Policy.json and /tmp/Policy.json).
  • Explicitly mention that the Azure CLI commands work on all platforms and clarify any platform-specific differences.
  • Include a note or section addressing common file path conventions for Linux/macOS users.
  • Ensure that screenshots, if any, and further examples are platform-neutral or show parity between Windows and Linux.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/pre-backup-post-backup-scripts.md ...main/articles/backup/pre-backup-post-backup-scripts.md
High Priority View Details →
Scanned: 2025-07-17 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing only Windows file paths and conventions (e.g., 'Drive:' notation, backslashes in paths), mentioning Windows-specific technologies (e.g., Exchange, SQL Server, SharePoint), and omitting any mention of Linux or cross-platform usage. There are no examples or instructions for Linux environments, nor any discussion of Linux-compatible scripting or file system conventions.
Recommendations
  • Include explicit guidance for Linux environments, such as using forward slashes in paths and Linux mount points (e.g., '/mnt/data').
  • Provide Linux-specific examples for ScriptingConfig.xml, including how to specify data sources and script paths.
  • Clarify whether MABS supports Linux agents and, if so, document any differences in script execution or configuration.
  • Mention Linux scripting languages (e.g., Bash, Python) and how to invoke them in the configuration.
  • Ensure that references to Windows technologies are balanced with Linux equivalents where applicable, or clearly state if only Windows is supported.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-alternate-dpm-server.md ...n/articles/backup/backup-azure-alternate-dpm-server.md
High Priority View Details →
Scanned: 2025-07-17 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes recovery using Azure Backup Server and System Center Data Protection Manager (DPM), both of which are Windows-only tools. All instructions, screenshots, and terminology are focused on the Windows GUI and workflow, with no mention of Linux-based recovery, command-line alternatives, or cross-platform considerations. There are no examples or guidance for Linux environments or tools.
Recommendations
  • Explicitly state in the introduction that Azure Backup Server and DPM are Windows-only, and clarify support for Linux workloads if any.
  • If Linux-based recovery is supported (e.g., for files backed up from Linux VMs), add equivalent instructions or reference documentation for Linux recovery scenarios.
  • Include command-line or script-based recovery examples (such as PowerShell for Windows and Bash/CLI for Linux, if supported).
  • Mention and link to Azure-native or cross-platform backup/recovery options for Linux users, such as Azure CLI or Recovery Services Vault operations for Linux VMs.
  • Ensure parity in documentation structure and detail for both Windows and Linux recovery workflows if both are supported.
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: 2025-07-17 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. When mentioning command-line options for moving Backup vaults, it lists PowerShell before CLI, and the PowerShell module is referenced directly, while the CLI reference is less prominent. There are no explicit Linux-specific examples or guidance, and no mention of Bash or Linux shell environments. The documentation assumes familiarity with PowerShell and does not provide parity for Linux users, such as Bash or cross-platform CLI examples, nor does it clarify that the Azure CLI is cross-platform.
Recommendations
  • When referencing command-line tools, list Azure CLI before or alongside PowerShell, and clarify that Azure CLI is cross-platform (Windows, Linux, macOS).
  • Provide explicit Bash/Linux shell examples where scripts or command-line operations are discussed, or at least mention that the Azure CLI commands work identically on Linux.
  • Where PowerShell modules are referenced, also provide equivalent Azure CLI commands and documentation links.
  • Add a section or note clarifying that all portal and Azure CLI instructions are applicable to Linux users, and provide links to Azure CLI installation and usage on Linux.
  • Avoid assuming PowerShell as the default scripting environment; use neutral language or provide both PowerShell and Bash/CLI script snippets.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-exchange-server.md ...articles/backup/backup-azure-backup-exchange-server.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Powershell Heavy Windows First
Summary
The documentation is heavily focused on Windows environments, specifically Microsoft Exchange and System Center DPM, both of which are Windows-only products. All instructions, tools, and examples assume a Windows Server environment, with references to Windows file paths, the DPM Administrator Console, and PowerShell automation. There are no Linux equivalents, examples, or even mentions of cross-platform scenarios, making the documentation inaccessible to Linux users or those seeking platform-neutral guidance.
Recommendations
  • Clearly state at the beginning that System Center DPM and Exchange Server are Windows-only products, and that the guide is not applicable to Linux environments.
  • If Azure Backup supports Linux servers or workloads, provide links or sections for Linux backup scenarios, including supported tools and workflows.
  • For automation, offer examples using cross-platform tools (such as Azure CLI) where possible, or clarify that PowerShell examples are only for Windows.
  • If any steps or concepts are relevant to Linux (e.g., Azure Backup agent installation, vault credential management), provide parallel Linux instructions or references.
  • Consider including a comparison table or FAQ addressing platform support and limitations.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-server-vmware.md ...n/articles/backup/backup-azure-backup-server-vmware.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments. All administrative steps, scripts, and configuration examples assume the use of Windows tools (e.g., Registry Editor, Certificate Import Wizard, PowerShell scripts). There are no instructions or examples for performing these tasks on Linux-based Azure Backup Server installations, nor are Linux equivalents for registry or certificate management provided. The documentation implicitly assumes the Azure Backup Server is running on Windows, with no mention of Linux support or parity.
Recommendations
  • Explicitly state if Azure Backup Server is only supported on Windows. If Linux is not supported, clarify this early in the documentation.
  • If Linux is supported, provide parallel instructions for Linux environments, including:
  • - How to import CA certificates using Linux tools (e.g., update-ca-certificates, keytool, etc.).
  • - How to configure equivalent settings (such as disabling certificate validation) using Linux configuration files or environment variables.
  • - How to run administrative scripts using Bash or Python, or provide Linux-compatible versions of PowerShell scripts.
  • - How to modify application settings that are stored in the Windows Registry on Linux (e.g., via config files or environment variables).
  • Add notes or callouts indicating which steps are Windows-specific and provide alternatives or guidance for Linux users.
  • Ensure that screenshots and UI references are not exclusively Windows-centric if Linux GUIs or CLI tools are available.
  • Consider including a section on cross-platform support and any limitations or differences between Windows and Linux deployments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-sharepoint.md ...main/articles/backup/backup-azure-backup-sharepoint.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation is heavily focused on System Center Data Protection Manager (DPM), a Windows-only tool, and references to PowerShell for automation. There are no examples or mentions of Linux-based backup solutions, commands, or cross-platform alternatives. All instructions and screenshots assume a Windows environment, and there is no guidance for Linux administrators or mixed OS environments.
Recommendations
  • Include information about cross-platform or Linux-compatible backup solutions for SharePoint (if any), or clarify that DPM is Windows-only and suggest alternatives for Linux environments.
  • Provide equivalent command-line examples for Linux where possible, or explicitly state the lack of Linux support.
  • If automation is discussed via PowerShell, mention if there are REST APIs, CLI tools, or other automation options usable from Linux.
  • Add a section addressing backup and restore strategies for organizations with non-Windows infrastructure, or link to relevant Azure/Linux documentation.
  • Clearly state the OS requirements and limitations at the beginning of the article to set expectations for non-Windows users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-microsoft-azure-backup.md ...articles/backup/backup-azure-microsoft-azure-backup.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. All installation, configuration, and operational steps assume the use of Windows Server, with no mention of Linux or cross-platform support. Only Windows tools (such as PowerShell cmdlets, Windows Server Deduplication, and Windows registry edits) are referenced, and all examples and instructions are specific to Windows. There are no Linux equivalents, examples, or even statements about (non)support for Linux platforms.
Recommendations
  • Explicitly state whether Linux is supported or not for Azure Backup Server. If not supported, clarify this early in the documentation.
  • If any Linux support exists (for agents, workloads, or management), add equivalent Linux installation and configuration instructions.
  • Provide examples using Linux tools (e.g., shell commands) where applicable, or clarify that only Windows tools are supported.
  • Include a comparison table of supported platforms (Windows vs. Linux) for transparency.
  • Mention any Linux-specific limitations or alternatives for users managing mixed environments.
  • If only Windows is supported, add a section recommending alternative backup solutions for Linux workloads.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-sql.md ...s/blob/main/articles/backup/backup-azure-backup-sql.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation is heavily oriented toward Windows environments, specifically focusing on Data Protection Manager (DPM), a Windows-only backup tool. All examples, workflows, and screenshots are based on the DPM GUI, which is only available on Windows. There is no mention of Linux-based SQL Server workloads, nor are there any instructions or examples for backing up SQL Server on Linux. The only automation reference is to PowerShell, a Windows-centric scripting environment.
Recommendations
  • Add a section or parallel documentation for backing up SQL Server on Linux to Azure, using supported tools (such as Azure CLI, azcopy, or native SQL tools).
  • Explicitly state that DPM is a Windows-only tool and provide alternatives for Linux environments, such as Azure Backup integration with Linux or third-party solutions.
  • Include command-line examples for Linux (bash, shell scripts) alongside PowerShell examples.
  • Mention and link to documentation for cross-platform backup solutions where available.
  • Ensure that automation and scripting guidance covers both PowerShell (Windows) and bash/CLI (Linux) scenarios.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-sql-mabs.md ...ocs/blob/main/articles/backup/backup-azure-sql-mabs.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes backup and recovery of SQL Server using Microsoft Azure Backup Server (MABS) and Data Protection Manager (DPM), both of which are Windows-only tools. All examples, screenshots, and workflows assume a Windows environment, with references to Windows-specific accounts (NTAuthority\System) and features. There are no mentions of Linux-based SQL Server deployments, nor are there any instructions or examples for Linux environments.
Recommendations
  • Clearly state early in the documentation that MABS and DPM are Windows-only solutions, and specify supported operating systems.
  • Provide guidance or links for backing up SQL Server running on Linux, such as using Azure Backup with Linux VMs or native SQL Server backup tools.
  • Include a section comparing backup options for SQL Server on Windows vs. Linux, highlighting parity and differences.
  • If possible, offer alternative workflows or references for Linux users, such as using Azure Backup for Linux VMs or scripting native SQL Server backups on Linux.
  • Avoid assuming all SQL Server deployments are on Windows; acknowledge cross-platform scenarios.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dpm-introduction.md .../main/articles/backup/backup-azure-dpm-introduction.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented towards Windows environments, specifically System Center DPM, which is a Windows-only product. All examples, prerequisites, and tooling references (such as PowerShell, .NET Framework, and MARSAgentInstaller.exe) are Windows-specific. There are no examples or guidance for Linux-based backup scenarios, nor are Linux tools or commands mentioned. The documentation assumes the use of Windows UI elements and Windows server environments throughout.
Recommendations
  • Clearly state at the beginning that DPM is a Windows-only product, and provide links or references to equivalent Azure Backup solutions for Linux workloads.
  • Where possible, include parallel documentation or links for backing up Linux servers to Azure using native Azure Backup agents or other supported Linux backup solutions.
  • If PowerShell or Windows tools are required, explicitly mention that these steps are for Windows, and provide alternative steps or references for Linux users where applicable.
  • Add a comparison table or section outlining backup options for both Windows and Linux environments to help users choose the right solution.
  • Ensure that troubleshooting and prerequisites sections clarify OS-specific requirements and direct Linux users to appropriate resources.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-protection-matrix.md .../main/articles/backup/backup-mabs-protection-matrix.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation exhibits a strong Windows bias: all detailed workload and recovery examples are for Windows-based systems and applications (e.g., Windows Server, SQL Server, Exchange, SharePoint), with Linux relegated to a single, limited section. Windows tools and patterns (e.g., NTFS, VSS, Control Panel, system state, bare metal recovery) are referenced throughout, while Linux-specific backup scenarios, tools, or recovery options are not discussed. The Linux section only covers VM-level backup, with no mention of file-level or application-level protection, and requires a Windows-based host for protection. There are no Linux command-line or configuration examples, and Windows terminology and requirements (e.g., NTFS, Visual C++ redistributable, Volume Shadow Copy Service) are presented as defaults.
Recommendations
  • Provide Linux-specific backup and recovery scenarios, including file-level and application-level protection, not just VM-level.
  • Include examples and documentation for Linux-native tools and filesystems (e.g., ext4, XFS, LVM), and clarify support or limitations.
  • Offer parity in documentation structure: for every Windows workload example, provide a Linux equivalent or explicitly state support status.
  • Add Linux command-line examples (e.g., shell scripts, CLI commands) for agent installation, configuration, and recovery.
  • Clarify whether Linux VMs can be protected with application consistency (e.g., using pre/post scripts or VSS-like mechanisms), and document procedures.
  • Avoid presenting Windows tools and patterns (e.g., NTFS, VSS, Control Panel) as the only or default approach; mention Linux alternatives or note their absence.
  • Explicitly state any limitations or roadmap for Linux support to set user expectations.
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: 2025-07-16 00:00
Reviewed by: Unknown
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 environments, command-line alternatives, or cross-platform considerations. There are no Linux-specific instructions, nor are there references to managing telemetry via non-Windows tools.
Recommendations
  • Clarify early in the documentation that MABS is a Windows-only product, if applicable. If not, provide equivalent instructions for Linux environments.
  • If telemetry settings can be managed via command-line or scripts (e.g., PowerShell, CLI), provide those examples and note their platform compatibility.
  • If a Linux version or alternative exists, include parallel steps and screenshots for Linux users.
  • Explicitly state platform limitations and suggest alternatives for non-Windows users, if MABS is not available on Linux.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-add-storage.md ...s/blob/main/articles/backup/backup-mabs-add-storage.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric: all instructions, screenshots, and examples assume Windows Server environments, specifically referencing Server Manager, ReFS, and PowerShell cmdlets. There are no Linux equivalents or cross-platform guidance, and all tooling and workflows are based on Windows-only features. Linux users are not addressed at all.
Recommendations
  • Clarify early in the documentation whether Azure Backup Server supports Linux as a host or if it is strictly a Windows-only product. If it is Windows-only, state this explicitly to avoid confusion.
  • If any features or workflows are available on Linux, provide parallel instructions and examples for Linux environments, including relevant CLI commands and storage management tools (e.g., using LVM, ext4/xfs, or Linux equivalents of storage pools).
  • Where PowerShell is used, offer Bash or shell script alternatives if Linux is supported.
  • Include screenshots or terminal output from Linux environments where applicable.
  • If Modern Backup Storage and workload-aware storage are not available on Linux, clearly state this and provide alternative recommendations for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/microsoft-azure-backup-server-protection-v3-ur1.md ...kup/microsoft-azure-backup-server-protection-v3-ur1.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a strong Windows bias. Windows workloads, tools, and file systems are prioritized throughout, with detailed support matrices and recovery options for Windows environments. Linux support is limited to guest VMs, with only file-consistent snapshots and no item-level/file-level recovery. Windows-specific technologies (NTFS, VSS, ReFS, deduplication, FAT/FAT32, system state, bare metal recovery) are referenced exclusively, and Linux is only mentioned in a single, minimal section. There are no Linux-native backup scenarios or examples, and no mention of Linux file systems or tools.
Recommendations
  • Provide Linux-native backup scenarios, not just Linux as a guest VM.
  • Include item-level/file-level recovery options for Linux VMs, or clearly state limitations and possible workarounds.
  • Add examples and documentation for Linux file systems (e.g., ext4, XFS) and clarify their support status.
  • Mention Linux tools and patterns where relevant, not just Windows-specific technologies like VSS, NTFS, ReFS.
  • Ensure parity in documentation structure: for every Windows example or scenario, provide a Linux equivalent or explicitly state if unsupported.
  • Clarify agent support and installation procedures for Linux workloads, not just Windows.
  • Consider a dedicated section for Linux backup and recovery best practices, limitations, and troubleshooting.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/microsoft-azure-backup-server-protection-v3-ur1.md ...kup/microsoft-azure-backup-server-protection-v3-ur1.md
High Priority View Details →
Scanned: 2025-07-15 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a strong Windows bias: all detailed workload examples, backup scenarios, and recovery options are focused on Windows operating systems and Microsoft applications. Linux is only mentioned as a VM guest, with minimal detail and no parity in backup/recovery features (e.g., only entire VM backup, no file-level restore). Windows-specific tools and patterns (NTFS, VSS, ReFS, deduplication, system state, bare metal recovery) are referenced throughout, with no Linux equivalents or alternatives described.
Recommendations
  • Provide Linux-specific backup and recovery examples, including supported filesystems, backup types (e.g., file-level, application-aware), and restore options.
  • Clarify limitations and feature gaps for Linux workloads, and offer guidance or workarounds where possible.
  • Mention Linux tools or patterns (e.g., LVM snapshots, ext4/xfs support, Linux backup agents) where relevant.
  • Ensure Linux support is described with the same level of detail as Windows, including supported distributions, backup scenarios, and recovery procedures.
  • If certain features are Windows-only, explicitly state this and suggest alternative approaches for Linux environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/microsoft-azure-backup-server-protection-v3-ur1.md ...kup/microsoft-azure-backup-server-protection-v3-ur1.md
High Priority View Details →
Scanned: 2025-07-14 17:05
Reviewed by: Unknown
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 and tools are described in detail and appear first in all tables and sections. Linux support is limited to guest VMs, with no examples or details for native Linux workloads, file systems, or application backups. Windows-specific technologies (NTFS, VSS, ReFS, Windows domains, etc.) are referenced throughout, while Linux equivalents are not mentioned. Recovery options for Linux are limited and less granular than for Windows. There are no PowerShell examples, but the overall structure and content heavily favor Windows environments.
Recommendations
  • Add explicit examples and documentation for protecting native Linux workloads (e.g., file-level backup, application backup for Linux-based apps like MySQL, PostgreSQL).
  • Include Linux file system support details (e.g., ext4, xfs, btrfs) and clarify any limitations or requirements.
  • Describe Linux-specific backup and recovery workflows, including agent installation and configuration on Linux systems.
  • Provide parity in recovery options for Linux VMs (e.g., item-level/file-level recovery) or clearly state limitations and roadmap.
  • Reference Linux authentication and domain/workgroup equivalents where Windows domains are discussed.
  • List Linux tools or commands where Windows tools (e.g., VSS, NTFS, ReFS) are mentioned, or clarify that such features are unavailable.
  • Reorganize tables and sections to give Linux workloads equal prominence, not always after Windows.
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: 2025-07-14 17:05
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All workload examples, supported platforms, and backup scenarios are focused on Windows operating systems and Microsoft workloads (Windows Server, SQL Server, Exchange, SharePoint, Hyper-V). Linux is only mentioned as a guest OS in Hyper-V or VMware, with no details on native Linux backup, file-level recovery, or parity of features. Windows-specific tools and technologies (NTFS, VSS, ReFS, Windows Management Framework, NTLM authentication) are referenced throughout, and there are no Linux-specific instructions, requirements, or examples. The matrix and narrative consistently list Windows scenarios first or exclusively.
Recommendations
  • Add explicit support matrix rows for native Linux workloads (not just as VMs), including supported distributions, file systems, and backup/recovery capabilities.
  • Provide Linux-specific requirements, limitations, and supported features (e.g., file-level backup, application-aware backup, snapshot mechanisms like LVM or filesystem freeze).
  • Include Linux examples and scenarios alongside Windows ones, ensuring parity in documentation structure and detail.
  • Reference Linux tools and patterns (e.g., ext4, XFS, LVM, rsync, SSH-based authentication) where relevant.
  • Clarify any feature gaps or differences between Windows and Linux support, and provide guidance or workarounds for Linux users.
  • Avoid listing only Windows-specific technologies (NTFS, VSS, ReFS) without mentioning Linux equivalents or alternatives.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references the Microsoft Azure Backup Server (MABS) console, which is a Windows-only application, and all instructions are given through its GUI. There are no examples or mentions of Linux tools, command-line alternatives, or cross-platform considerations. The documentation assumes a Windows environment throughout.
Recommendations
  • Clarify early in the documentation that MABS is a Windows-only product, if that is the case, to set expectations for Linux users.
  • If any telemetry management is possible via command-line (e.g., PowerShell), provide those commands and note their platform compatibility.
  • If there are equivalent Azure Backup solutions or telemetry management options for Linux servers, link to those or provide a brief mention.
  • Explicitly state the platform requirements and limitations to avoid confusion for non-Windows administrators.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-monitor-troubleshoot.md ...n/articles/backup/backup-azure-monitor-troubleshoot.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively references Windows tools and patterns, such as Task Manager, Control Panel, and Windows file paths, without mentioning Linux equivalents or providing Linux-specific troubleshooting steps. There are no examples or instructions for users running Azure Backup on Linux systems.
Recommendations
  • Include troubleshooting steps for Linux environments, such as using 'ps', 'systemctl', or 'journalctl' to check and manage the agent process.
  • Provide Linux file path examples for log locations (e.g., /var/opt/microsoft/azure-recoveryservices-agent/log/).
  • Mention both Windows and Linux agent process names and management commands.
  • Structure instructions so that both Windows and Linux users can easily find relevant guidance, possibly with separate sections or side-by-side examples.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/query-backups-using-azure-resource-graph.md ...les/backup/query-backups-using-azure-resource-graph.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. In the 'Getting started' section, PowerShell is mentioned first among automation clients, ahead of CLI and SDK options. There are no explicit Linux or cross-platform shell (e.g., Bash) examples, nor are Linux-specific tools or workflows referenced. The sample queries are platform-agnostic (Kusto), but the automation guidance implicitly prioritizes Windows/PowerShell users.
Recommendations
  • List Azure CLI before PowerShell when mentioning automation clients, or present both together to avoid implying a platform preference.
  • Explicitly mention that both PowerShell and Azure CLI are cross-platform, and provide links to installation/use on Linux/macOS as well as Windows.
  • Add sample usage snippets for both PowerShell and Azure CLI (and/or Bash) to demonstrate parity.
  • Reference Linux/macOS environments in automation and scripting contexts, not just Windows.
  • Consider including a short section or note on using ARG queries from Linux terminals, with example commands.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-kubernetes-backup-bicep.md .../main/articles/backup/quick-kubernetes-backup-bicep.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively providing PowerShell deployment instructions and referencing the Azure PowerShell module as a prerequisite. There are no examples or instructions for deploying the Bicep template using Azure CLI, Bash, or other cross-platform tools. This may hinder Linux or Mac users who are more likely to use CLI or Bash scripts.
Recommendations
  • Add equivalent Azure CLI (az) deployment instructions alongside the PowerShell example, including both script and command-line usage.
  • Mention both Azure PowerShell and Azure CLI as valid prerequisites for deployment, and provide installation links for both.
  • Explicitly state that the deployment steps can be performed on any platform (Windows, Linux, Mac) using the Azure CLI.
  • Where possible, provide Bash script snippets for Linux/Mac users, or at least show the az deployment group create command.
  • Ensure that references to shell actions (e.g., 'right-click the shell window') are platform-neutral or include alternatives for Linux/Mac terminals.
GitHub Create Pull Request
← Previous Page 39 of 65 Next →