Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 701-725 of 2185 flagged pages
Azure Docs
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All instructions, prerequisites, and tooling references assume the use of Windows (e.g., Windows PowerShell, .NET Framework, .exe installers). There are no examples, instructions, or even mentions of Linux or cross-platform scenarios. The documentation does not address how to prepare DPM or Azure Backup in a Linux environment, nor does it mention Linux-compatible tools or alternatives.
Recommendations
- Explicitly state that DPM is a Windows-only product, if that is the case, or clarify Linux support status.
- If Linux support exists (e.g., for Azure Backup agent or similar workloads), provide parallel instructions and examples for Linux systems, including command-line steps (bash, shell scripts), package installation (deb/rpm), and configuration.
- Mention Linux prerequisites (e.g., required libraries, supported distributions) alongside Windows prerequisites.
- Reference Linux-native tools or equivalents where Windows tools (PowerShell, .NET Framework, .exe installers) are mentioned.
- If Linux is not supported, add a clear note at the beginning to inform users and suggest alternative backup solutions for Linux workloads.
Create Pull Request
Azure Docs
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the only command-line automation example, without mentioning or providing equivalent instructions for Linux users (e.g., Azure CLI or Bash). The documentation also refers to Windows-centric tools and patterns first, with no explicit Linux parity or examples.
Recommendations
- Add equivalent Azure CLI (cross-platform) or Bash examples alongside PowerShell instructions for configuring permissions and automation.
- Explicitly mention that steps can be performed from both Windows and Linux environments, and provide links to both PowerShell and Azure CLI documentation.
- Where automation or scripting is referenced, ensure both Windows (PowerShell) and Linux (Bash/Azure CLI) workflows are described.
- Review linked pages (such as 'enable-protection' and 'create-a-vm-from-restored-disks') to ensure Linux parity in examples and instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-exchange-mabs.md
...ob/main//articles/backup/backup-azure-exchange-mabs.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows environments, specifically Microsoft Exchange Server and Azure Backup Server (MABS), both of which are Windows-only products. All instructions and examples assume a Windows operating system, referencing Windows file paths (e.g., C:\Program Files), Windows-specific tools (e.g., Eseutil.exe), and GUI navigation in the MABS Administrator Console. There are no Linux equivalents, examples, or mentions of cross-platform considerations.
Recommendations
- Explicitly state that MABS and Exchange Server are Windows-only products, and clarify if Linux support is not available.
- If any Linux-based backup or recovery scenarios are possible (e.g., backing up Linux workloads with Azure Backup), provide links or references to those workflows.
- Where possible, mention alternative Azure Backup solutions that support Linux servers, and link to their documentation.
- If the documentation is intended to be cross-platform, include Linux-specific instructions, tools, and command-line examples.
- Clarify in the prerequisites or introduction that the instructions are specific to Windows environments to set user expectations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-delete-vault.md
...lob/main//articles/backup/backup-azure-delete-vault.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. PowerShell is the primary automation method described, with detailed steps, scripts, and prerequisites (including explicit instructions to install PowerShell 7). The ARMClient tool is installed via Chocolatey, a Windows package manager, and all management console instructions (MARS, MABS, DPM) are Windows-only. There are no Bash, Linux, or cross-platform CLI examples for on-premises or automation scenarios. The Azure CLI section is limited and notes that it only works for VM backups, with no parity for other scenarios. Linux users are left without equivalent guidance for automation or management.
Recommendations
- Provide Bash and cross-platform Azure CLI examples for all major operations, not just VM backups.
- Document how to use PowerShell Core on Linux/macOS, or provide equivalent scripts in Bash or Python.
- For ARMClient, suggest cross-platform installation methods (e.g., via pip, npm, or direct download) and clarify usage on Linux/macOS.
- Include guidance for managing on-premises backups from non-Windows environments, or clarify limitations.
- Ensure that automation and scripting examples are not limited to Windows tools; offer alternatives or note cross-platform compatibility.
- Where Windows-specific tools are required (e.g., MARS, DPM, MABS), clearly state this and suggest any available alternatives for Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-mabs-troubleshoot.md
...ain//articles/backup/backup-azure-mabs-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation for Azure Backup Server troubleshooting is heavily Windows-centric. All file paths, registry keys, and tool references are Windows-specific (e.g., C:\ paths, Windows registry, Windows services, Windows Server Backup, DPM, MARS agent). Troubleshooting steps and examples assume a Windows environment, with no mention of Linux equivalents or cross-platform considerations. There are no Linux commands, file paths, or references to Linux backup agents or tools. This creates a strong Windows bias and excludes users running Linux workloads or seeking cross-platform guidance.
Recommendations
- Include Linux-specific troubleshooting steps and examples where applicable, such as commands for checking services, file paths, and permissions on Linux systems.
- Provide equivalent Linux commands (e.g., systemctl, journalctl, grep) alongside Windows commands (e.g., net start, reg query).
- Reference Linux backup agents or supported Linux workloads if Azure Backup Server supports them, and clarify any platform limitations.
- Add notes or sections that address common issues and solutions for Linux-based protected servers, including antivirus configuration, agent installation, and backup/restore operations.
- Where registry edits are mentioned, provide guidance for Linux configuration files or settings if relevant.
- Ensure parity in documentation structure and troubleshooting coverage for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-monitor-troubleshoot.md
...//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 demonstrates Windows bias by exclusively referencing Windows tools (Task Manager, Control Panel), Windows service/process names, and Windows file paths. There are no troubleshooting steps, examples, or file paths provided for Linux environments, nor is there any mention of Linux equivalents or support.
Recommendations
- Include troubleshooting steps for Linux-based Azure Backup agents, if supported.
- Provide Linux equivalents for process management (e.g., using 'ps', 'systemctl', or 'service' commands) and log file locations.
- Add examples of Linux file paths and commands alongside Windows examples.
- Explicitly state if the Azure Backup agent or specific troubleshooting steps are only applicable to Windows, or clarify Linux support status.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-mars-troubleshoot.md
...ain//articles/backup/backup-azure-mars-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. All troubleshooting steps, examples, and tool references are specific to Windows (e.g., MMC console, Internet Explorer, Task Scheduler, Registry Editor, vssadmin, PowerShell). There are no Linux equivalents or mentions, and the MARS agent is presented as a Windows-only solution. The documentation assumes the user is operating on Windows, with no guidance for Linux users or cross-platform scenarios.
Recommendations
- Clearly state at the beginning if the MARS agent is only supported on Windows. If so, explain alternatives for Linux users (such as Azure Backup for Linux or Azure VM backup).
- If any cross-platform support exists, provide equivalent troubleshooting steps and examples for Linux environments.
- Avoid referencing Windows-specific tools (e.g., Internet Explorer, Task Scheduler, Registry Editor) without mentioning if there are Linux alternatives or if these steps are not applicable.
- For PowerShell-heavy instructions, offer Bash/CLI equivalents if Linux is supported.
- Add a section or note for Linux users, clarifying supported agents and linking to relevant documentation for Linux backup and troubleshooting.
Azure Docs
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-based backup solutions (MABS, DPM, MARS), with all examples, tools, and workflows tailored to Windows environments. There is no mention of Linux backup agents, Linux-based recovery, or parity in features for non-Windows workloads. Command-line examples (e.g., Remove-DPMChildDatasource, Remove-OBPolicy) are PowerShell/Windows-specific, and all product/version requirements and troubleshooting steps refer exclusively to Windows tools.
Recommendations
- Include information about Linux support in Azure Backup, if available, and clarify feature parity or gaps.
- Provide Linux-specific examples and workflows (e.g., using Azure CLI, shell scripts, or Linux agents) alongside or before Windows examples.
- Mention and link to Linux backup agent documentation where relevant.
- If features are Windows-only, explicitly state this early in the article and provide guidance or alternatives for Linux users.
- Balance command-line examples by including both PowerShell (Windows) and Bash/Azure CLI (Linux) equivalents where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-sql-mabs.md
...cs/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 the use of Microsoft Azure Backup Server (MABS) and Data Protection Manager (DPM), which are Windows-only tools, for backing up SQL Server databases. All examples, screenshots, and instructions are based on the Windows GUI and Windows-specific account names (e.g., NTAuthority\System). There is no mention of Linux-based SQL Server deployments, nor are there any examples or guidance for Linux environments, even though SQL Server is supported on Linux.
Recommendations
- Acknowledge in the introduction that MABS and DPM are Windows-only solutions, and clarify their applicability to Windows-based SQL Server deployments.
- Provide a section or links for Linux users, outlining supported backup strategies for SQL Server on Linux (e.g., using Azure Backup with Linux VMs, native SQL Server backup/restore commands, or third-party tools).
- Include examples or references for backing up SQL Server on Linux, such as using bash scripts, cron jobs, or integration with Azure Backup via Linux agents.
- Mention any limitations or alternative recommendations for organizations running SQL Server on Linux, to ensure parity and avoid confusion.
- Ensure that future documentation on SQL Server backup in Azure covers both Windows and Linux scenarios, or clearly scopes the content to Windows if Linux is not supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/how-to-use-apis.md
...s/blob/main//articles/digital-twins/how-to-use-apis.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Visual Studio, a Windows-centric tool, and does not mention or provide examples for equivalent workflows on Linux or macOS. All setup and usage instructions are tailored to Visual Studio and its .http file support, with no mention of cross-platform alternatives such as VS Code with REST Client, curl, Postman, or other tools commonly used on Linux. The prerequisites and step-by-step instructions assume a Windows environment, and there are no Linux-specific notes or parity guidance.
Recommendations
- Add a section describing how to perform the same API calls using cross-platform tools such as VS Code with the REST Client extension, curl, or Postman.
- Include Linux/macOS-specific setup instructions and screenshots where applicable.
- Clearly indicate that Visual Studio is Windows-only and suggest alternatives for non-Windows users.
- Reorganize the documentation to present cross-platform options before or alongside Windows-specific instructions.
- Provide sample .http files and equivalent curl/Postman requests for Linux users.
Azure Docs
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All examples, screenshots, and instructions are specific to the Microsoft Azure Recovery Services (MARS) Agent, which is a Windows-only tool. There are no references to Linux systems, Linux backup agents, or cross-platform alternatives. The documentation assumes the use of Windows GUIs, Windows file paths, and Windows-specific tools (e.g., MARS console, DPM/MABS, %ProgramFiles% paths, .exe binaries). No Linux commands, tools, or equivalent workflows are mentioned or linked.
Recommendations
- Clearly state at the beginning of the documentation that MARS Agent is Windows-only, and provide links to equivalent Linux backup solutions (such as Azure Backup for Linux or Azure VM Backup).
- Add a comparison table or section outlining backup options for both Windows and Linux, with links to relevant documentation for Linux users.
- Where possible, provide parity in documentation by including references or links to Linux backup workflows, even if direct feature parity is not available.
- Ensure that navigation paths, commands, and screenshots are labeled as Windows-specific, and avoid implying that the instructions are cross-platform.
- If the product is truly Windows-only, make this explicit in the prerequisites and summary, and direct Linux users to appropriate alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-sql-database.md
...lob/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 is heavily biased toward Windows environments. All examples, instructions, and tooling references (such as SSMS, NT SERVICE accounts, and PowerShell scripts) are specific to Windows. There is no mention of Linux-based SQL Server VMs, nor are there any Linux command-line or configuration examples. The documentation assumes the use of Windows authentication, Windows file paths, and Windows-specific service accounts, with no guidance for equivalent Linux scenarios.
Recommendations
- Add explicit support and examples for SQL Server running on Linux-based Azure VMs, including any differences in the Azure Backup extension and service account configuration.
- Provide Linux command-line examples (e.g., using sqlcmd, bash scripts) for granting permissions and configuring backups.
- Clarify whether the AzureBackupWindowsWorkload extension or an equivalent is available for Linux, and if not, state the limitation up front.
- Include Linux file path conventions and permission-setting instructions (e.g., using chmod/chown) for configuring local backup folders.
- Mention any differences in authentication (e.g., use of local or domain accounts vs. service accounts) for Linux SQL Server.
- If the solution is Windows-only, clearly state this at the beginning of the documentation to set expectations.
Azure Docs
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 referencing Windows-specific tools (System Center DPM, Windows Server, Azure Backup Server) and providing a 'Back up a Windows Server' next step, while not mentioning or linking to Linux-specific backup tools or examples. Although Linux is briefly mentioned as a supported VM type, there are no Linux-focused instructions or parity in examples.
Recommendations
- Include explicit Linux backup scenarios and examples, such as 'Back up a Linux Server' in the Next Steps section.
- Mention and link to Linux-specific documentation or tools (e.g., Azure Backup for Linux VMs, or Linux agent documentation) alongside Windows tools.
- Ensure that when listing supported workloads or tools, Linux equivalents are mentioned with equal prominence and detail.
- Provide example commands or workflows for both Windows (PowerShell, MARS agent) and Linux (CLI, shell scripts) where relevant.
- Review and update cross-links to ensure Linux users have clear guidance for their environments.
Azure Docs
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 exhibits a moderate Windows bias. Windows instructions and tools are often presented first, with more visual emphasis (screenshots, registry edits, File Explorer references). Windows-specific troubleshooting (registry changes) is detailed, while Linux troubleshooting is present but less visually emphasized. The 'Next steps' section highlights PowerShell before Azure CLI. Windows tools and patterns (e.g., File Explorer, registry editor) are mentioned explicitly, while Linux equivalents are described but not as prominently. Both platforms are covered, but Windows is prioritized in ordering and detail.
Recommendations
- Alternate the order of Windows and Linux instructions in each section, or present them in parallel to avoid 'Windows first' bias.
- Provide equal visual emphasis for Linux steps (e.g., screenshots of Linux file managers, terminal outputs).
- Include Linux-specific troubleshooting and configuration details with the same depth as Windows (e.g., highlight Linux config file changes visually).
- In the 'Next steps' section, mention Azure CLI and Linux automation options before or alongside PowerShell.
- Where Windows tools (e.g., File Explorer, registry editor) are referenced, provide explicit Linux equivalents (e.g., Nautilus, GNOME Disks, or command-line alternatives) and screenshots.
- Ensure that all advanced scenarios (e.g., large disks, LVM/RAID) are equally detailed for both OSes.
Azure Docs
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 page demonstrates a Windows bias by providing detailed PowerShell examples and cmdlets for all command-line operations, with no mention of Linux-native tools, Bash, or Azure CLI equivalents. The PowerShell tab is presented as the only scriptable command-line option, and all code snippets use PowerShell syntax. There are no examples or guidance for users on Linux or macOS platforms, nor are cross-platform tools like Azure CLI referenced. This may hinder Linux users or those preferring non-Windows environments from following the documentation easily.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell Core is available cross-platform, if PowerShell must be used, and provide installation instructions for Linux/macOS.
- Reorder or parallelize example tabs so that Azure CLI and REST API are presented equally with PowerShell, not after it.
- Include notes or links for Linux/macOS users on how to perform the same tasks in their environments.
- Audit all screenshots and UI references to ensure they are not Windows-specific, or provide Linux/macOS equivalents where relevant.
Azure Docs
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 is heavily oriented toward Windows environments, referencing Windows-specific tools (such as 'net stop dpmra' and 'net start dpmra'), and assumes the use of Data Protection Manager (DPM), which is a Windows-only product. There are no examples or troubleshooting steps for Linux systems, nor are Linux equivalents or cross-platform considerations mentioned. The troubleshooting steps and terminology (e.g., NT AUTHORITY\SYSTEM, command prompt) are specific to Windows, with no mention of PowerShell or Linux shell commands, but the overall guidance is Windows-centric.
Recommendations
- Explicitly state that Data Protection Manager is a Windows-only product at the beginning of the documentation.
- If any components or agents have Linux support (such as Azure Backup agent), provide equivalent troubleshooting steps and commands for Linux systems.
- Where Windows-specific commands are given (e.g., 'net stop dpmra'), note that these are for Windows, and provide Linux equivalents if applicable.
- For authentication and permissions examples (e.g., NT AUTHORITY\SYSTEM), clarify the context and provide Linux analogs if relevant.
- Review all troubleshooting steps to ensure that, where cross-platform support exists, both Windows and Linux procedures are documented equally and in parallel.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-mabs-sharepoint-azure-stack.md
.../articles/backup/backup-mabs-sharepoint-azure-stack.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. All instructions, tools, and examples assume a Windows Server/SharePoint deployment. Only Windows command-line tools (CMD, Registry Editor), Windows file paths, and Windows-specific services (VSS Writer, DCOM, NT AUTHORITY\SYSTEM) are referenced. There are no Linux equivalents, nor is there any mention of Linux-based SharePoint or Azure Stack deployments. The documentation presumes the use of Windows administrative patterns and does not address cross-platform scenarios.
Recommendations
- Explicitly state that MABS and SharePoint farm protection are only supported on Windows, if that is the case. If Linux is not supported, clarify this early in the prerequisites.
- If any components (such as Azure Backup Server or Azure Stack) support Linux workloads, provide parallel instructions or at least mention the differences and limitations.
- Where possible, include Linux equivalents or alternatives for backup and monitoring (e.g., using Linux-based backup agents, or scripting with Bash instead of CMD/PowerShell).
- Avoid assuming the use of Windows-only tools (such as Registry Editor, CMD, or Windows file paths) without noting platform limitations.
- If the product is Windows-only, add a clear note at the top of the documentation to prevent confusion for Linux administrators.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-restore-system-state.md
...//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, tools (MARS agent, Windows Server Backup, wbadmin), screenshots, and command-line examples are specific to Windows environments. There are no references to Linux, Linux-based tools, or cross-platform recovery scenarios. The documentation assumes the user is operating in a Windows Server environment from start to finish.
Recommendations
- If Azure Backup supports Linux system state or equivalent (e.g., bare-metal or configuration backup), add a parallel section for Linux servers, including supported distributions, prerequisites, and step-by-step restore instructions.
- Include Linux-specific tools and commands (such as rsync, tar, dd, or Azure CLI for Linux) where applicable, and provide examples for restoring system configuration or state on Linux.
- If Linux is not supported for system state backup/restore, explicitly state this at the beginning of the article to set user expectations.
- For cross-platform parity, consider linking to Linux backup/restore documentation or best practices for disaster recovery in Linux environments using Azure services.
- Ensure that future documentation for backup and restore scenarios covers both Windows and Linux platforms where possible, or clearly delineates platform-specific guidance.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-sql-restore-cli.md
.../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 exclusively focusing on SQL Server (a Microsoft/Windows-centric database) and providing examples only for restoring SQL Server databases on Azure VMs. There is no mention of Linux-based SQL Server VMs, nor are there examples or guidance for restoring databases on Linux VMs. All resource and instance names (e.g., mssqlserver, testSQLVM) imply Windows environments. No Linux-specific tools, patterns, or considerations are discussed, and the documentation does not clarify whether the steps apply to Linux-based SQL Server installations or other database engines.
Recommendations
- Explicitly state whether the documented procedures apply to both Windows and Linux-based SQL Server VMs, or clarify any differences.
- Provide examples and command lines for restoring SQL Server databases on Linux VMs, including any Linux-specific prerequisites or considerations (such as file paths, permissions, or service management).
- If supported, include guidance for restoring other database engines (e.g., PostgreSQL, MySQL) on Linux VMs using Azure Backup, or clearly state the scope is limited to SQL Server.
- Use neutral resource and instance names (not just 'mssqlserver' or 'testSQLVM') or alternate between Windows and Linux examples.
- Mention any differences in file paths, service names, or post-restore steps that may be required on Linux versus Windows.
- Add troubleshooting tips or links for common Linux-specific restore issues (e.g., SELinux, file permissions, systemd service restarts).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-overview.md
...ure-docs/blob/main//articles/backup/backup-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Microsoft-centric backup agents (MARS, DPM, MABS) that are Windows-only, and by listing Windows backup scenarios before Linux equivalents. There is a lack of explicit Linux tooling or example parity, especially for on-premises backup scenarios, and no Linux-specific instructions or tools are mentioned for non-Azure VM backups.
Recommendations
- Include explicit mention of Linux-compatible backup agents or third-party solutions for on-premises Linux systems.
- Provide Linux-specific examples or documentation links alongside Windows examples, especially for on-premises backup scenarios.
- Avoid listing Windows tools and scenarios first; instead, present Windows and Linux options together or alternate their order.
- Clarify support for Linux workloads in each backup scenario, including any limitations or required tools.
- If Linux support is not available for certain features (e.g., MARS agent), state this clearly and suggest alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-system-state.md
...lob/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 Windows Server, with all instructions, screenshots, and tools (such as the MARS agent) tailored for Windows environments. There are no references to Linux systems, no Linux command-line or tool equivalents, and no cross-platform guidance. The workflow, agent, and backup targets are all Windows-specific, and even the prerequisites and notes reinforce a Windows-only context.
Recommendations
- If Azure Backup supports Linux system state or equivalent backups, add a parallel section or a separate article for Linux, including step-by-step instructions, screenshots, and supported tools.
- Where possible, mention cross-platform alternatives or clarify that the described method is Windows-only, and link to Linux backup documentation if available.
- Include a comparison table or FAQ addressing differences in backup support and tooling between Windows and Linux.
- If Linux is not supported for system state backup with Azure Backup, explicitly state this early in the article to set expectations for cross-platform users.
Azure Docs
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 exhibits a moderate Windows bias. Windows-specific tools (services.msc, Control Panel, Event Viewer, regsvr32.exe, .NET, Visual C++ Redistributable) are mentioned in detail, often with screenshots and step-by-step instructions, while equivalent Linux troubleshooting steps are less detailed and lack visual aids. PowerShell is referenced as a primary automation method, and Windows procedures are often listed before Linux ones. Some troubleshooting sections (e.g., COM+, VSS, antivirus exclusions) are Windows-only, with no Linux parallels or guidance.
Recommendations
- Provide equivalent Linux commands and troubleshooting steps wherever Windows tools (e.g., services.msc, Event Viewer, regsvr32.exe) are referenced. For example, show how to check and restart the Azure agent service on Linux using systemctl, and how to view relevant logs.
- Include Linux-specific examples for antivirus exclusions, disk and extension troubleshooting, and backup job management.
- Add screenshots or terminal output examples for Linux steps, similar to the Windows screenshots provided.
- When listing steps or causes, alternate the order or present Windows and Linux instructions in parallel to avoid 'Windows first' bias.
- Reference Linux automation tools (e.g., Bash scripts, Azure CLI) alongside PowerShell, and provide CLI examples for both platforms.
- For sections that are Windows-only (e.g., COM+, VSS), explicitly state that these are not applicable to Linux, and provide Linux-specific troubleshooting for comparable issues where possible.
Azure Docs
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, and troubleshooting steps (e.g., PowerShell, Server Manager, Windows Server Backup, wbadmin). There are no Linux equivalents or cross-platform considerations, and all examples and instructions are tailored exclusively to Windows systems.
Recommendations
- Clearly state in the introduction that System State Backup is a Windows-only feature, and provide links to equivalent backup and troubleshooting documentation for Linux systems if available.
- If the Azure Backup solution supports Linux in other contexts, add a section or cross-reference to Linux backup documentation and troubleshooting guides.
- Where possible, provide parity in troubleshooting steps for Linux-based backup agents or clarify the scope is intentionally limited to Windows.
- If Linux is not supported for System State Backup, explicitly mention this limitation early in the document to set user expectations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-vm-migrate-enhanced-policy.md
...cles/backup/backup-azure-vm-migrate-enhanced-policy.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and CLI versions for backup operations, but does not provide explicit Linux or cross-platform command examples. The only non-portal automation guidance is a link to the Azure CLI, but there are no direct command-line examples or Linux-specific notes. The documentation also refers to PowerShell before CLI in the note, and does not clarify that Azure CLI is cross-platform or provide Bash/Linux shell usage patterns.
Recommendations
- Provide explicit Azure CLI command examples for migration steps, including sample commands for both Windows (CMD/PowerShell) and Linux (Bash).
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Avoid listing PowerShell before CLI in notes or instructions; instead, present CLI first or in parallel, as it is cross-platform.
- Include screenshots or terminal output from Linux environments where relevant.
- Add a section or callout specifically for Linux users, highlighting any OS-specific considerations or confirming there are none.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-during-vm-creation.md
...lob/main//articles/backup/backup-during-vm-creation.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows VM deployment templates, referencing PowerShell for automation, and lacking Linux-specific examples or parity in automation instructions. While both Windows and Linux are briefly mentioned for manual VM creation, automation and template guidance focus exclusively on Windows.
Recommendations
- Provide equivalent deployment templates for Linux VMs with backup enabled, and link to them alongside the Windows template.
- Include automation instructions for configuring Azure Backup resource groups using Azure CLI or ARM templates, not just PowerShell.
- Ensure that all steps and screenshots that apply to both Windows and Linux are clearly labeled as such, and provide Linux-specific notes where behavior or options differ.
- When referencing automation or scripting, always present both Windows (PowerShell) and cross-platform (Azure CLI, Bicep, ARM) options.
- In the 'Deploy a protected VM using a Resource Manager template' section, add a link to a Linux VM template with backup enabled.