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 1076-1100 of 1604 flagged pages
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-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows environments, specifically focusing on Data Protection Manager (DPM), which is a Windows-only tool. All instructions, screenshots, and terminology assume the use of Windows Server, Windows-based SQL Server, and Windows authentication patterns (e.g., NTAuthority\System). There are no examples, guidance, or mentions of Linux-based SQL Server deployments or equivalent backup workflows for Linux environments.
Recommendations
  • Add a section or parallel documentation for backing up SQL Server running on Linux VMs or containers, using Azure Backup or other supported tools.
  • Explicitly state that DPM is a Windows-only solution and provide alternative recommendations for Linux users (e.g., Azure Backup integration with Linux, or using native SQL Server backup/restore commands with Azure Blob Storage).
  • Include examples and screenshots for Linux-based SQL Server environments, if supported, or clearly direct Linux users to relevant documentation.
  • Mention and link to cross-platform or Linux-native backup tools and workflows where applicable.
  • Ensure that prerequisite and limitation sections clarify OS support and provide parity guidance for non-Windows environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/back-up-managed-disks-tutorial.md ...main/articles/backup/back-up-managed-disks-tutorial.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation primarily focuses on Azure Portal UI steps and, where automation is mentioned, references PowerShell before CLI. There are no explicit Linux or cross-platform command-line examples, and scripting is described in terms of PowerShell or CLI, with PowerShell listed first. No Linux-specific tools, shell commands, or considerations are provided, and the overall flow assumes a Windows-centric audience.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples, as CLI is cross-platform and works natively on Linux, macOS, and Windows.
  • Explicitly mention that all CLI commands can be run on Linux, macOS, or Windows, and provide sample shell commands for Linux users.
  • Where scripting is referenced, avoid listing PowerShell before CLI unless there is a technical reason; consider listing CLI first for cross-platform parity.
  • Add a section or callout for Linux/macOS users, clarifying that all operations can be performed from their platforms using Azure CLI.
  • If automation scripts are provided, include Bash shell script examples in addition to PowerShell.
  • Ensure that any downloadable scripts or templates are available in both PowerShell and Bash formats.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-architecture.md ...-docs/blob/main/articles/backup/backup-architecture.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by focusing on Windows-specific backup agents (MARS, DPM, MABS), providing detailed architectural descriptions and workflows only for Windows/on-premises Windows Server scenarios, and omitting equivalent Linux backup workflows or agents. Linux is mentioned only to state that certain features are unsupported, and there are no Linux-specific examples, tools, or architectural diagrams. The documentation also lists Windows backup options before Azure VM or cross-platform options, and does not provide parity in guidance for Linux workloads.
Recommendations
  • Add explicit coverage of Linux backup scenarios, including supported methods for backing up on-premises Linux machines (e.g., via Azure Backup Server, third-party tools, or native Azure VM backup).
  • Include architectural diagrams and step-by-step workflows for Linux backup scenarios, similar to those provided for Windows/MARS agent.
  • Clearly state the limitations and alternatives for Linux backup, and provide links to relevant Linux backup documentation.
  • Ensure that examples and feature tables include both Windows and Linux where applicable, or clarify when features are Windows-only.
  • Where possible, present Azure VM backup (which supports both Windows and Linux) before Windows-only solutions, to avoid a 'windows_first' impression.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-about-mars.md ...s/blob/main/articles/backup/backup-azure-about-mars.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example Windows First 🔧 Windows Tools
