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 726-750 of 2185 flagged pages
Azure Docs
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
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily Windows-centric: all troubleshooting steps, examples, and tools (such as Performance Monitor and MARS agent) are specific to Windows. There are no Linux equivalents, examples, or guidance, and the language assumes the user is operating in a Windows environment. Linux users are not addressed, and no cross-platform considerations are mentioned.
Recommendations
- Add explicit mention of supported operating systems at the top of the article. If only Windows is supported, clarify this early.
- If Linux is supported, provide equivalent troubleshooting steps, examples, and tools for Linux environments (e.g., using iostat, vmstat, atop for performance monitoring).
- Include Linux-specific log file locations and agent behaviors, if applicable.
- Where Windows tools are referenced (e.g., Performance Monitor), provide Linux alternatives and example commands.
- Ensure that all recommendations (such as antivirus exclusions, disk defragmentation, etc.) have Linux analogs or note if not applicable.
- Add screenshots or command-line examples for Linux where relevant.
- Structure the documentation so that Windows and Linux guidance are clearly separated or paralleled, rather than Windows-first.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/includes/digital-twins-local-credentials-inner.md
...wins/includes/digital-twins-local-credentials-inner.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation prioritizes Windows-centric tools and workflows by mentioning Visual Studio and Visual Studio Code sign-in before CLI usage, and does not provide Linux-specific guidance or examples. It assumes the use of editors and tools more common on Windows, without acknowledging Linux alternatives or nuances.
Recommendations
- Explicitly mention that Visual Studio Code is cross-platform and available on Linux and macOS, not just Windows.
- Include examples or notes for Linux users, such as using the Azure CLI in a Linux terminal.
- Reference other popular Linux editors (e.g., Vim, Emacs) and clarify that signing in via Azure CLI works regardless of the editor.
- Reorder the instructions to present CLI-based authentication first, as it is platform-agnostic.
- Add a section or note confirming that the described authentication steps apply equally on Linux, macOS, and Windows.
Azure Docs
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 provides links to Windows VM Agent and snapshot extension documentation only. There are no Linux-specific examples or links, and Linux is only mentioned in passing without further guidance or parity in documentation references.
Recommendations
- Provide equal prominence to Linux tools and processes (e.g., link to Linux VM Agent and snapshot extension documentation alongside Windows).
- Include Linux-specific examples or scenarios, such as how crash-consistent backups interact with Linux filesystems or typical Linux workloads.
- Mention Linux tools (like fsfreeze) before or alongside Windows tools (like VSS), not after.
- Add links to relevant Linux documentation for VM Agent and snapshot extension, not just Windows.
- Clarify any differences in backup behavior or requirements between Windows and Linux VMs.
Azure Docs
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 greater detail than their Linux equivalents. Windows-specific GUI workflows are described step-by-step with screenshots, while Linux guidance is often limited to references or brief command-line instructions. Some troubleshooting scenarios provide detailed Windows instructions but refer Linux users to other documentation or omit equivalent Linux steps entirely.
Recommendations
- Provide Linux troubleshooting steps alongside Windows steps, ensuring parity in detail and clarity.
- Include Linux command-line equivalents for all Windows GUI actions (e.g., using lsblk, mount, fdisk, or parted for disk management).
- Add Linux-specific screenshots or terminal outputs where Windows screenshots are used.
- Avoid referencing Linux solutions only as links; instead, summarize key steps directly in the troubleshooting flow.
- When mentioning Windows tools (e.g., File Explorer, Disk Management), also mention and explain the Linux alternatives (e.g., file managers, mount commands, /etc/fstab).
- Ensure error messages and their resolutions are covered for both platforms with equal depth.
Azure Docs
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 exhibits a Windows-first bias in several areas. Windows-specific tools and patterns (such as VSS and PowerShell) are mentioned first or exclusively, while Linux equivalents are either mentioned later, in less detail, or require custom user intervention (e.g., custom scripts for app consistency). There is a lack of concrete Linux command examples, and the guidance for Linux users is less prescriptive and more reliant on user implementation.
Recommendations
- Provide Linux command-line examples (e.g., Bash/CLI) alongside or before PowerShell examples, especially in automation and restore scenarios.
- Describe Linux-native tools (such as fsfreeze, LVM snapshots, or other consistency mechanisms) in detail, not just as 'custom scripts'.
- Offer ready-to-use sample pre/post scripts for common Linux workloads (e.g., MySQL, PostgreSQL) to match the prescriptive guidance given for Windows (VSS).
- Ensure that Linux-specific backup and restore workflows are documented with the same depth and clarity as Windows workflows.
- Avoid always listing Windows tools or patterns first; alternate or parallelize the presentation of Windows and Linux approaches.
- Explicitly mention any Azure Backup features or limitations that are unique to Linux, and provide guidance or workarounds where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-vms-encryption.md
...b/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, while stating support for both Windows and Linux Azure VMs, demonstrates a Windows bias in several areas. PowerShell is the only command-line example provided (for identifying a VM's associated Key Vault), with no equivalent Linux/CLI example. In the 'Provide permissions' section, the PowerShell command is presented first and exclusively, with the CLI option only mentioned as a link, not as an inline example. Additionally, BitLocker (Windows) is described before dm-crypt (Linux) in the ADE section, and there are no Linux-specific command or troubleshooting examples.
Recommendations
- For every PowerShell example, provide an equivalent Azure CLI (az) example, especially for tasks like identifying the Key Vault associated with a VM.
- When referencing OS-specific encryption technologies (BitLocker, dm-crypt), present them in parallel and with equal detail.
- Where possible, avoid presenting Windows tools or patterns first; alternate or present both together.
- Include Linux-specific troubleshooting tips or links, especially where agent installation or backup extension issues may differ.
- Ensure that all procedural steps (such as setting permissions or configuring backup) include both PowerShell and CLI/Linux-friendly instructions inline, not just as external links.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-vms-troubleshoot.md
...main//articles/backup/backup-azure-vms-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a noticeable Windows bias. Troubleshooting steps and error resolutions frequently reference Windows-specific tools (such as Services.msc, Event Viewer, regedit, command prompt, and registry edits) and PowerShell cmdlets, often without providing equivalent Linux instructions or alternatives. Windows troubleshooting is often presented first or exclusively, while Linux guidance is limited to a few sections and is less detailed. Several error resolutions (e.g., VSS, COM+, BitLocker, registry edits) are only relevant to Windows, with no Linux context or parallel troubleshooting steps provided.
Recommendations
- For every troubleshooting step or error code that references Windows tools (e.g., Services.msc, Event Viewer, regedit, registry keys, VSS, COM+), provide equivalent Linux commands or log file locations (e.g., systemctl, journalctl, syslog, Linux agent logs).
- Where PowerShell or Windows command prompt commands are given (e.g., net start, net stop, icacls, REG ADD), include corresponding Linux shell commands or configuration file edits, or explicitly state if not applicable.
- When referencing Windows-specific backup products or features (e.g., Windows Server Backup, BitLocker), clarify their Linux equivalents or note their absence.
- Ensure that Linux troubleshooting is not only present but given equal prominence and detail as Windows, including examples for common Linux distributions.
- Add more Linux-specific error scenarios and their resolutions, especially for agent installation, permissions, disk/mount issues, and backup extension failures.
- In summary tables and step-by-step guides, always provide both Windows and Linux paths, commands, and screenshots where appropriate.
- Review the order of presentation to avoid always listing Windows first; alternate or group by OS where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-sql-server-azure-troubleshoot.md
...rticles/backup/backup-sql-server-azure-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. All file paths, process names, and configuration steps reference Windows conventions (e.g., C:\ paths, NT AUTHORITY accounts, Control Panel, Local Security Policy). There are no Linux examples or mentions of Linux-based SQL Server VMs. The extension referenced is AzureBackupWindowsWorkload, and all troubleshooting steps, error messages, and recommendations assume a Windows environment. PowerShell is referenced as the automation method, with no mention of Bash, CLI, or Linux-native tools.
Recommendations
- Add equivalent instructions, file paths, and process names for Linux-based SQL Server VMs where supported.
- Clearly indicate if features or extensions are Windows-only, and provide links or notes for Linux alternatives if available.
- Include Linux troubleshooting steps, such as commands for checking permissions, service status, and log locations.
- Provide automation examples using Azure CLI or Bash scripts for Linux environments.
- When referencing tools (e.g., Control Panel, Local Security Policy), offer Linux equivalents (e.g., systemd, chown/chmod, relevant config files).
- Explicitly state OS prerequisites at the start of the document, and link to Linux-specific documentation if this page is not applicable.
Azure Docs
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 exclusively describes backup and recovery using Microsoft Azure Backup Server, which is a Windows-based tool. All instructions, screenshots, and workflows are based on the Azure Backup Server console, with no mention of Linux-based backup agents, command-line tools, or Linux VM scenarios. There are no examples or guidance for Linux VMs or for performing these tasks using Linux-native tools or interfaces.
Recommendations
- Include explicit guidance for backing up and recovering files from Linux-based Azure Stack VMs, such as using the Azure Backup Linux agent or native Linux backup tools.
- Provide parallel examples and screenshots for Linux environments, including command-line instructions (e.g., using shell scripts or CLI tools) where appropriate.
- Mention Linux support and any prerequisites or limitations for Linux VMs in Azure Stack environments.
- If Azure Backup Server does not support Linux VMs, clearly state this and provide alternative recommendations for Linux backup.
- Ensure that references to tools and workflows are not Windows-specific by default, or provide equivalent Linux options alongside Windows instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-mabs-release-notes-v3.md
.../main//articles/backup/backup-mabs-release-notes-v3.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation for Microsoft Azure Backup Server v3 is heavily oriented toward Windows environments. All examples, tools, and instructions assume the use of Windows Server, SQL Server Management Studio (SSMS), and other Microsoft-specific technologies. There are no references to Linux environments, tools, or procedures, and no Linux-specific issues or workarounds are mentioned.
Recommendations
- Explicitly state the platform support for MABS (e.g., if it is Windows-only, clarify this early in the documentation).
- If Linux is supported, provide equivalent instructions, examples, and troubleshooting steps for Linux environments.
- Mention Linux-compatible tools or alternatives where possible (e.g., using sqlcmd or Azure CLI for database operations).
- Include notes or links for users managing hybrid or non-Windows environments, if applicable.
- Review all examples and tool references to ensure Linux administrators are not excluded or left without guidance.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-mabs-add-storage.md
.../blob/main//articles/backup/backup-mabs-add-storage.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 instructions, screenshots, and tooling (Server Manager, PowerShell cmdlets, ReFS, Windows Server versions) focused exclusively on Windows environments. There are no Linux examples, nor is there any mention of Linux support or alternatives. The workflow assumes the use of Windows Server and its management tools, and PowerShell is the only scripting interface referenced.
Recommendations
- Clearly state in the introduction or prerequisites whether Linux is supported or not for Azure Backup Server and Modern Backup Storage. If not, make this explicit to set user expectations.
- If Linux support exists or is planned, provide equivalent instructions, examples, and screenshots for Linux environments (e.g., using Linux filesystems, CLI tools, and storage management).
- If only Windows is supported, add a prominent note to clarify this and, if possible, suggest alternative backup solutions for Linux users.
- Avoid using only PowerShell examples; if cross-platform CLI tools exist, include those as well.
- When referencing tools (e.g., Server Manager), mention if there are Linux equivalents or clarify that these steps are specific to Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-mabs-sql-azure-stack.md
...b/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 towards Windows environments, specifically referencing Microsoft Azure Backup Server (MABS), which is a Windows-only tool. All instructions, UI references, and screenshots are based on the Windows GUI, with no mention of Linux-based SQL Server deployments, command-line alternatives, or cross-platform backup solutions. There are no Linux or PowerShell/CLI examples, and the documentation assumes the use of Windows-specific accounts and patterns (e.g., NTAuthority\System, MMC-style wizards).
Recommendations
- Explicitly state that MABS is a Windows-only solution and clarify support for Linux-based SQL Server, if any.
- If Linux-based SQL Server on Azure Stack is supported, provide parallel instructions or references for Linux environments, including command-line (bash) or cross-platform tools.
- Include examples using Azure CLI, PowerShell, or REST API for backup and recovery operations, which can be used on both Windows and Linux.
- Mention any alternative backup solutions for Linux-based SQL Server (e.g., Azure Backup integration with Linux, or third-party tools) if MABS is not supported.
- Avoid assuming the presence of Windows-specific accounts (like NTAuthority\System) or GUI workflows; provide equivalent steps for Linux or clarify limitations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/includes/digital-twins-setup-verify-role-assignment.md
...includes/digital-twins-setup-verify-role-assignment.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively describes using the Azure portal (a web-based GUI) to verify role assignments, which is a platform-agnostic method but is often associated with Windows-centric workflows. There are no examples or mentions of command-line alternatives such as Azure CLI or PowerShell, which would provide parity for Linux users. The lack of CLI instructions or Linux-specific guidance may make the documentation less accessible to users who prefer or require non-GUI, cross-platform solutions.
Recommendations
- Add instructions for verifying role assignments using the Azure CLI, which is cross-platform and widely used on Linux.
- Include PowerShell examples if desired, but ensure they are presented alongside Azure CLI examples, not exclusively or first.
- Explicitly mention that the Azure portal is accessible from any operating system, but provide CLI alternatives for users who prefer or require them.
- Consider adding a table or section comparing verification methods (Portal, Azure CLI, PowerShell) to highlight cross-platform options.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-mabs-system-state-and-bmr.md
...n//articles/backup/backup-mabs-system-state-and-bmr.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All examples, workflows, and tool references are specific to Windows Server, Windows Server Backup, and PowerShell cmdlets. There is no mention of Linux support, Linux backup tools, or Linux-specific workflows. The documentation assumes the use of Windows-only features and does not provide parity for Linux systems.
Recommendations
- Clearly state at the beginning of the documentation whether Azure Backup Server supports Linux system state and bare-metal recovery, and if not, provide links to Linux backup documentation.
- If Linux is supported, add equivalent Linux backup and recovery workflows, including examples using native Linux tools (e.g., rsync, tar, dd, or third-party solutions).
- Provide Linux-specific prerequisites, limitations, and supported scenarios in parity with the Windows sections.
- Include command-line examples for Linux (e.g., bash scripts or CLI commands) alongside PowerShell examples.
- Reference Linux backup and recovery tools (such as Timeshift, Clonezilla, or Azure Backup agent for Linux) where appropriate.
- Ensure that all UI and wizard steps are matched with Linux equivalents or clearly note when features are Windows-only.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-managed-disks.md
...ocs/blob/main//articles/backup/backup-managed-disks.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation primarily focuses on using the Azure portal for backup operations, but when mentioning scripting or automation, it lists PowerShell before CLI and does not provide direct Linux/bash examples. The 'Next steps' and automation guidance consistently mention PowerShell before CLI, and there is no explicit mention of Linux-specific tools or workflows. This ordering and lack of Linux-centric examples may make Linux users feel secondary or unsupported.
Recommendations
- When referencing automation, list Azure CLI before or alongside PowerShell, as CLI is cross-platform and commonly used on Linux.
- Provide explicit bash/Azure CLI examples for common tasks, not just PowerShell.
- Include references to Linux-native scripting environments (e.g., bash) and clarify that all CLI examples are cross-platform.
- In 'Next steps' and related content, alternate the order of PowerShell and CLI, or group them together as equal options.
- Add a section or note highlighting that all features are available and supported on Linux, and provide links to Linux-specific guidance where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-mabs-protection-matrix.md
...main//articles/backup/backup-mabs-protection-matrix.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias: all detailed examples, supported workloads, and recovery scenarios focus on Windows operating systems and applications. Linux is only mentioned as a VM guest, with no native or agent-based Linux backup support or examples. Windows-specific tools and filesystems (e.g., NTFS, VSS, ReFS) are referenced throughout, while Linux filesystems and backup scenarios are omitted.
Recommendations
- Provide explicit examples and documentation for protecting native Linux workloads, not just Linux VMs running on Windows hosts.
- Include details about supported Linux filesystems (e.g., ext4, xfs, btrfs) and any limitations or requirements.
- Add parity in recovery scenarios for Linux (e.g., item-level/file-level recovery, not just entire VM restore).
- Mention Linux backup agents or integration options if available, or clarify their absence.
- List Linux-specific data protection issues and unsupported data types, similar to the Windows section.
- Ensure Linux is not always listed last or as an afterthought; integrate Linux scenarios alongside Windows where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-rbac-rs-vault.md
...ocs/blob/main//articles/backup/backup-rbac-rs-vault.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific backup tools (such as the Azure Backup agent client UI, System Center Data Protection Manager UI, and Azure Backup Server UI) without mentioning Linux equivalents. The section on registering on-premises machines only lists Windows Server/client/SCDPM or Azure Backup Server, omitting Linux backup agents or scenarios. There are no explicit Linux or cross-platform examples or tool mentions, and the documentation does not clarify how Linux VMs or workloads are managed in the context of Azure Backup RBAC. Additionally, where command-line tooling is referenced, PowerShell is mentioned before Azure CLI, which is more cross-platform.
Recommendations
- Explicitly mention and provide examples for Linux backup scenarios, such as registering on-premises Linux servers with Azure Backup.
- Reference cross-platform tools (e.g., Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
- If certain features are Windows-only, clearly state this and provide guidance or alternatives for Linux users.
- Include Linux-specific backup agents or workflows in the tables and examples, ensuring parity with Windows coverage.
- Where UI tools are listed (e.g., Azure Backup agent, SCDPM), mention if there are Linux equivalents or clarify their absence.
Azure Docs
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 page demonstrates a Windows bias by exclusively describing backup procedures for SQL Server on Azure VMs using Windows-specific tools and extensions (e.g., AzureBackupWindowsWorkload, NT Service accounts, SQLIaaSExtension). There is no mention of Linux-based SQL Server VMs, nor are any Linux-specific instructions, tools, or caveats provided. The documentation implicitly assumes the SQL Server VM is running Windows, and Linux parity is not addressed.
Recommendations
- Explicitly state whether the described procedure applies only to Windows-based SQL Server VMs, or clarify support for Linux-based SQL Server VMs.
- If Linux-based SQL Server VMs are supported, provide parallel instructions, screenshots, and notes for configuring Azure Backup on Linux VMs.
- Document any differences in agent/extension installation, service accounts, and permissions for Linux VMs (e.g., use of systemd services, different backup extensions, or required user accounts).
- Include troubleshooting and FAQ sections specific to Linux-based SQL Server VMs.
- If Linux is not supported, clearly state this limitation at the beginning of the article to avoid confusion.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-the-mabs-server.md
...s/blob/main//articles/backup/backup-the-mabs-server.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily Windows-centric, with all operational instructions, examples, and tooling based on Windows environments. It exclusively references Windows tools (PowerShell, mountvol.exe, diskshadow.exe, psexec.exe, Net Share, Windows Explorer), Windows file paths, and Windows-specific features (VSS, Previous Versions). There are no examples or guidance for performing any backup or restore operations from Linux or non-Windows platforms, nor is there mention of cross-platform alternatives.
Recommendations
- Add explicit statements clarifying platform support (e.g., if MABS is Windows-only, state this clearly at the top).
- If any operations can be performed from Linux (e.g., accessing SMB shares, restoring SQL backups), provide equivalent Linux command-line examples (e.g., using smbclient, mount.cifs, or sqlcmd).
- Where possible, mention cross-platform tools or methods (e.g., using Azure CLI or REST APIs for backup/restore, or SQL Server tools available on Linux).
- For file operations, provide both Windows and Linux command examples (e.g., copy files using cp or scp on Linux).
- If restore or backup is only possible from Windows, explicitly state this limitation and suggest workarounds or alternatives for Linux environments.
- Review all code and command snippets to ensure Linux parity where feasible, or provide rationale for Windows-only steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-support-automation.md
...lob/main//articles/backup/backup-support-automation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation consistently lists PowerShell (a Windows-centric tool) as the first automation method in all operation tables, and provides explicit PowerShell example links for nearly every scenario. This ordering and emphasis on PowerShell, even when cross-platform tools like Azure CLI are equally or more relevant for Linux users, demonstrates a Windows-first and PowerShell-heavy bias. There is little to no mention of Linux-native scripting or automation patterns, and no explicit Linux shell (bash) examples are provided. The documentation assumes PowerShell as the primary scripting interface, which may alienate Linux administrators.
Recommendations
- Alternate the order of PowerShell and CLI columns in tables, or list CLI first for scenarios where Linux is common.
- Explicitly mention that Azure CLI commands and examples are cross-platform and can be run on Linux, macOS, and Windows.
- Add bash shell script examples or references for common automation tasks, especially for Linux-centric workloads.
- Where PowerShell is not supported (e.g., SAP HANA), highlight this as a parity issue and provide guidance for Linux users.
- Include a section or callout for Linux administrators, summarizing recommended tools and scripting approaches.
- Review linked example pages to ensure they include Linux-friendly instructions and not just PowerShell scripts.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-sql-server-database-azure-vms.md
...rticles/backup/backup-sql-server-database-azure-vms.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation page exhibits a Windows-centric bias. It assumes SQL Server VMs are running Windows, references Windows-specific agents and extensions (e.g., AzureBackupWindowsWorkload, NT Service\AzureWLBackupPluginSvc), and provides troubleshooting scripts only for Windows. There are no examples or guidance for SQL Server on Linux VMs, nor are Linux-specific tools, agents, or differences mentioned. The documentation implicitly treats Windows as the default or only supported OS for SQL Server in Azure VMs.
Recommendations
- Explicitly state OS support: Clarify early in the article whether the guidance applies to both Windows and Linux SQL Server VMs, or only Windows.
- Add Linux parity: If Azure Backup supports SQL Server on Linux VMs, provide equivalent instructions, prerequisites, and troubleshooting steps for Linux (e.g., mention Linux VM Agent, Linux-specific extensions, and service accounts).
- Provide Linux examples: Include Linux command-line examples (e.g., Bash, Azure CLI on Linux) and reference Linux-specific diagnostic scripts if available.
- Mention differences: Highlight any differences in backup/restore workflows, agent installation, or permissions between Windows and Linux SQL Server VMs.
- Balance tool references: Where troubleshooting scripts or tools are provided for Windows, offer or reference Linux alternatives, or note their absence.
- Update terminology: Use neutral language (e.g., 'the VM' instead of 'the Windows VM') unless a step is truly OS-specific.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-support-matrix-mabs-dpm.md
...ain//articles/backup/backup-support-matrix-mabs-dpm.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows environments, with all examples, supported operating systems, and deployment scenarios referencing only Windows Server versions. There is no mention of Linux support, Linux-based workloads, or cross-platform backup scenarios. All tools, workflows, and requirements are Windows-centric, and Linux is entirely omitted from compatibility, deployment, and management discussions.
Recommendations
- Explicitly state whether Linux operating systems and workloads are supported or not. If not supported, clarify this early in the documentation.
- If Linux support is available (even partially), add equivalent sections and examples for Linux-based deployments, including supported distributions, installation steps, and backup scenarios.
- Include Linux-specific requirements, limitations, and best practices where applicable.
- Mention Linux tools or agents if available, and provide parity in documentation structure (e.g., tables listing both Windows and Linux OS support).
- If only Windows is supported, consider adding a comparison or guidance for Linux users, such as recommending alternative Azure Backup solutions for Linux workloads.
Azure Docs
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 assumes SQL Server is running on Windows, with no mention of Linux-based SQL Server deployments. There are no examples or guidance for Linux environments, and all references to backup extensions, registration, and failover implicitly target Windows VMs. The lack of Linux-specific instructions or parity in tooling and process indicates a Windows-first, Windows-only bias.
Recommendations
- Explicitly state whether the described Azure Backup features and processes support SQL Server on Linux, and clarify any limitations.
- Provide parallel instructions and examples for SQL Server Always On AGs running on Linux VMs, including registration, backup, and failover processes.
- Mention and document any differences in backup extension installation, configuration, and management for Linux-based SQL Server nodes.
- Include troubleshooting steps and error codes relevant to Linux environments.
- If Linux is not supported, 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-support-matrix-mars-agent.md
...n//articles/backup/backup-support-matrix-mars-agent.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation for the MARS agent is exclusively focused on Windows environments. All examples, supported operating systems, tools, and procedures are Windows-specific, with no mention of Linux or cross-platform support. Windows tools and patterns (such as registry edits, MMC, PowerShell, DISM.exe, and NTFS) are referenced throughout, and there are no Linux equivalents or alternatives provided. The documentation assumes a Windows-only context, omitting any guidance for Linux users.
Recommendations
- Clearly state at the beginning whether Linux is supported or not. If not, explicitly mention that the MARS agent is Windows-only and suggest alternative backup solutions for Linux environments (such as Azure Backup for Linux VMs or third-party tools).
- If partial or future Linux support is planned, provide a roadmap or guidance for Linux users.
- Where possible, provide parity in documentation by including Linux equivalents for backup, restore, and configuration tasks, or link to relevant Azure Backup documentation for Linux.
- Avoid referencing only Windows tools and patterns (such as registry edits, MMC, PowerShell) without mentioning that these are not applicable to Linux, and suggest analogous Linux tools or commands if relevant.
- Add a comparison table or section that summarizes backup options for both Windows and Linux environments, helping users quickly identify the right solution for their OS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-support-matrix.md
...cs/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, tools, and features. Windows-specific tools (MARS agent, DPM, MABS) are discussed in detail, with Linux support often described as 'not supported' or limited to VM-level backups. Linux backup options are less comprehensive, and Linux examples or parity features are missing or require custom scripting, while Windows scenarios are described as default or primary. Tables and feature lists frequently mention Windows first, and some features (like direct on-premises backup) are only available for Windows.
Recommendations
- Provide Linux-specific backup examples and scenarios alongside Windows examples, especially for on-premises and VM backups.
- Clearly indicate Linux support status in all relevant tables, not just as 'not supported', but with guidance or alternatives where possible.
- Where Windows tools (MARS, DPM, MABS) are mentioned, include Linux equivalents or explain the lack thereof and suggest best practices for Linux users.
- Avoid listing Windows scenarios/features first by default; alternate order or group by OS for parity.
- Expand documentation on using custom scripts for Linux app-consistent backups, including links to sample scripts and best practices.
- Highlight any roadmap or ongoing work to improve Linux backup support, if applicable, to set expectations for parity.