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 1101-1125 of 1604 flagged pages
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-install-backup-extension.md
...main/articles/backup/quick-install-backup-extension.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation primarily describes installation steps using the Azure Portal UI, which is platform-agnostic. However, in the 'Next steps' section, Azure PowerShell is listed before Azure CLI, ARM, Bicep, and Terraform, which may suggest a Windows-first or PowerShell-heavy bias. There are no explicit Linux-specific instructions or CLI examples in the main quickstart, and no mention of Linux-native tools or shell commands. The documentation does not provide command-line examples (e.g., Bash, Azure CLI) inline, which are commonly used on Linux systems.
Recommendations
- Provide Azure CLI (bash) examples directly in the quickstart steps, not just as a link in 'Next steps'.
- List Azure CLI before Azure PowerShell in the 'Next steps' to reflect cross-platform parity.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and clarify any platform-specific requirements.
- Include at least one example of installing the extension using Azure CLI or Bash script within the main instructions.
- If screenshots are shown, consider including CLI output or terminal screenshots in addition to portal UI.
Create Pull Request
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-mars-troubleshoot.md
...main/articles/backup/backup-azure-mars-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation for troubleshooting the Azure Backup (MARS) agent is heavily biased towards Windows environments. All examples, instructions, and troubleshooting steps are specific to Windows OS, tools, and patterns (e.g., MMC console, Internet Explorer, Task Scheduler, Registry Editor, vssadmin, PowerShell, Windows file paths, and Windows-specific error codes). There are no references to Linux environments, tools, or equivalent procedures, nor is it clarified that the MARS agent is Windows-only, which may confuse cross-platform users.
Recommendations
- Explicitly state early in the documentation that the MARS agent is only supported on Windows, if that is the case. If Linux support is planned or exists, provide equivalent troubleshooting steps for Linux.
- Where possible, mention alternatives for Linux users, such as Azure Backup for Linux VMs, and link to relevant documentation.
- Avoid assuming the use of Windows-only tools (e.g., Internet Explorer, Task Scheduler, Registry Editor) without clarifying OS requirements.
- If the documentation is intended for a cross-platform audience, provide parallel troubleshooting steps or notes for Linux (or clarify the scope).
- Add a section or callout for users seeking Linux backup solutions, directing them to appropriate Azure documentation.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily Windows-centric, with all installation, configuration, and operational instructions assuming a Windows Server environment. Only Windows operating systems are listed as supported platforms, and all examples, tools, and commands (such as PowerShell cmdlets and registry edits) are specific to Windows. There is no mention of Linux support, nor are there any examples or guidance for Linux environments.
Recommendations
- Clearly state at the beginning of the documentation whether Linux is supported or not. If not, explain the reasons and provide alternatives for Linux users.
- If Linux support is possible or planned, add equivalent Linux installation and configuration instructions, including supported distributions and prerequisites.
- Provide examples using Linux-native tools and commands (e.g., bash, systemd, Linux file paths) where applicable.
- If the product is Windows-only, consider linking to Azure-native backup solutions that support Linux workloads, and provide guidance for mixed-environment scenarios.
- Ensure that any references to PowerShell, Windows registry, or Windows-specific features are either accompanied by Linux equivalents or clearly marked as Windows-only.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively references Windows tools and workflows (Task Manager, Control Panel, Windows file paths) when troubleshooting Azure Backup monitoring issues. There are no examples or instructions for Linux environments, nor is there any mention of Linux equivalents or cross-platform considerations.
Recommendations
- Include troubleshooting steps for Linux-based Azure Backup agents, if supported.
- Provide Linux command-line equivalents for process and service management (e.g., using 'ps', 'systemctl', or 'service' commands).
- Show Linux file path examples alongside Windows paths.
- Clearly state if the instructions only apply to Windows, and link to Linux-specific documentation if available.
- Ensure parity in examples and guidance for both Windows and Linux users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-scdpm-troubleshooting.md
.../articles/backup/backup-azure-scdpm-troubleshooting.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references Windows tools, services, and patterns (e.g., 'net stop dpmra', NT AUTHORITY\SYSTEM, MARS agent, Data Protection Manager), with no mention of Linux equivalents or support. All troubleshooting steps and terminology are specific to the Windows ecosystem, and there are no examples or guidance for Linux environments.
Recommendations
- Clarify early in the documentation whether Data Protection Manager is Windows-only, or if there are Linux-supported scenarios.
- If Linux is supported, provide equivalent troubleshooting steps and commands for Linux environments (e.g., service management commands, agent installation, and log locations).
- Where Windows-specific tools or patterns are mentioned (e.g., 'net stop dpmra', NT AUTHORITY\SYSTEM), offer Linux alternatives or explicitly state if not applicable.
- Include examples and error resolutions for Linux-based workloads or agents, if supported.
- Ensure parity in documentation structure by presenting Linux and Windows solutions side-by-side where possible.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-move-recovery-services-vault.md
...es/backup/backup-azure-move-recovery-services-vault.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples for moving Recovery Services vaults, mentioning Windows update procedures before Linux, and omitting Linux-specific command-line examples. While the Azure CLI is mentioned, the PowerShell workflow is more thoroughly documented, and there is no parity in Linux shell or scripting guidance.
Recommendations
- Provide equivalent Bash or Linux shell examples alongside PowerShell for all command-line operations, especially for moving resources.
- Ensure that Azure CLI examples are as detailed and prominent as PowerShell examples, including explanations of parameters and expected output.
- When discussing VM prerequisites (such as updating certificates), present Linux instructions before or alongside Windows instructions, with explicit commands or links to common Linux distributions.
- Include references to cross-platform tools and avoid assuming the administrator is using a Windows environment.
- Review all procedural steps and ensure that Linux users are not required to infer their own workflows from Windows-centric guidance.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-recovery-services-vault-overview.md
...ackup/backup-azure-recovery-services-vault-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning Windows-centric tools (System Center DPM, Windows Server, Azure Backup Server) prominently and providing a 'Back up a Windows Server' next step, without equivalent Linux-specific examples or guidance. While Linux is mentioned as a supported workload, there are no explicit Linux backup scenarios, tools, or walkthroughs provided. The focus on Windows tools and the absence of Linux-specific examples or parity in next steps may make Linux users feel less supported.
Recommendations
- Add explicit Linux backup scenarios and walkthroughs, such as 'Back up a Linux Server' or 'Back up a Linux VM', in the 'Next steps' section.
- Mention Linux-compatible backup tools or agents where Windows tools (like MARS agent, DPM, Azure Backup Server) are referenced, or clarify their applicability to Linux.
- Provide links to Linux-specific documentation or guides alongside Windows examples.
- Ensure that examples and references to operating systems are balanced, mentioning Linux and Windows together where both are supported.
- Review the documentation for opportunities to add Linux command-line or scripting examples, not just Windows/PowerShell.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-restore-key-secret.md
...ain/articles/backup/backup-azure-restore-key-secret.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All examples use PowerShell cmdlets, Windows file paths (e.g., C:\), and Windows-centric tools and workflows. Linux is only mentioned in passing, with no Bash, Azure CLI, or Linux-native examples provided. The documentation assumes the user is operating in a Windows environment, even for Linux VM scenarios.
Recommendations
- Provide equivalent Azure CLI and Bash examples for all PowerShell commands, especially for Linux users.
- Use platform-agnostic file paths or provide both Windows (C:\) and Linux (/home/user/) path examples.
- Include explicit instructions for restoring keys and secrets from Linux or macOS environments, not just Windows.
- Mention and demonstrate cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell.
- Reorder sections or examples so that Linux and Windows are given equal prominence, or clarify when steps are identical across platforms.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-kubernetes-backup-arm.md
...ob/main/articles/backup/quick-kubernetes-backup-arm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI or Bash/Linux shell instructions. The prerequisites and deployment instructions focus on PowerShell, which is primarily associated with Windows environments, and do not mention or demonstrate how to perform the same steps on Linux or macOS systems. This may hinder accessibility for users on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI (az) examples for deploying the ARM template, suitable for Linux/macOS users.
- Explicitly mention that the deployment can be performed from any platform (Windows, Linux, macOS) and provide cross-platform instructions.
- Where PowerShell is referenced, also provide Bash or shell script alternatives.
- In the prerequisites, include installation instructions for Azure CLI and note its cross-platform compatibility.
- Ensure that all code snippets are available in both PowerShell and CLI formats, and consider presenting CLI examples first or side-by-side to avoid implicit Windows prioritization.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-restore-files-from-vm.md
.../articles/backup/backup-azure-restore-files-from-vm.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows-first bias in several areas: Windows terminology and tools (e.g., 'Download Executable', registry edits, Windows Explorer) are mentioned before their Linux equivalents, and Windows-specific troubleshooting steps are more detailed. PowerShell is referenced in the 'Next steps' section before the Azure CLI. Some sections (e.g., registry changes for large disks) are Windows-only, while Linux equivalents are less detailed or appear later. The documentation assumes familiarity with Windows patterns and tools, and Windows steps are often described first.
Recommendations
- Alternate the order of Windows and Linux instructions throughout the document, or present both in parallel where possible.
- Provide equally detailed troubleshooting steps for Linux as are given for Windows (e.g., registry edits vs. Linux config changes).
- In 'Next steps', list Azure CLI and Linux-native tools before or alongside PowerShell.
- Use neutral terminology (e.g., 'Download recovery script' instead of 'Download Executable') and clarify both OS options at each step.
- Where Windows tools (e.g., Windows Explorer, registry) are referenced, provide Linux equivalents (e.g., file managers, relevant config files) with equal prominence.
- Ensure that screenshots and examples are balanced between Windows and Linux environments.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-restore-system-state.md
...n/articles/backup/backup-azure-restore-system-state.md
High Priority
View Details →
Detected Bias Types
Windows Only
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is exclusively focused on restoring System State for Windows Server using Azure Backup. All instructions, screenshots, and command-line examples are specific to Windows tools (e.g., Microsoft Azure Backup snap-in, Windows Server Backup utility, wbadmin, Windows Recovery Environment). There are no references to Linux systems, tools, or equivalent processes, nor any mention of cross-platform applicability or limitations.
Recommendations
- Clearly state at the beginning that the procedure is only applicable to Windows Server, and provide a link or note about Linux/UNIX backup and restore options if available.
- If Azure Backup supports Linux system state or similar functionality, add equivalent sections and examples for Linux, including commands (e.g., using rsync, tar, or Azure CLI), and describe the restore process for Linux servers.
- If Linux is not supported for system state restore, explicitly mention this limitation to set user expectations.
- Where possible, use cross-platform Azure Backup tools (such as Azure CLI or portal-based workflows) in examples, or at least reference them.
- Consider providing a comparison table or FAQ about differences in backup/restore capabilities between Windows and Linux servers in Azure Backup.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-security-feature.md
.../main/articles/backup/backup-azure-security-feature.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation is heavily focused on Windows-centric backup solutions (MABS, DPM, MARS), with no mention of Linux backup agents, Linux-specific workflows, or examples. All tools, error messages, and recovery procedures are described for Windows environments, and PowerShell commands are referenced without Linux CLI or scripting equivalents. The documentation assumes the user is operating in a Windows environment and does not address Linux hybrid backup scenarios.
Recommendations
- Include information about Azure Backup support for Linux workloads, if available, and how security features apply to them.
- Provide parallel examples and procedures for Linux-based backup agents or scripts, including CLI commands and error handling.
- Mention Linux-compatible tools and workflows alongside Windows tools, rather than focusing exclusively on Windows solutions.
- If certain features are not available for Linux, explicitly state this and provide guidance or alternatives for Linux users.
- Add troubleshooting steps and error messages relevant to Linux environments.
- Ensure parity in documentation structure, so Linux users can follow similar steps and benefit from the same security features where supported.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell deployment instructions, referencing PowerShell as a prerequisite, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The deployment workflow and prerequisites are tailored to Windows users, with no guidance for Linux or macOS environments.
Recommendations
- Add Azure CLI deployment instructions alongside the PowerShell example, as Azure CLI is cross-platform and widely used on Linux and macOS.
- In the prerequisites section, mention both Azure PowerShell and Azure CLI as supported options, with installation links for each.
- Wherever PowerShell-specific instructions are given (e.g., right-click to paste), provide equivalent instructions for Bash or other common Linux shells.
- Ensure that all code snippets and deployment steps are presented in both PowerShell and CLI/Bash formats, or clearly indicate which environments are supported.
- Review the 'Next steps' section to ensure that CLI and PowerShell links are given equal prominence.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-security-feature-cloud.md
...articles/backup/backup-azure-security-feature-cloud.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing only PowerShell command-line examples for scripting and automation, with no equivalent examples for Linux shells (such as Bash or Azure CLI). The use of PowerShell as the sole scripting interface assumes a Windows environment or familiarity with Windows tooling. There is no mention of Linux-native tools or cross-platform command-line options, and the documentation does not provide guidance for Linux users who may prefer Bash or the Azure CLI.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and commonly used on Linux.
- Explicitly mention that PowerShell Core is available cross-platform, but also provide Bash/Azure CLI equivalents for Linux users.
- Include a 'Choose a client' tab for Azure CLI, similar to the existing tabs for PowerShell, REST API, and Portal.
- Review all command snippets and ensure Linux users are not required to use Windows-specific tools or patterns.
- Add notes or sections addressing any differences or prerequisites for Linux environments, such as authentication or module installation.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-sql-database.md
...blob/main/articles/backup/backup-azure-sql-database.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All examples, instructions, and tooling references are specific to Windows environments. There is no mention of Linux-based SQL Server VMs, nor are there any examples or instructions for Linux users. All account names, file paths, permissions, and automation scripts (PowerShell, SMB shares, NT SERVICE accounts) are Windows-specific. The documentation assumes the use of Windows authentication, Windows file system paths, and Windows-only tools such as SSMS and PowerShell, with no Linux alternatives or parity.
Recommendations
- Add explicit guidance and examples for SQL Server running on Linux-based Azure VMs, including differences in backup extension installation, service accounts, and file system paths.
- Provide Linux command-line equivalents (e.g., bash scripts, sqlcmd usage on Linux, chown/chmod for permissions) alongside PowerShell and SSMS instructions.
- Clarify which features or steps are Windows-only and provide alternative steps or note limitations for Linux users.
- Reference Linux authentication and account management patterns (e.g., systemd service accounts, sudoers) where appropriate.
- Include screenshots or terminal output relevant to Linux environments, not just Windows GUIs.
- Update links and quickstart guides to include both Windows and Linux SQL Server VM creation and management.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively describes 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 no mention of Linux or cross-platform alternatives. There are no Linux-specific instructions, examples, or parity notes, and the documentation implicitly assumes SQL Server is running on Windows.
Recommendations
- Explicitly state that MABS and DPM are Windows-only tools at the beginning of the documentation.
- Provide guidance or links for backing up SQL Server on Linux (if supported by Azure Backup or other Microsoft tools), or clarify that Linux-based SQL Server instances are not supported by this workflow.
- Include a comparison table or section outlining backup options for SQL Server on Linux, such as using Azure Backup agent, native SQL Server backup/restore commands, or third-party tools.
- If possible, add Linux-specific examples or alternative workflows for organizations running SQL Server on Linux.
- Mention any limitations or differences in backup support for SQL Server on Linux versus Windows.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-sql-restore-cli.md
...b/main/articles/backup/backup-azure-sql-restore-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on SQL Server (a Microsoft/Windows-centric database) running on Azure VMs, with all examples and terminology tailored to SQL Server instances (e.g., 'mssqlserver', 'master'). There are no examples or guidance for restoring other database types (such as MySQL, PostgreSQL, or even SQL Server on Linux VMs). The documentation assumes the use of SQL Server tools and patterns, and does not address Linux-specific considerations or provide parity for Linux-based SQL Server deployments.
Recommendations
- Include explicit examples and notes for restoring SQL Server databases running on Linux-based Azure VMs, highlighting any differences in process, file paths, or prerequisites.
- Clarify whether the documented CLI commands and workflows are applicable to SQL Server on Linux VMs, and if not, provide Linux-specific instructions or call out limitations.
- If Azure Backup supports other database engines (e.g., MySQL, PostgreSQL) on Linux VMs, add sections or links to equivalent documentation for those scenarios.
- When referencing file paths (e.g., '/home/sql/restoreasfiles'), clarify OS-specific conventions and provide both Windows and Linux path examples where relevant.
- Avoid assuming the use of Windows tools or patterns (such as 'master' database, 'mssqlserver' instance names) without noting Linux differences or alternatives.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-system-state-troubleshoot.md
...icles/backup/backup-azure-system-state-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically on-premises Windows servers, and provides only Windows-specific tools, commands (PowerShell, wbadmin), and troubleshooting steps. There are no Linux equivalents or cross-platform considerations, and all examples and screenshots are Windows-centric.
Recommendations
- Clearly state in the introduction that System State Backup is only supported on Windows, if that is the case, and provide links to equivalent Linux backup solutions if relevant.
- If Azure Backup or MARS Agent supports Linux in other scenarios, add a section or links to Linux-specific documentation for parity.
- Where possible, provide parallel troubleshooting steps or references for Linux environments, or explicitly mention that the described procedures are not applicable to Linux.
- Avoid assuming the use of Windows-only tools (like PowerShell, Server Manager) without noting alternatives or the lack thereof for Linux.
- If the product is Windows-only, clarify this early and suggest alternative backup strategies for Linux users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-system-state.md
...blob/main/articles/backup/backup-azure-system-state.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is exclusively focused on backing up Windows Server system state using Azure Backup. All instructions, screenshots, and tool references are specific to Windows (e.g., MARS Agent, .exe installers, Windows Server versions, Windows-specific commands like SFC). There are no Linux equivalents, examples, or even mentions of Linux support or alternatives. The workflow, tools, and terminology are all Windows-centric, and Linux users are not addressed at all.
Recommendations
- Clearly state in the introduction that this guide is Windows-only, and provide a link to equivalent Linux backup documentation if available.
- Add a section or cross-reference for Linux system backup to Azure, if supported, including relevant tools (e.g., Azure CLI, azcopy, rsync, or third-party agents).
- If Azure Backup supports Linux system state or file backup, provide parallel instructions and screenshots for Linux environments.
- Avoid using only Windows-specific terminology and tools (such as MARS Agent, .exe installers, SFC) without mentioning if or how Linux users can achieve similar results.
- If Linux is not supported for system state backup, explicitly mention this limitation to set user expectations.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-troubleshoot-slow-backup-performance-issue.md
...ackup-azure-troubleshoot-slow-backup-performance-issue.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation is heavily Windows-centric, referencing only Windows tools (such as Performance Monitor), Windows file paths, and Windows-specific troubleshooting steps. There are no Linux examples, tools, or guidance provided, and the language assumes the user is operating in a Windows environment throughout.
Recommendations
- Add equivalent troubleshooting steps and examples for Linux systems, including references to common Linux backup agents or methods supported by Azure Backup.
- Include Linux performance monitoring tools (such as iostat, vmstat, top, sar, or dstat) and provide example commands for diagnosing bottlenecks.
- Mention Linux file paths and log locations where relevant, or clarify if the Azure Backup agent is not supported on Linux.
- If the Azure Backup agent is Windows-only, explicitly state this at the start of the documentation and provide links or references to Linux backup solutions supported by Azure.
- Ensure that troubleshooting advice and recommendations are presented for both Windows and Linux environments, or clarify platform limitations.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md
...up-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows troubleshooting steps and tools (e.g., services.msc, Control Panel, Event Viewer, regsvr32.exe, Visual C++ Redistributable) are described in detail, often with screenshots, while Linux equivalents are less detailed or omitted. Windows is frequently mentioned first, and PowerShell is referenced for operations like setting static IPs or cancelling backup jobs, with no equivalent Linux CLI or shell commands provided. Some troubleshooting steps and error resolutions are Windows-specific, with Linux guidance being more generic or less actionable.
Recommendations
- Provide equivalent Linux commands and tools for all troubleshooting steps (e.g., systemctl/service for agent status, journalctl/log file locations for logs, dpkg/rpm for package management).
- Include Linux CLI examples (e.g., az CLI, shell commands) wherever PowerShell or Windows GUI steps are given.
- Add screenshots or terminal output examples for Linux where Windows screenshots are used.
- Ensure Linux troubleshooting steps are as detailed and actionable as Windows steps, including specific commands for checking and restarting services, managing dependencies, and handling agent/extension issues.
- When listing steps or options, alternate the order or present Windows and Linux guidance in parallel rather than always leading with Windows.
- Reference Linux-specific documentation and best practices alongside Windows links.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vm-file-recovery-troubleshoot.md
...s/backup/backup-azure-vm-file-recovery-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by frequently presenting Windows troubleshooting steps and tools (such as File Explorer, Server Manager, Disk Management, ISCSI initiator Properties) before or in more detail than their Linux equivalents. Windows-specific error messages and GUI workflows are described with screenshots, while Linux sections often refer users to external links or provide minimal command-line guidance. Some scenarios (e.g., deduplication, disk management) are only covered for Windows, with no Linux equivalents or detailed steps.
Recommendations
- Provide Linux troubleshooting steps and examples with equal detail and prominence as Windows, including command-line workflows for common tasks (e.g., mounting/unmounting disks, checking disk status, handling deduplication).
- Include Linux-specific error messages and their resolutions directly in the documentation, not just as links.
- Add screenshots or terminal output examples for Linux steps, similar to the Windows GUI screenshots.
- When listing steps for both OSes, alternate the order or present them in parallel sections to avoid always placing Windows first.
- For every Windows tool or feature mentioned (e.g., Disk Management, deduplication), mention the Linux equivalent (e.g., lsblk, mount, lvm, mdadm, file system deduplication tools) and provide usage instructions.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-agentless-multi-disk-crash-consistent-overview.md
...ure-vms-agentless-multi-disk-crash-consistent-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation references Windows-specific tools (Volume Shadow Copy Service - VSS) before mentioning the Linux equivalent (fsfreeze), and does not provide detailed Linux examples or guidance. Windows terminology and links (such as to the VM Agent and snapshot extension for Windows) are provided, but there are no equivalent Linux-focused links or instructions. Linux is only mentioned in passing, and Linux-specific backup considerations (such as pre/post scripts) are not elaborated.
Recommendations
- Provide equal detail for both Windows and Linux backup mechanisms, including links to Linux VM Agent and snapshot extension documentation.
- List Linux tools (e.g., fsfreeze) before or alongside Windows tools (VSS) to avoid Windows-first ordering.
- Include Linux-specific examples or scenarios, such as how crash-consistent backups interact with common Linux filesystems and applications.
- Expand on Linux pre/post script usage and provide guidance or references for Linux users.
- Ensure all references to extensions or agents include both Windows and Linux documentation links.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-all-files-volume-mars.md
.../main/articles/backup/restore-all-files-volume-mars.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows environments. All instructions, screenshots, and terminology are specific to the Microsoft Azure Recovery Services (MARS) Agent, which is a Windows-only tool. There are no references to Linux systems, no Linux command-line or GUI examples, and no mention of restoring files on non-Windows platforms. The documentation assumes the use of Windows features (snap-ins, desktop apps, ACLs in NTFS format) and does not provide parity for Linux users.
Recommendations
- Clearly state at the beginning of the documentation that the MARS Agent is only supported on Windows, if that is the case.
- If Linux support is available via other Azure backup solutions (such as Azure Backup for Linux VMs or Azure CLI), provide links or references to those alternatives.
- If Linux support is planned, add equivalent Linux instructions, including command-line examples and screenshots for restoring files on Linux systems.
- Avoid using Windows-specific terminology (such as 'snap-in', 'desktop app', 'NTFS ACLs') without clarifying platform limitations.
- Add a comparison table or section outlining supported platforms and tools for both Windows and Linux, helping users quickly find the relevant guidance.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-encryption.md
...ob/main/articles/backup/backup-azure-vms-encryption.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation, while mentioning both Windows and Linux VMs, demonstrates a Windows bias by providing PowerShell commands as the only example for identifying a VM's associated Key Vault, referencing BitLocker (Windows) before dm-crypt (Linux) in the ADE section, and omitting equivalent Linux/CLI commands or examples. There are no explicit Linux command-line examples or references to Linux-native tools, and the only command-line example is Windows PowerShell.
Recommendations
- Provide equivalent Azure CLI or Bash examples alongside PowerShell commands, especially for tasks like identifying the Key Vault associated with a VM.
- When describing ADE, mention Linux (dm-crypt) and Windows (BitLocker) in parallel, and provide links to both Windows and Linux disk encryption documentation equally.
- Ensure that all procedural steps that reference command-line actions include both Windows (PowerShell) and Linux (CLI/Bash) variants.
- Add Linux-specific troubleshooting links and examples where relevant.
- Review the order of OS mentions to avoid always listing Windows first, and strive for parity in example depth and detail.