Summary
The documentation for the MARS Agent is heavily focused on Windows environments. All backup and recovery scenarios, process steps, and technical details are described exclusively for Windows systems, with explicit references to Windows-specific features (e.g., VSS, USN change journal, Windows volumes, system state). There are no examples, instructions, or mentions of Linux support or equivalent Linux tools. The documentation implicitly assumes the user is operating in a Windows environment.
Recommendations
  • Clearly state the platform support for the MARS Agent at the beginning of the documentation. If Linux is not supported, explicitly mention this to set user expectations.
  • If Linux support is planned or available, add equivalent Linux examples, scenarios, and technical details (e.g., how to back up Linux files/folders, which snapshotting tools are used, etc.).
  • Where Windows-specific tools or patterns are mentioned (e.g., VSS, USN journal), provide Linux equivalents or clarify that these features are not available/applicable on Linux.
  • Add a comparison table or section outlining feature parity (or lack thereof) between Windows and Linux for the MARS Agent.
  • Ensure that any future updates to the documentation include Linux examples and instructions if/when support is added.
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-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references Azure Backup Server and Data Protection Manager (DPM), both of which are Windows-only tools. All instructions, screenshots, and terminology are tailored to the Windows GUI and ecosystem, with no mention of Linux-based backup servers, command-line alternatives, or cross-platform recovery workflows. There are no Linux or PowerShell/Bash examples, but the bias is toward Windows GUI tools and patterns.
Recommendations
  • Explicitly state that Azure Backup Server and DPM are Windows-only solutions at the beginning of the article.
  • If Linux-based backup and recovery is supported, provide parallel instructions or links for Linux environments (e.g., using Azure CLI, Recovery Services Vault with Linux VMs, or other supported Linux backup agents).
  • Include a comparison table or section outlining backup and recovery options for both Windows and Linux workloads.
  • Where possible, add command-line examples (PowerShell for Windows, Bash/Azure CLI for Linux) to supplement GUI instructions.
  • Reference Linux-specific documentation for users seeking to recover data from Linux-based systems.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-alternate-dpm-server-troubleshoot.md ...ckup/backup-azure-alternate-dpm-server-troubleshoot.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows environments, referencing only Windows Server, Windows Client, and Microsoft-specific tools (such as DPM and Azure Backup Server) without any mention of Linux equivalents or cross-platform considerations. There are no troubleshooting steps or examples for Linux-based systems, nor is it clarified whether the guidance is applicable to non-Windows environments.
Recommendations
  • Explicitly state whether Azure Backup Server supports Linux or is Windows-only. If Linux is supported, include troubleshooting steps and examples for Linux environments.
  • If the product is Windows-only, clarify this at the beginning of the documentation to set expectations for Linux users.
  • Where possible, provide parity in documentation by including Linux command-line examples (e.g., Bash) or references to Linux backup/recovery tools if supported.
  • Mention any cross-platform limitations or alternative solutions for Linux users, such as using Azure Backup for Linux VMs or other supported agents.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-restore-vms.md ...b/main/articles/backup/backup-azure-arm-restore-vms.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias in several areas: Windows-specific examples and references (such as PowerShell and Windows tutorials) are given without equivalent Linux instructions; Windows terminology and tools are mentioned first or exclusively; and some advanced scenarios (e.g., restoring VMs with special network configurations or domain controllers) focus on Windows workflows. Linux-specific guidance is minimal or absent, and there are few, if any, CLI or Linux-native examples.
Recommendations
  • Provide equivalent Linux examples and references wherever Windows/PowerShell examples are given (e.g., using Azure CLI or Bash scripts for restore operations).
  • Include links to Linux-specific documentation (e.g., restoring Linux VMs, handling cloud-init, or troubleshooting Linux agent issues).
  • Balance references to Windows and Linux in scenario tables and guidance, ensuring both platforms are equally represented.
  • When mentioning tools or workflows (such as PowerShell), also mention and provide examples for their Linux/CLI counterparts.
  • Add explicit notes or sections for Linux-specific post-restore steps, such as handling SSH keys, cloud-init, and agent installation.
  • Review scenario coverage (e.g., SQL VMs, domain controllers) to ensure Linux equivalents (e.g., restoring MySQL/PostgreSQL VMs, LDAP servers) are addressed.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-bicep-file.md ...lob/main/articles/backup/quick-backup-vm-bicep-file.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All deployment and cleanup examples use Azure PowerShell scripts, with no mention or example of Azure CLI or Bash equivalents. The Bicep template provisions only Windows VMs, and the allowed OS versions are exclusively Windows. The instructions and references (such as monitoring and starting backup jobs) link to PowerShell-specific guides. There is no guidance for Linux users or for deploying/protecting Linux VMs.
Recommendations
  • Provide parallel Azure CLI/Bash examples for deploying the Bicep template, starting backup jobs, monitoring, and cleanup.
  • Include or reference a Bicep template that provisions a Linux VM, or show how to modify the template for Linux.
  • Mention both Windows and Linux options in the prerequisites and throughout the guide, including links to relevant Linux documentation.
  • When referencing tools or scripts, present cross-platform options (e.g., Azure CLI before or alongside PowerShell).
  • Ensure that links to further reading or next steps include Linux-focused guides as well as Windows ones.
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-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes backup procedures using System Center Data Protection Manager (DPM), a Windows-only tool, and focuses on Microsoft Exchange Server, which is also a Windows-based application. All instructions, screenshots, and examples are based on Windows environments, with no mention of Linux equivalents, cross-platform tools, or alternative approaches for non-Windows systems.
Recommendations
  • Clearly state at the beginning that the guide is specific to Windows environments and DPM, and provide links to cross-platform or Linux-based backup solutions if available.
  • If Azure Backup supports Linux-based workloads or Exchange alternatives on Linux, include parallel documentation or references for those scenarios.
  • Where possible, mention or link to Azure-native backup options or third-party tools that support Linux servers and applications.
  • Add a comparison table or section outlining backup options for both Windows and Linux environments, helping users identify the right tool for their platform.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-import-export.md ...n/articles/backup/backup-azure-backup-import-export.md
