Backup
755
Total Pages
562
Linux-Friendly Pages
193
Pages with Bias
25.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
520 issues found
Showing 176-200 of 520 flagged pages
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 page demonstrates a Windows bias in several ways: Windows troubleshooting steps and tools (such as File Explorer, Server Manager, Disk Management, ISCSI initiator Properties) are described in detail with screenshots and step-by-step instructions, while Linux troubleshooting is often referenced via external links or summarized briefly. Windows scenarios are frequently presented before Linux equivalents, and some error resolutions provide only Windows-specific guidance or examples. Linux instructions are less detailed, sometimes missing direct command-line examples or GUI walkthroughs.
Recommendations
- Provide equally detailed, step-by-step instructions for Linux scenarios, including relevant commands (e.g., mount, fdisk, lsblk, iscsiadm) and screenshots where applicable.
- Include Linux troubleshooting examples directly in the documentation, rather than referring to external links.
- Present Windows and Linux guidance in parallel, ensuring neither is consistently prioritized or described first.
- List Linux tools and patterns (e.g., GNOME Disks, CLI utilities) alongside Windows tools when discussing disk management and recovery.
- Add Linux-specific error codes and their resolutions where only Windows errors are currently described.
Create Pull Request
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 page exhibits mild Windows bias by mentioning Windows-specific tools (Volume Shadow Copy Service - VSS) before Linux equivalents (fsfreeze) when describing backup consistency mechanisms. References to VM Agent and snapshot extension link only to Windows documentation, with no Linux-specific links or examples. There are no Linux command-line or tool examples, and Linux backup patterns (such as pre/post scripts) are only mentioned as a reason not to use crash-consistent backups, without further guidance.
Recommendations
- Provide equal prominence to Linux tools (e.g., fsfreeze) alongside Windows tools (VSS), including links to relevant Linux documentation.
- Include examples or references for both Windows and Linux VM Agent and snapshot extension documentation.
- Add Linux-specific backup scenarios, including guidance on using pre/post scripts and how crash-consistent backups interact with common Linux workloads.
- Ensure that any tool or pattern mentioned for Windows is matched with its Linux equivalent, and vice versa, to maintain parity.
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 page shows evidence of Windows bias. PowerShell is the only command-line example provided for identifying a VM's associated key vault, with no equivalent Linux/CLI example. In the section on ADE, Windows tools (BitLocker) are mentioned before Linux equivalents (dm-crypt). There are no explicit Linux shell or Azure CLI examples for common tasks, and the only code snippet for identifying key vaults uses PowerShell, which is more familiar to Windows users.
Recommendations
- Provide equivalent Azure CLI and/or Bash examples alongside PowerShell commands, especially for tasks like identifying a VM's associated key vault.
- When describing encryption technologies, mention Linux (dm-crypt) and Windows (BitLocker) tools in parallel, not always listing Windows first.
- Ensure that all automation and scripting instructions are available for both Windows (PowerShell) and Linux (Bash/CLI) users.
- Add explicit Linux-focused examples or callouts where workflows or commands differ.
- Review screenshots and UI instructions to ensure they are not overly Windows-centric (e.g., referencing right-clicks or UI elements that may differ on Linux).
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-extended-zones.md
...ain/articles/backup/backup-azure-vms-extended-zones.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation primarily focuses on Azure Portal-based workflows, which are platform-agnostic. However, in the 'Install the VM agent' section, Windows instructions are presented first, with explicit references to Windows-specific tools (MSI installer, C:\ paths, right-click context menus), while Linux instructions are less detailed and lack concrete command examples. No Linux command-line examples (e.g., Bash, az CLI) are provided anywhere in the document, and there are no references to Linux-specific tools or troubleshooting steps. This results in a subtle Windows bias, especially for users managing Linux VMs.
Recommendations
- Provide Linux instructions before or alongside Windows instructions in the 'Install the VM agent' section, including concrete command-line examples (e.g., using apt, yum, or zypper to install the agent).
- Add az CLI and/or Bash examples for key operations (e.g., enabling backup, monitoring jobs, cleaning up resources) to ensure parity for users who prefer or require command-line workflows, especially on Linux.
- Include Linux-specific troubleshooting tips (e.g., checking agent status with systemctl, log file locations) where relevant.
- Avoid Windows-centric language such as 'right-click', 'Properties', or explicit references to C:\ paths unless mirrored with Linux equivalents.
- Consider a dedicated section or callouts for Linux administrators to highlight any differences or best practices.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-introduction.md
.../main/articles/backup/backup-azure-vms-introduction.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 areas. Windows-specific tools (such as VSS) are described in detail and mentioned before Linux equivalents. PowerShell is referenced for restore operations, with no equivalent Linux CLI or automation example. Linux backup consistency relies on custom scripting, but no concrete Linux script example is provided, whereas Windows backup is described as automatic via VSS. Overall, Windows tools and patterns are presented as the default, with Linux support appearing as an afterthought.
Recommendations
- Provide Azure CLI or Bash examples for backup and restore operations alongside PowerShell, especially for tasks like restoring managed disks.
- Include concrete Linux pre/post script samples for achieving application-consistent backups, not just a link to another article.
- When describing backup consistency mechanisms, give equal detail to Linux (e.g., describe the 'freeze' tool and how it is used, not just mention it in passing).
- Present Windows and Linux instructions/examples in parallel, rather than always listing Windows first.
- Where possible, avoid language that implies Windows is the default or primary platform; instead, clarify parity and differences explicitly.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-instant-restore-capability.md
...n/articles/backup/backup-instant-restore-capability.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides configuration instructions for Instant Restore using the Azure portal and PowerShell, but does not mention or provide examples for Linux users (e.g., Azure CLI or Bash scripting). All command-line examples use PowerShell, which is primarily associated with Windows environments. There is no mention of Linux-specific tools or workflows, and no parity for Linux administrators.
Recommendations
- Add equivalent Azure CLI examples for configuring snapshot retention and other operations, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that the operations can be performed from Linux environments using Azure CLI or Bash, and provide sample commands.
- Where PowerShell is referenced, clarify if the steps are also supported in PowerShell Core on Linux, or provide alternative instructions.
- Ensure that screenshots and UI instructions do not assume a Windows environment.
- Include a section or note addressing Linux users and their typical workflows, ensuring parity in guidance and tooling.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-encryption.md
...re-docs/blob/main/articles/backup/backup-encryption.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning BitLocker (a Windows tool) before DM-Crypt (the Linux equivalent) in the context of Azure Disk Encryption. There are no explicit Linux command-line examples or references to Linux-specific backup workflows, and the only detailed example for in-guest encryption references BitLocker for Windows, with DM-Crypt for Linux mentioned secondarily and without further explanation. No Linux shell or tool usage is shown, and the documentation does not provide parity in examples or guidance for Linux users.
Recommendations
- Provide equal prominence to Linux tools such as DM-Crypt by mentioning them alongside BitLocker, not after.
- Include explicit examples or references for Linux backup scenarios, such as using Linux command-line tools or scripts.
- Add links to Linux-specific documentation for DM-Crypt and Azure Disk Encryption on Linux.
- Ensure that any workflow or process described for Windows (e.g., BitLocker usage) is also described for Linux, with step-by-step guidance or references.
- Consider including a table or section comparing Windows and Linux encryption approaches in Azure Backup to highlight parity.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-add-storage.md
...s/blob/main/articles/backup/backup-mabs-add-storage.md
High Priority
View Details →
Detected Bias Types
Windows Only
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All instructions, screenshots, and tools referenced are specific to Windows Server (e.g., Server Manager, ReFS, PowerShell cmdlets). There is no mention of Linux support, nor are there any Linux-specific instructions or examples. The documentation assumes the user is operating in a Windows ecosystem and does not address cross-platform scenarios.
Recommendations
- Clarify early in the documentation whether Azure Backup Server and Modern Backup Storage are Windows-only solutions, or if there is any Linux support or equivalent.
- If Linux is supported, provide parallel instructions and examples for Linux environments, including command-line equivalents and supported filesystems.
- If Linux is not supported, explicitly state this limitation at the beginning of the article to set user expectations.
- Where possible, mention cross-platform alternatives or Azure-native backup solutions that support Linux workloads.
- Avoid using only Windows-specific tools and terminology (e.g., Server Manager, PowerShell) without noting their platform limitations.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-files-applications-azure-stack.md
...s/backup/backup-mabs-files-applications-azure-stack.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows environments, specifically referencing Microsoft Azure Backup Server, which is a Windows-based tool. All instructions and screenshots are based on the Azure Backup Server console, with no mention of Linux-based backup solutions, command-line alternatives, or cross-platform considerations. There are no examples or guidance for Linux VMs or filesystems, and the workflow assumes a Windows-centric administrative experience.
Recommendations
- Include explicit instructions or references for backing up files and applications from Linux-based Azure Stack VMs, such as using Azure Backup agent for Linux or other supported methods.
- Provide command-line examples (e.g., Bash scripts, CLI commands) for Linux environments alongside or in addition to GUI-based instructions.
- Mention any Linux-compatible backup tools or agents supported by Azure Stack, and clarify any limitations or differences in feature support.
- Add screenshots or walkthroughs for Linux scenarios, if supported, to ensure parity with Windows examples.
- Clearly state in the prerequisites or introduction if the documented workflow is only supported for Windows VMs, and link to Linux-specific backup guidance if available.
Backup
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 Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments. All examples, tools, and instructions assume Windows servers, Windows command-line tools (CMD, Registry Editor), and Windows-specific services (VSS Writer, DCOM, NT AUTHORITY\SYSTEM). There are no Linux equivalents, nor any mention of Linux-based SharePoint deployments or Azure Backup Server support for Linux. The documentation presumes the use of Windows domains, file paths, and administrative patterns unique to Windows.
Recommendations
- Explicitly state platform requirements and limitations at the top of the documentation, clarifying if Linux is unsupported.
- If Linux support is possible, add equivalent instructions, examples, and tool references for Linux environments.
- Where possible, use cross-platform terminology and avoid Windows-specific jargon unless necessary.
- Provide a comparison table of supported OSes for MABS and SharePoint backup scenarios.
- Include notes or links to Linux backup solutions if MABS is Windows-only, to guide Linux users to alternatives.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-sql-azure-stack.md
...ob/main/articles/backup/backup-mabs-sql-azure-stack.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows environments, specifically Microsoft Azure Backup Server (MABS), which is a Windows-only tool. All instructions, screenshots, and workflows assume a Windows GUI and SQL Server running on Windows. There are no examples, instructions, or even mentions of Linux-based SQL Server or command-line alternatives (e.g., Bash, CLI). The documentation does not address Linux users or provide parity for cross-platform scenarios.
Recommendations
- Explicitly state in the prerequisites and introduction that MABS is a Windows-only tool, and clarify support for Linux-based SQL Server (if any).
- If Linux-based SQL Server on Azure Stack is supported, provide parallel instructions or note the differences/workarounds for Linux environments.
- Include command-line examples (e.g., using Azure CLI, Bash scripts, or cross-platform tools) where possible, not just GUI walkthroughs.
- Mention and link to Linux-native backup solutions or Azure Backup alternatives for Linux SQL Server, if MABS is not supported.
- Ensure that any references to system accounts, file paths, or permissions include Linux equivalents or note their absence.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-managed-disks-cli.md
.../blob/main/articles/backup/backup-managed-disks-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. While the main focus is on Azure CLI (which is cross-platform), variable assignment examples use PowerShell syntax (e.g., $DiskId = ...), which is specific to Windows and not valid in Bash or other Linux shells. There are no explicit Bash/Linux shell examples, nor are there notes about cross-platform differences. The 'Next steps' section lists Azure portal and PowerShell before CLI, reinforcing a Windows-first pattern. There is also a link to PowerShell-specific documentation for assigning permissions, but no equivalent Bash/Linux guidance.
Recommendations
- Replace PowerShell variable assignment examples (e.g., $DiskId = ...) with Bash-compatible syntax (e.g., DiskId=...) or provide both.
- Add explicit Bash/Linux shell examples alongside PowerShell where variables or scripting are involved.
- In 'Next steps', list CLI before PowerShell to avoid Windows-first ordering.
- Provide links to Linux/Bash-specific documentation for tasks like assigning permissions, or clarify that the CLI commands work identically on Linux/macOS.
- Add a note at the top clarifying that Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-managed-disks.md
...docs/blob/main/articles/backup/backup-managed-disks.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation primarily describes how to back up Azure Managed Disks using the Azure portal, with only brief references to scripting alternatives. When scripts are mentioned, PowerShell is listed before Azure CLI, and there are no explicit Linux-specific examples or guidance. The 'Next steps' section also lists PowerShell before CLI, and there is no mention of Bash or Linux shell scripting. The documentation assumes familiarity with Windows-centric tools and patterns, which may disadvantage Linux users.
Recommendations
- When referencing scripting options, list Azure CLI before or alongside PowerShell, and provide parity in examples for both.
- Explicitly mention that Azure CLI can be used from Linux, macOS, and Windows, and provide Bash shell examples where relevant.
- Add links or sections for Linux users, such as 'How to back up Azure Managed Disks using Azure CLI on Linux'.
- Ensure that all references to scripts or automation include both PowerShell and Bash/CLI examples, not just PowerShell.
- Avoid Windows-first ordering when listing tools or approaches; alternate or group by platform.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-overview.md
...zure-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 for Azure Backup demonstrates a Windows bias by prominently mentioning Windows-specific backup agents (MARS, DPM, MABS) and tools before Linux equivalents, and by providing examples and links that focus on Windows workloads. Linux backup scenarios are referenced only in passing (e.g., 'Windows/Linux VMs'), with no detailed Linux-specific examples or tool guidance. There is a lack of parity in describing Linux backup options, agents, or best practices compared to the detailed coverage of Windows tools.
Recommendations
- Add explicit examples and guidance for backing up Linux systems, including supported Linux distributions and file systems.
- Include Linux-specific agent/tool names, installation instructions, and links to relevant documentation.
- Present Windows and Linux backup scenarios in parallel, ensuring equal detail and visibility for both platforms.
- Highlight any differences or limitations for Linux backup (e.g., application consistency, file-level restore) to help users plan accordingly.
- Provide sample commands or scripts for Linux environments (e.g., shell commands, cron job integration) alongside PowerShell/Windows examples.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-reports-email.md
...docs/blob/main/articles/backup/backup-reports-email.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Office 365/Outlook (a Microsoft/Windows-centric email solution) and the Azure portal for configuration, with no mention of Linux-native tools, open-source alternatives, or cross-platform command-line approaches. All examples and troubleshooting steps are tailored to the Azure portal and Office 365, and there is no guidance for users who may prefer or require Linux-based email solutions or automation tools. The documentation also presents the Azure portal (a GUI) as the primary method, which is more familiar to Windows users, and only secondarily mentions ARM templates, with no mention of CLI or scripting alternatives common in Linux environments.
Recommendations
- Provide examples or guidance for configuring email delivery using Linux-native tools (e.g., sendmail, Postfix, or mailx) or open-source alternatives to Office 365.
- Include Azure CLI or Azure PowerShell examples for automation, and ensure parity between PowerShell and Bash/CLI instructions.
- Mention and link to documentation for integrating with non-Microsoft email providers (such as Gmail, SendGrid, or SMTP servers) for users who do not use Office 365.
- Add troubleshooting steps relevant to Linux environments, such as checking logs or permissions for Linux-based automation tools.
- Ensure that all platform-specific instructions are clearly labeled, and provide equivalent steps for both Windows and Linux users where possible.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-database-from-azure-vm-blade.md
...ckup/backup-sql-server-database-from-azure-vm-blade.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows-based SQL Server VMs. It exclusively references the AzureBackupWindowsWorkload extension, NT Service accounts, and Windows-specific service accounts. There are no examples or instructions for SQL Server on Linux VMs, nor any mention of Linux-specific tools or differences. The documentation implicitly assumes SQL Server is running on Windows, and does not address Linux scenarios.
Recommendations
- Add explicit guidance for backing up SQL Server running on Linux-based Azure VMs, including any differences in supported features or required extensions.
- Mention and document any Linux-specific backup agents or extensions, or clarify if Azure Backup does not support SQL Server on Linux VMs.
- Include examples or callouts for Linux users, such as differences in service accounts, permissions, or extension installation.
- If Azure Backup does not support SQL Server on Linux, state this clearly at the beginning of the article.
- Ensure parity in documentation by providing Linux and Windows instructions side-by-side where applicable.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/modify-vm-policy-cli.md
...docs/blob/main/articles/backup/modify-vm-policy-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows environments by using a Windows-style file path (C:\temp2\Policy.json) in the Azure CLI example and not providing a Linux/macOS equivalent. There are no examples or notes for Linux users regarding file paths or command usage, and the documentation implicitly assumes a Windows environment.
Recommendations
- Provide both Windows and Linux/macOS file path examples when referencing files in CLI commands (e.g., C:\temp2\Policy.json and /tmp/Policy.json).
- Add a note clarifying that file paths should be adapted to the user's operating system.
- Include explicit Linux/macOS CLI examples or mention that the Azure CLI commands are cross-platform.
- Avoid using only Windows-specific conventions in cross-platform documentation.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-on-availability-groups.md
...les/backup/backup-sql-server-on-availability-groups.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page focuses exclusively on SQL Server Always On Availability Groups in Azure VMs, implicitly assuming a Windows environment. There are no examples, instructions, or mentions of Linux-based SQL Server deployments, nor any Linux-specific backup tooling or patterns. All references to backup extensions, registration, and failover are written from the perspective of Windows VMs, with no guidance for Linux users. The documentation also omits any mention of cross-platform compatibility or differences, and does not provide parity for Linux SQL Server scenarios.
Recommendations
- Add explicit guidance for SQL Server AG deployments on Linux, including any limitations or differences in Azure Backup support.
- Provide Linux-specific examples for registering AG nodes, configuring backups, and handling failover, using relevant Linux tools and commands.
- Clarify whether the Azure Backup workload extension is supported on Linux SQL Server VMs, and if not, document alternative backup strategies for Linux.
- Include a section comparing Windows and Linux support for SQL Server AG backups in Azure, highlighting any feature gaps or required steps.
- Ensure that all instructions and diagrams mention both Windows and Linux scenarios where applicable, and avoid assuming a Windows-only environment.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-the-mabs-server.md
...cs/blob/main/articles/backup/backup-the-mabs-server.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All backup and recovery procedures rely on Windows-specific tools (e.g., PowerShell, mountvol.exe, diskshadow.exe, psexec.exe, VSS, Windows Explorer), and all example commands and scripts are for Windows. There are no Linux equivalents or cross-platform instructions, and the documentation assumes the use of Windows-based SQL Server and file paths. No mention is made of Linux support, alternative tools, or how to perform these tasks on non-Windows systems.
Recommendations
- Clearly state in the prerequisites or introduction if MABS is only supported on Windows. If so, explain why and link to alternatives for Linux users.
- If any components (such as SQL Server) can be hosted on Linux, provide equivalent Linux commands and procedures for backup and restore.
- For each example using Windows-specific tools (e.g., PowerShell, mountvol.exe, diskshadow.exe), provide Linux equivalents or note their absence.
- Where file paths or shares are referenced (e.g., C:\ paths, UNC shares), include Linux path examples if supported.
- If VSS (Volume Shadow Copy Service) or Windows Previous Versions are used, mention Linux alternatives (e.g., LVM snapshots, rsync, etc.) or clarify that these features are not available on Linux.
- Add a section explicitly addressing cross-platform support and limitations, so Linux administrators know what is and isn't possible.
- If MABS is strictly Windows-only, suggest alternative backup solutions for Linux environments (e.g., Azure Backup for Linux, third-party tools).
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-vm-from-vm-pane.md
...n/articles/backup/backup-sql-server-vm-from-vm-pane.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation focuses exclusively on backing up SQL Server VMs using the Azure portal UI, with no mention of Linux-specific tools, commands, or considerations. All examples and screenshots are oriented toward the Windows/SQL Server environment, and there is no discussion of Linux-based SQL Server VMs or command-line alternatives (e.g., Bash, Linux CLI). The related content references Azure CLI and REST API, but the main instructions and UI are Windows-centric.
Recommendations
- Add explicit instructions or notes for backing up SQL Server on Linux-based Azure VMs, including any differences in the process or prerequisites.
- Include examples using Bash or Linux shell commands where applicable, especially if there are CLI-based alternatives.
- Mention any Linux-specific considerations (e.g., permissions, file system differences) when configuring backup.
- Ensure screenshots and UI references clarify if they apply to both Windows and Linux SQL Server VMs, or provide Linux-specific visuals if the experience differs.
- List Linux and cross-platform options alongside Windows options, not just in related content but in the main instructional flow.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix.md
...ocs/blob/main/articles/backup/backup-support-matrix.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows backup scenarios and tools (MARS, DPM, MABS) throughout, often listing Windows support and features first or exclusively. Linux support is frequently noted as 'not supported' or is only available via indirect or limited methods (e.g., file-consistent backup for Linux VMs via DPM/MABS, custom scripts for app-consistency). There are no Linux-specific examples, and Windows tools are referenced without Linux equivalents. The documentation assumes familiarity with Windows-centric backup patterns and does not provide parity in Linux guidance.
Recommendations
- Provide Linux-specific backup examples and workflows where possible, especially for Azure VM and on-premises scenarios.
- List Linux support and features alongside Windows in all tables and descriptions, rather than as afterthoughts or exclusions.
- Include Linux-native tools and commands (e.g., shell scripts, cron jobs, rsync, etc.) where relevant, or clarify their (lack of) support explicitly.
- Offer guidance or references for Linux users seeking backup solutions outside the MARS/DPM/MABS ecosystem, including third-party or Azure-native alternatives.
- Ensure that any mention of Windows tools or features is balanced with Linux equivalents or clear statements about platform limitations.
- Add more detail and links for configuring app-consistent backups on Linux, not just referencing 'custom scripts'.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/blob-backup-configure-manage.md
...b/main/articles/backup/blob-backup-configure-manage.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page primarily describes backup configuration and management using the Azure portal, with references to Azure PowerShell, Azure CLI, and REST API in the 'Related content' section. However, throughout the main guide, there are no explicit CLI or Linux-oriented examples, and PowerShell is mentioned before CLI in the related links. The step-by-step instructions and screenshots are focused on the Azure portal, which is platform-neutral but often more familiar to Windows users. There is no mention of Linux-specific tools, shell commands, or parity guidance for users on Linux systems.
Recommendations
- Add explicit Azure CLI examples alongside PowerShell references, especially in sections describing backup and restore operations.
- Provide sample commands for common Linux shells (bash/zsh) where applicable, such as role assignment or backup configuration.
- Ensure that CLI instructions are presented before or alongside PowerShell instructions to avoid Windows-first bias.
- Include notes or links to Linux-specific documentation or troubleshooting guides for Azure Backup.
- Clarify that all operations can be performed from Linux, macOS, or Windows, and highlight any platform-specific considerations.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/disk-backup-overview.md
...docs/blob/main/articles/backup/disk-backup-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a mild Windows bias. Windows-specific technologies (e.g., Volume Shadow Copy Service, Windows Server Failover Cluster) are mentioned before or more prominently than Linux equivalents. There are no Linux-specific backup consistency mechanisms or tools referenced, and no explicit Linux command-line or scripting examples are provided. The documentation assumes familiarity with Windows patterns and does not provide parity in Linux-specific guidance or examples.
Recommendations
- Include Linux-specific backup consistency mechanisms (e.g., LVM snapshots, fsfreeze) alongside mentions of VSS.
- Provide explicit examples or references for Linux environments, such as how to prepare Linux VMs for crash-consistent or application-consistent backups.
- Mention Linux clustering technologies (e.g., Pacemaker, Corosync) when referencing Windows Server Failover Cluster.
- Add Linux command-line or scripting examples (e.g., using Azure CLI on Linux) where relevant.
- Ensure that Linux and Windows scenarios are given equal prominence and detail in all relevant sections.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-telemetry.md
...ure-docs/blob/main/articles/backup/manage-telemetry.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows, referencing only the Microsoft Azure Backup Server (MABS) console, which is a Windows application. All instructions and screenshots are for the Windows GUI, with no mention of Linux equivalents, CLI commands, or cross-platform alternatives. There is no guidance for managing telemetry settings on Linux systems, nor any mention of PowerShell or Windows-specific tools, but the overall context and examples are exclusively Windows-centric.
Recommendations
- Clarify platform support: Explicitly state whether MABS and telemetry management are available on Linux or only on Windows.
- If Linux is supported, provide equivalent instructions for managing telemetry settings on Linux, including CLI commands or configuration file edits.
- Include cross-platform guidance or alternatives, such as REST API or scripting options, if available.
- Add a section comparing Windows and Linux management options, or explicitly note limitations for non-Windows platforms.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/install-mars-agent.md
...e-docs/blob/main/articles/backup/install-mars-agent.md
High Priority
View Details →
Detected Bias Types
Windows Only
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exclusively describes installation and usage of the MARS agent for Windows machines, with all instructions, screenshots, and prerequisites focused on Windows environments. There are no examples, instructions, or mentions of Linux support or Linux equivalents. Windows tools (such as PowerShell, .NET Framework, and Windows-specific installer files) are referenced throughout, and the only scripting example provided is for PowerShell. The page title, customer intent, and all steps reinforce a Windows-centric approach, with no Linux parity.
Recommendations
- Clearly state in the introduction whether the MARS agent is Windows-only, and if so, provide links or guidance for Linux backup solutions (e.g., Azure Backup for Linux VMs, Azure Backup Server, or third-party tools).
- If Linux support exists, add equivalent installation and usage instructions for Linux, including command-line examples, package requirements, and screenshots.
- Provide parity in scripting examples by including Bash or shell script alternatives alongside PowerShell.
- Reference Linux backup patterns and tools where appropriate, and avoid implying that Azure Backup is only for Windows by updating customer intent and summary sections.
- If the MARS agent is not available for Linux, clarify this limitation and direct Linux users to supported alternatives.