High Priority View Details →
Scanned: 2025-07-08 04:23
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 instructions, prerequisites, and tooling (such as the MARS agent, AzureOfflineBackupDiskPrep utility, and Azure PowerShell) are Windows-specific. There are no examples or guidance for Linux systems, and the workflow assumes the use of Windows-only tools and patterns (e.g., elevated command prompt, Windows file paths, Internet Explorer/Edge). Linux users are not addressed, and there is no mention of cross-platform alternatives.
Recommendations
  • Explicitly state early in the documentation that the workflow is only supported on Windows, if that is the case. If Linux is not supported, clarify this to set user expectations.
  • If Linux support is possible, provide equivalent instructions, tooling, and examples for Linux environments (e.g., bash commands, Linux-compatible utilities, and browser requirements).
  • Mention any cross-platform or Linux-compatible Azure backup agents or workflows, if available.
  • Where PowerShell or Windows-specific tools are required, suggest or link to alternatives for Linux (such as Azure CLI or REST API usage).
  • Avoid assuming the presence of Windows-only browsers (Edge, Internet Explorer); mention cross-platform browser support if applicable.
  • Include a comparison table or section that outlines supported OSes and any limitations for non-Windows users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-server-import-export.md ...les/backup/backup-azure-backup-server-import-export.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows environments, specifically referencing System Center Data Protection Manager (DPM), Microsoft Azure Backup Server (MABS), and the Microsoft Azure Recovery Services (MARS) agent—all Windows-only products. All examples, prerequisites, and workflows assume a Windows system, referencing Windows-specific tools (e.g., AzureOfflineBackupDiskPrep.exe), Windows PowerShell, and browsers like Microsoft Edge or Internet Explorer. There are no Linux equivalents, examples, or guidance for performing offline seeding from Linux systems, nor is it clarified whether the workflow is possible from non-Windows environments.
Recommendations
  • Explicitly state in the prerequisites and introduction whether the workflow is supported or unsupported on Linux systems.
  • If possible, provide Linux-compatible tools or scripts for preparing disks and interacting with the Azure Import/Export service.
  • Include example workflows or guidance for performing offline seeding from Linux servers, or provide links to relevant Linux documentation if available.
  • Mention cross-platform alternatives (such as Azure CLI or REST APIs) where possible, and provide usage examples for Linux environments.
  • Clarify any limitations or required workarounds for Linux administrators who need to seed data to Azure.
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-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments. All command-line examples use PowerShell, and all configuration steps reference Windows tools (such as Registry Editor and Certificate Import Wizard). There are no examples or instructions for performing equivalent tasks on Linux-based Azure Backup Server deployments, nor is there mention of Linux compatibility or alternatives. Windows-specific patterns (e.g., .reg files, Windows services, Windows-style file paths) are used exclusively and presented as the default or only approach.
Recommendations
  • Add equivalent instructions and examples for Linux-based deployments, including how to import certificates, modify configuration files, and manage services.
  • Provide shell (bash) script examples alongside PowerShell for tasks like disk exclusion or service management.
  • Clarify whether Azure Backup Server is supported on Linux, and if not, explicitly state this early in the documentation.
  • When referencing tools (e.g., Registry Editor, Certificate Import Wizard), mention Linux alternatives or note their absence.
  • Use neutral language and ordering (e.g., 'On Windows, do X. On Linux, do Y.') when describing platform-specific steps.
  • If certain features or scripts (like ExcludeDisk.ps1) are Windows-only, 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/backup-azure-backup-sharepoint-mabs.md ...articles/backup/backup-azure-backup-sharepoint-mabs.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All instructions, tools, and examples assume a Windows Server context, with exclusive references to Windows-specific tools (e.g., Registry Editor, CMD, NT AUTHORITY\SYSTEM, %Program Files%, Windows registry paths, and Windows service accounts). There are no Linux equivalents or cross-platform guidance, and no mention of Linux-based SharePoint deployments or Azure Backup Server usage on Linux. All command-line examples use Windows CMD, and all administrative procedures reference Windows UI or Windows-specific concepts.
Recommendations
  • Explicitly state that MABS and SharePoint backup are only supported on Windows, if that is the case. If Linux is not supported, clarify this early in the documentation.
  • If any part of the workflow is possible on Linux (e.g., Azure Backup Server components, agent installation, or monitoring), provide equivalent Linux instructions and examples.
  • For command-line operations, provide PowerShell and, if possible, Bash or cross-platform CLI alternatives.
  • Replace or supplement Windows-specific paths (e.g., %Program Files%, registry keys) with Linux equivalents or note their absence.
  • Mention any limitations or lack of support for Linux environments explicitly, so Linux administrators are not misled.
  • If the product is Windows-only, consider a brief section explaining why, and link to any roadmap or alternatives for Linux environments.
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-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references System Center Data Protection Manager (DPM), a Windows-only backup solution, and provides instructions and screenshots for Windows environments without mentioning Linux alternatives or providing cross-platform guidance. There are no examples or guidance for Linux-based SharePoint deployments or backup tools, and the documentation assumes the use of Windows-native tools and interfaces throughout.
Recommendations
  • Acknowledge that DPM is a Windows-only solution and clarify platform limitations early in the documentation.
  • Provide information or links to alternative backup solutions for SharePoint on Linux (if supported), or explicitly state if Linux-based SharePoint deployments are not supported.
  • If possible, include parity documentation for Linux-based backup tools (such as Azure CLI, AzCopy, or third-party solutions) for similar backup scenarios.
  • Add a comparison table or section outlining platform support and tool availability for both Windows and Linux environments.
  • Ensure that future documentation for Azure Backup scenarios includes both Windows and Linux examples where applicable.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-delete-vault.md ...blob/main/articles/backup/backup-azure-delete-vault.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias through heavy reliance on PowerShell scripts and commands, exclusive mention of Windows-centric tools (such as MARS, MABS, DPM, and ARMClient via Chocolatey), and a lack of Linux or cross-platform alternatives. Instructions for deleting backup items and vaults are primarily provided for Windows tools and interfaces, with no equivalent examples for Linux environments or Bash scripting. The CLI section is minimal and notes limited support, while the PowerShell and management console instructions are detailed and Windows-specific.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for all major operations, including vault and backup item deletion, and ensure these are as detailed as the PowerShell examples.
  • Mention and demonstrate installation and usage of Azure CLI and ARMClient on Linux/macOS, not just via Chocolatey (Windows).
  • Include guidance for managing Recovery Services vaults from Linux-based environments, including any differences or limitations.
  • When referencing management consoles (MARS, MABS, DPM), clarify their platform support and, if Windows-only, suggest alternatives or note limitations for Linux users.
  • Ensure that examples and tool recommendations are presented in a platform-neutral order, or provide parallel instructions for both Windows and Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-database-postgresql.md ...in/articles/backup/backup-azure-database-postgresql.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell is emphasized as the primary scripting method, with a dedicated section for running a PowerShell script to grant privileges. The instructions for setting up the environment variables for PSQL are explicitly Windows-centric, referencing Control Panel and System Properties, with screenshots and steps only for Windows. There are no equivalent instructions or examples for Linux or macOS users, and Linux command-line patterns are not mentioned. While the PSQL tool is referenced, its usage is only contextualized within a Windows environment.
Recommendations
  • Provide parallel instructions and screenshots for Linux and macOS environments, especially for setting environment variables and running scripts.
  • Include bash or shell script examples alongside PowerShell, or at least mention how to adapt the PowerShell script for non-Windows platforms.
  • When referencing tools like PSQL, show how to install and configure them on Linux (e.g., using apt or yum) and macOS (e.g., using Homebrew).
  • Avoid assuming the user is on Windows; use cross-platform language and clarify when steps differ by OS.
  • Add notes or links to official PostgreSQL documentation for Linux/macOS users regarding environment setup and script execution.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-template.md .../blob/main/articles/backup/quick-backup-vm-template.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All code examples are provided exclusively in PowerShell, with explicit instructions for using PowerShell in the Azure Cloud Shell. The ARM template referenced is described as deploying a 'simple Windows VM', with no mention of Linux VM options or examples. Linux command-line tools or Bash/CLI examples are not provided, and the workflow assumes familiarity with Windows-centric tools and patterns.
Recommendations
  • Add equivalent Azure CLI (Bash) examples for deploying the ARM template, including step-by-step instructions.
  • Reference and, if possible, provide an ARM template example for deploying and backing up a Linux VM, or clarify how to adapt the template for Linux.
  • Ensure that mentions of deployment methods (PowerShell, CLI, Portal, REST) give equal prominence to Azure CLI/Bash and not just PowerShell.
  • Include cleanup instructions using Azure CLI, not just PowerShell cmdlets.
  • Where possible, use neutral language (e.g., 'virtual machine' instead of 'Windows VM') unless the example is truly Windows-specific, and clarify applicability to Linux.
  • Provide links to Linux-specific backup/restore documentation if available.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-blob-vaulted-backup-cli.md .../main/articles/backup/quick-blob-vaulted-backup-cli.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows subtle Windows bias by referencing PowerShell and linking to PowerShell-based instructions (e.g., for creating a Backup vault and restoring blobs) before or in addition to CLI examples. There is no explicit mention of Linux or Bash environments, and the linked PowerShell instructions may not be directly usable on Linux or macOS systems. The documentation does not provide Linux-specific guidance or parity in example scripts.
Recommendations
  • Ensure that all referenced instructions (such as creating a Backup vault and restoring blobs) include both Azure CLI and PowerShell options, with CLI (cross-platform) examples presented first.
  • Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and provide Bash shell examples where appropriate.
  • Avoid linking only to PowerShell-based guides; always provide a CLI alternative or make it clear when a step is Windows-specific.
  • Add a note in the prerequisites clarifying that the quickstart is cross-platform and does not require Windows or PowerShell.
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-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows environments, specifically referencing System Center DPM, Windows PowerShell, and .NET Framework as prerequisites. All instructions, tools, and screenshots assume a Windows GUI and Windows-based workflows. There are no examples, instructions, or considerations for Linux-based DPM servers or cross-platform scenarios. Linux equivalents for agent installation, prerequisites, or command-line operations are not mentioned.
Recommendations
  • Explicitly state that DPM is a Windows-only product, if that is the case, or clarify Linux support status.
  • If Linux-based backup scenarios are supported (e.g., via MARS or Azure Backup agent), provide parallel instructions and examples for Linux environments.
  • List Linux prerequisites (such as required packages or dependencies) alongside Windows requirements.
  • Include Linux command-line examples (e.g., Bash, shell scripts) for agent installation, registration, and troubleshooting.
  • Mention and link to any Linux-native tools or agents that can be used for Azure Backup, if available.
  • If DPM is not available on Linux, suggest alternative Azure Backup solutions for Linux workloads and link to relevant documentation.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-encrypted-vm-troubleshoot.md ...icles/backup/backup-azure-encrypted-vm-troubleshoot.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the only CLI automation example and omitting explicit Linux or cross-platform CLI (e.g., Azure CLI, Bash) instructions. The mention of PowerShell for permission configuration is not balanced with equivalent Linux or cross-platform alternatives, and no Linux-specific tools or workflows are referenced.
Recommendations
  • Provide equivalent Azure CLI (az) command examples alongside or before PowerShell instructions for all automation and scripting steps.
  • Explicitly mention that steps can be performed from Linux, macOS, or Windows, and clarify any OS-specific differences.
  • Include Bash shell examples where relevant, particularly for scripting or automation tasks.
  • Review linked pages (such as backup-azure-vms-automation.md) to ensure Linux parity in automation instructions.
  • Avoid referencing only Windows-specific tools (like PowerShell) without cross-platform alternatives.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-terraform.md ...blob/main/articles/backup/quick-backup-vm-terraform.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively demonstrates how to back up a Windows virtual machine in Azure using Terraform. All examples, resource creation steps, and references are specific to Windows VMs, with no mention of Linux VM equivalents or how to adapt the process for Linux. The 'Next steps' section also directs users to more Windows VM articles, reinforcing the Windows-centric focus. There are no examples or guidance for Linux users, nor any mention of Linux-specific considerations.
Recommendations
  • Add parallel instructions and Terraform code samples for creating and backing up a Linux virtual machine, including any differences in resource definitions or backup procedures.
  • Update the checklist and step-by-step instructions to mention both Windows and Linux VM options, or provide a choice at the beginning for users to follow either path.
  • Include links to additional documentation or articles focused on Linux VM backup with Terraform.
  • Revise the 'Next steps' section to include resources for both Windows and Linux VMs.
  • Clarify in the introduction that the guide is Windows-specific, or broaden the scope to cover both operating systems.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-exchange-mabs.md ...lob/main/articles/backup/backup-azure-exchange-mabs.md
High Priority View Details →
Scanned: 2025-07-08 04:23
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 procedures for Microsoft Exchange Server using Microsoft Azure Backup Server (MABS), which is a Windows-only tool. All examples, instructions, and screenshots are based on the Windows GUI and Windows file paths. There is no mention of Linux-based Exchange alternatives, Linux backup agents, or cross-platform considerations. The documentation assumes a Windows environment throughout.
Recommendations
  • Clarify early in the documentation that MABS and Exchange Server are Windows-only, and explicitly state platform limitations.
  • If Azure Backup supports Linux workloads or other mail servers (e.g., Postfix, Dovecot), provide parallel documentation or links for Linux backup scenarios.
  • Where possible, mention or link to Azure Backup documentation for Linux servers, including agent installation and backup procedures.
  • Add a note or section addressing the lack of Linux support for this scenario, and suggest alternative solutions for Linux-based mail servers.
  • Ensure that future documentation for backup scenarios includes both Windows and Linux examples where supported.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-mabs-troubleshoot.md ...main/articles/backup/backup-azure-mabs-troubleshoot.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation for Azure Backup Server troubleshooting is heavily biased toward Windows environments. All examples, file paths, commands, and troubleshooting steps reference Windows-specific tools (e.g., Registry Editor, Windows Services, Windows Server Backup, Control Panel, Internet Explorer, Windows registry keys, Windows file paths). There are no examples, instructions, or even mentions of Linux or cross-platform scenarios, and all operational guidance assumes a Windows OS context.
Recommendations
  • Add explicit statements about platform support (e.g., clarify if Azure Backup Server is Windows-only or if Linux is supported).
  • If Linux is supported, provide equivalent troubleshooting steps, file paths, and commands for Linux environments.
  • Include Linux-specific examples for agent installation, service management, and backup/restore operations.
  • Reference Linux tools (e.g., systemctl, journalctl, Linux file paths) where appropriate.
  • If certain features or steps are Windows-only, clearly label them as such and provide alternatives or guidance for Linux users.
  • Ensure parity in documentation structure: for every Windows example or instruction, provide a Linux equivalent where possible.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-manage-mars.md .../blob/main/articles/backup/backup-azure-manage-mars.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on the Microsoft Azure Recovery Services (MARS) Agent, which is a Windows-only backup solution. All instructions, screenshots, and tool references are specific to Windows environments (e.g., MARS management console, %ProgramFiles% paths, Windows-style UI navigation). There are no Linux equivalents, examples, or mentions, and the documentation implicitly assumes the user is operating on Windows systems.
Recommendations
  • Clearly state at the beginning of the documentation that the MARS Agent is only supported on Windows, and provide links to equivalent Azure Backup solutions for Linux (such as Azure Backup for Linux VMs or Azure Backup Server).
  • Where possible, add a comparison table or section outlining backup options for both Windows and Linux, with links to relevant documentation for Linux users.
  • If any cross-platform features exist (e.g., Azure Backup Reports, Azure Monitor integration), provide Linux-specific instructions or examples alongside the Windows ones.
  • Avoid using only Windows-specific terminology and paths without clarification; if the product is Windows-only, make this explicit to avoid confusion for Linux users.
  • For antivirus configuration, mention that the guidance is for Windows and provide a note or link for Linux-based backup agent antivirus configuration if applicable.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-monitoring-built-in-monitor.md ...les/backup/backup-azure-monitoring-built-in-monitor.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric backup tools (DPM, MABS, MARS) and providing navigation examples that focus on Windows Server workloads. There are no explicit Linux or cross-platform examples, and the terminology and links (e.g., 'backup-azure-manage-windows-server.md') suggest a primary focus on Windows environments. Linux equivalents or guidance are missing.
Recommendations
  • Include explicit examples and navigation instructions for monitoring Linux-based backup workloads.
  • Mention and link to documentation for Linux backup agents or solutions supported by Azure Backup.
  • Balance references to Windows tools (DPM, MABS, MARS) with Linux-native or cross-platform backup solutions.
  • Add notes or sections clarifying how Linux workloads are monitored and any differences in portal experience.
  • Ensure that all examples and screenshots, if any, represent both Windows and Linux scenarios.
GitHub Create Pull Request
← Previous Page 44 of 65 Next →