Backup

381
Total Pages
181
Linux-Friendly Pages
200
Pages with Bias
52.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

1604 issues found
Showing 1001-1025 of 1604 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-azure-sql-vm-rest-api.md .../main/articles/backup/restore-azure-sql-vm-rest-api.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-style file paths (e.g., C:\SQLfiles\Default.ldf), using SQL Server (primarily a Windows workload) as the example, and omitting any mention of Linux-based SQL Server VMs or Linux file path conventions. There are no examples or notes for restoring SQL Server databases on Linux VMs, and all directory path examples use Windows syntax. No Linux tools, patterns, or considerations are mentioned.
Recommendations
  • Include examples of restoring SQL Server databases on Linux-based Azure VMs, using Linux file path conventions (e.g., /var/opt/mssql/data/).
  • Add notes or sections that clarify any differences or additional steps required for SQL Server on Linux VMs.
  • Where file paths are shown (such as in alternateDirectoryPaths), provide both Windows and Linux examples side by side.
  • Explicitly state whether the documented process is supported and tested for both Windows and Linux SQL Server VMs, and highlight any OS-specific limitations.
  • If PowerShell or Windows-specific tooling is referenced elsewhere, ensure parity by including Bash/CLI or Linux-native alternatives.
GitHub Create Pull Request
Backup 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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
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 standard policy support, mentioning PowerShell before CLI, and not providing explicit Linux or cross-platform command-line examples. The only non-portal automation path mentioned is through Azure CLI and PowerShell, but no Linux shell or bash-specific guidance is given. The documentation also lacks screenshots or instructions for Linux environments, focusing exclusively on the Azure Portal UI (which is platform-agnostic but often associated with Windows workflows in Azure documentation).
Recommendations
  • Provide explicit Linux/bash command-line examples for migration operations, including sample az CLI commands with Linux shell syntax.
  • When referencing automation tools, mention CLI before PowerShell or present both together to avoid Windows-first ordering.
  • Include notes or links to Linux-specific guidance or troubleshooting, especially for users managing Azure from Linux environments.
  • Add clarification that the Azure CLI commands work cross-platform (Windows, Linux, macOS), and provide sample usage in a Linux terminal context.
  • If possible, include screenshots or terminal output from Linux environments to reinforce parity.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides only PowerShell-based (Windows-centric) examples for configuring snapshot retention, with no equivalent CLI or Linux-native instructions. The only automation example is in PowerShell, and there is no mention of Azure CLI, Bash, or cross-platform scripting options. This may lead Linux or cross-platform administrators to feel unsupported or unclear about how to perform these tasks without Windows tools.
Recommendations
  • Add equivalent Azure CLI examples for configuring snapshot retention and other operations, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash script examples or references for common tasks, ensuring parity with PowerShell instructions.
  • When presenting automation or scripting options, list Azure CLI (or Bash) before or alongside PowerShell to avoid the impression of Windows-first bias.
  • Explicitly mention that all features are available regardless of the OS used for management, and provide links to relevant cross-platform tooling documentation.
  • Consider a section or note highlighting cross-platform management options for Azure Backup, including links to both PowerShell and CLI documentation.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-restore-system-state.md ...n/articles/backup/backup-azure-restore-system-state.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
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, screenshots, and command-line examples are specific to Windows environments (e.g., Windows Server Backup, wbadmin, MARS agent, Windows Recovery Environment). There are no references to Linux systems, Linux tools, or cross-platform considerations. The documentation assumes the reader is operating in a Windows-only context.
Recommendations
  • If Azure Backup supports similar system state or configuration backup/restore for Linux servers, add equivalent sections and walkthroughs for Linux, including relevant tools (e.g., rsync, tar, Timeshift, or native Azure Linux backup agents).
  • If Linux system state backup is not supported, clearly state this limitation at the beginning of the article to set expectations for cross-platform users.
  • Where possible, provide parity in troubleshooting and recovery guidance for Linux environments, or link to relevant Linux documentation.
  • Consider restructuring the documentation or titling it more explicitly as 'Restore System State to a Windows Server (Windows Only)' to avoid confusion for non-Windows users.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes backup and recovery using Azure Backup Server, which is a Windows-based tool, and all instructions reference a GUI workflow typical of Windows environments. There are no examples or guidance for Linux-based VMs, command-line workflows, or cross-platform backup tools. The documentation assumes the use of Windows patterns and tools throughout, with no mention of Linux equivalents or considerations.
Recommendations
  • Add explicit guidance for backing up and recovering files from Linux-based Azure Stack VMs, including any supported tools or agent installation steps.
  • Include CLI-based examples (e.g., using Azure CLI, Bash scripts, or relevant Linux backup agents) alongside or in place of GUI walkthroughs.
  • Mention any limitations or requirements for Linux VM backup and recovery with Azure Backup Server, and provide links to Linux-specific documentation if available.
  • If Azure Backup Server does not support Linux VMs, clearly state this and suggest alternative backup strategies or tools for Linux workloads.
  • Ensure parity in documentation structure and detail for both Windows and Linux environments, including troubleshooting and recovery scenarios.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-security-feature-cloud.md ...articles/backup/backup-azure-security-feature-cloud.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for command-line operations, referencing Windows-centric tools and cmdlets, and omitting any Linux-native CLI (such as Azure CLI/bash) examples. The structure and order of examples prioritize PowerShell after the portal, with no mention of Linux shell usage or cross-platform scripting approaches. This may hinder accessibility for Linux users or those preferring non-Windows environments.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all command-line instructions, especially for enabling/disabling soft delete and managing backup items.
  • Explicitly mention that PowerShell examples are cross-platform only if true, or clarify if they require Windows.
  • Include bash/shell script snippets where appropriate to demonstrate parity for Linux users.
  • Reorder or parallelize the presentation of PowerShell and Azure CLI examples to avoid implicit prioritization of Windows tools.
  • Reference Linux-compatible tooling and workflows in the prerequisites and throughout the documentation.
  • Add a note or section addressing cross-platform support and best practices for both Windows and Linux administrators.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/monitoring-and-alerts-overview.md ...main/articles/backup/monitoring-and-alerts-overview.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently listing PowerShell as the primary non-portal client, mentioning it before Azure CLI and REST API. The term 'PowerShell' is highlighted in multiple places, and there are references to Windows-centric backup agents and tools (e.g., Azure Backup Agent, DPM, Azure Backup Server) without equivalent Linux-focused examples or tools. There are no explicit Linux command-line examples or references to Linux-native tooling, and the documentation does not provide parity in guidance for Linux administrators.
Recommendations
  • Provide explicit Linux/Unix examples using Azure CLI and Bash scripts alongside PowerShell examples.
  • Mention Azure CLI before or alongside PowerShell when listing non-portal clients to avoid the impression of Windows-first tooling.
  • Include references to Linux-supported backup agents or clarify cross-platform compatibility where relevant.
  • Add sample monitoring and alerting workflows tailored for Linux environments, such as integrating with Linux-native notification systems or scripts.
  • Ensure that documentation for custom dashboards and automation includes both PowerShell and CLI/Bash script examples.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-sql-database.md ...blob/main/articles/backup/backup-azure-sql-database.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. All examples, instructions, and screenshots assume SQL Server is running on Windows. Only Windows authentication, Windows service accounts (NT SERVICE, NT AUTHORITY), Windows file paths, and Windows tools (SSMS, PowerShell, Task Manager, SMB shares) are referenced. There are no instructions, examples, or notes for running SQL Server on Linux VMs, nor for using Linux-native tools or authentication methods.
Recommendations
  • Add explicit guidance and examples for SQL Server on Linux VMs, including any differences in agent installation, permissions, and backup configuration.
  • Include Linux command-line equivalents (e.g., using sqlcmd, systemctl, chown/chmod for permissions) alongside PowerShell and SSMS instructions.
  • Document how to configure service accounts or required permissions on Linux (e.g., using system users or sudoers) instead of only referencing Windows service accounts.
  • Provide Linux file path examples and instructions for configuring local backup folders and permissions.
  • Clarify any limitations or differences in Azure Backup support for SQL Server on Linux, and link to relevant Linux-specific documentation if available.
  • Ensure that REST API and portal instructions are platform-agnostic or note any platform-specific steps.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-system-state-and-bmr.md ...in/articles/backup/backup-mabs-system-state-and-bmr.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased 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 workflows, or equivalent Linux tools. The documentation assumes the reader is operating in a Windows-only environment, with no guidance for Linux systems or cross-platform scenarios.
Recommendations
  • Clearly state at the beginning 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, include equivalent Linux backup and recovery workflows, referencing tools such as rsync, tar, dd, or native Linux backup solutions.
  • Provide Linux command-line examples alongside PowerShell and Windows Server Backup commands.
  • Mention Linux-specific prerequisites, limitations, and supported distributions if applicable.
  • Ensure parity in the documentation structure: for every Windows-specific section, provide a Linux equivalent or explicitly note if not supported.
  • If Azure Backup Server is Windows-only for system state/BMR, add a clear note and suggest alternative Azure/Linux backup solutions.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-install-azure-stack.md ...ain/articles/backup/backup-mabs-install-azure-stack.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. All instructions, prerequisites, and examples assume the use of Windows Server (specifically Windows Server 2019/2022), Windows file paths (C:\, D:\), Windows domain membership, and Windows-specific tools (e.g., PowerShell cmdlets, Windows Update, .NET Framework). There are no references to Linux-based installations, tools, or alternative workflows, and no mention of Linux compatibility or support.
Recommendations
  • Clearly state at the beginning whether Azure Backup Server supports only Windows or if Linux is also supported. If Linux is not supported, explicitly mention this to set expectations.
  • If Linux is supported, provide equivalent installation and configuration instructions for Linux environments, including prerequisites, file paths, and commands.
  • Include Linux-based examples for network connectivity checks, such as using curl, wget, or other Linux-native tools, in addition to the PowerShell cmdlet.
  • Mention Linux equivalents for domain joining (e.g., joining to Active Directory via realmd/sssd) if applicable.
  • Reference Linux-compatible backup agents or tools if Azure Backup Server can protect Linux workloads, and provide links to relevant documentation.
  • Avoid using only Windows terminology (e.g., C:\, D:\, Windows Update) or provide Linux alternatives where possible.
  • If the product is Windows-only, consider providing guidance for Linux workload protection using other Azure Backup solutions.
GitHub Create Pull Request
Backup 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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page for Azure Backup Server v4 demonstrates a strong Windows bias. Windows workloads, tools, and patterns are presented first and in detail, while Linux support is minimal and only described in the context of being a guest VM on Windows-based hypervisors. There are no Linux-specific backup scenarios, examples, or tooling mentioned. Windows-specific technologies (e.g., NTFS, VSS, system state, bare metal recovery) and requirements are referenced throughout, with little to no equivalent Linux guidance.
Recommendations
  • Provide explicit Linux backup scenarios, including agent-based backup for native Linux workloads (not just as VMs on Windows hosts).
  • Include Linux-specific examples and workflows, such as file-level recovery for Linux VMs, supported file systems, and backup/restore procedures.
  • Mention Linux tools and patterns (e.g., integration with LVM snapshots, ext4/xfs support, Linux-specific restore options) where relevant.
  • Balance the order of presentation: introduce Linux and Windows support in parallel where possible, rather than always listing Windows first.
  • Clarify any limitations or differences in Linux support (e.g., snapshot consistency, supported distributions) in the same detail as for Windows.
  • If PowerShell or Windows-specific tools are referenced, provide equivalent Linux command-line or scripting examples where applicable.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily focuses on using the Azure portal for backup operations and only briefly mentions automation via PowerShell and CLI, with PowerShell listed first. There are no explicit Linux-specific examples or references to Linux tools or shell environments. The 'Next steps' section lists PowerShell before CLI, and there is no mention of Bash, Linux shell, or cross-platform scripting considerations. This ordering and lack of Linux-specific guidance may suggest a Windows-first or PowerShell-heavy bias.
Recommendations
  • When mentioning automation or scripting, list Azure CLI before or alongside PowerShell to reflect cross-platform parity.
  • Include explicit Bash/Linux shell examples or references, especially in automation contexts.
  • Clarify that both PowerShell and CLI are cross-platform, and provide links or notes for Linux/macOS users.
  • Add a section or callout for Linux administrators, highlighting any platform-specific considerations or best practices.
  • Ensure that all referenced scripts or templates are available in both PowerShell and Bash/CLI formats.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-system-state-troubleshoot.md ...icles/backup/backup-azure-system-state-troubleshoot.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is exclusively focused on Windows environments, with all examples, tools, and troubleshooting steps tailored to Windows servers. Only Windows tools (PowerShell, Server Manager, wbadmin, Windows Server Backup) are mentioned, and there are no references or examples for Linux systems or their equivalents. The structure and language assume a Windows-only context, and Linux users are not addressed.
Recommendations
  • If System State Backup is not supported on Linux, explicitly state this early in the documentation to set user expectations.
  • If similar backup or troubleshooting functionality exists for Linux, provide parallel sections or links to Linux-specific documentation.
  • Where possible, mention cross-platform tools or alternatives, or clarify the scope is strictly for Windows.
  • Add a comparison table or note outlining differences in backup approaches between Windows and Linux environments, if relevant.
  • Ensure future documentation on backup and recovery covers both Windows and Linux scenarios, or clearly separates them.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-all-files-volume-mars.md .../main/articles/backup/restore-all-files-volume-mars.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows environments. All instructions, screenshots, and terminology are specific to Windows (e.g., 'Microsoft Azure Backup' snap-in, references to Windows OS versions, and Windows-style file paths). There are no examples, instructions, or even mentions of Linux or cross-platform usage, and the MARS Agent is presented as a Windows-only tool.
Recommendations
  • Explicitly state in the introduction whether the MARS Agent supports Linux, and if not, provide links to equivalent Linux backup/restore documentation.
  • If Linux is supported, add parallel instructions and screenshots for Linux environments, including command-line examples (e.g., Bash) and Linux-native tools.
  • Avoid Windows-specific terminology where possible, or provide Linux equivalents alongside (e.g., refer to 'machines' or 'servers' rather than only Windows computers).
  • Include a section or note clarifying platform support and guiding non-Windows users to appropriate resources.
  • If the product is Windows-only, make this clear early in the documentation to set expectations and avoid confusion.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments. All examples, tools, and procedures assume a Windows Server context, including the use of Windows command prompts, Windows-specific tools (like ConfigureSharePoint.exe, Registry Editor, and CMD commands), and Windows filesystem paths. There is no mention of Linux support, nor are there any examples or guidance for Linux-based environments. The documentation assumes the use of Windows authentication and permissions models, and all screenshots and UI references are for Windows-only applications.
Recommendations
  • Explicitly state whether Linux-based SharePoint deployments are supported or not. If not, clarify this early in the documentation.
  • If Linux is supported, provide parallel instructions for Linux environments, including command-line examples, file paths, and permission settings.
  • Include information about cross-platform compatibility for MABS and SharePoint, or provide links to Linux-specific backup solutions if MABS is Windows-only.
  • Avoid assuming Windows-only tools and patterns; where possible, mention equivalent Linux tools or note their absence.
  • Add a section on prerequisites and limitations that clearly addresses OS support and any platform-specific constraints.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-during-vm-creation.md ...blob/main/articles/backup/backup-during-vm-creation.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows resources and examples over Linux. In the 'Deploy a protected VM using a Resource Manager template' section, only a Windows VM template is linked, with no equivalent Linux example. Additionally, PowerShell is referenced for automation, but there is no mention of CLI or Bash alternatives. While both Windows and Linux quick-create links are provided in step 3, subsequent examples and automation guidance focus on Windows or Windows-centric tools.
Recommendations
  • Provide equivalent Linux Resource Manager template links for deploying and backing up Linux VMs.
  • Include Azure CLI and Bash script examples alongside PowerShell for automation tasks, such as configuring the Azure Backup resource group.
  • Ensure that all automation and scripting references include both Windows and Linux approaches, or clearly indicate cross-platform options.
  • When listing instructions or examples, alternate the order or present Windows and Linux options side by side to avoid 'windows_first' bias.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-bicep-file.md ...lob/main/articles/backup/quick-backup-vm-bicep-file.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All deployment and management instructions are provided exclusively using Azure PowerShell, with no Azure CLI or Bash examples. The Bicep template provisions only Windows VMs, and the allowed OS versions are all Windows Server variants. There is no mention of Linux VM deployment, nor are there instructions for Linux users or cross-platform tooling. The clean-up and backup monitoring steps also reference only PowerShell cmdlets.
Recommendations
  • Add Azure CLI/Bash examples for deploying the Bicep template, including Cloud Shell Bash instructions.
  • Provide a Bicep template or parameterization for deploying Linux VMs (e.g., Ubuntu, CentOS) alongside or instead of Windows.
  • Include Linux VM OS options in the Bicep template's allowed values and document how to select them.
  • Offer clean-up and backup management instructions using Azure CLI commands, not just PowerShell.
  • Rephrase instructions to be platform-neutral where possible, and mention both Windows and Linux workflows.
  • Ensure links to further reading or tutorials include Linux/CLI options, not just PowerShell.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, specifically referencing Microsoft Azure Backup Server (MABS), which is a Windows-only tool. All instructions, terminology, and screenshots are based on the Windows GUI and Windows-specific concepts (e.g., NTAuthority\System, MMC-style wizards, 'blades', and right-click context menus). There are no examples, instructions, or even mentions of Linux-based SQL Server deployments or backup workflows, nor are any Linux command-line or tool alternatives provided.
Recommendations
  • Explicitly state that MABS is a Windows-only solution and clarify support limitations for Linux-based SQL Server deployments.
  • If Azure Backup supports Linux SQL Server (even partially), provide equivalent instructions, examples, and screenshots for Linux environments, including command-line (bash) workflows.
  • Mention and link to any Azure-native or cross-platform backup solutions that support Linux SQL Server, or clarify if none exist.
  • Where possible, use neutral terminology (e.g., 'system account' instead of 'NTAuthority\System') and provide Linux equivalents (e.g., 'root' or relevant service accounts).
  • Add a section or note addressing Linux users, outlining their options or limitations for SQL Server backup on Azure Stack.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-automation.md ...blob/main/articles/backup/backup-support-automation.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation consistently lists PowerShell as the first automation method, with extensive PowerShell support and example links for nearly every operation. PowerShell is a Windows-centric tool, and its prominence throughout the support matrix (often before CLI or REST) suggests a Windows-first approach. While Azure CLI is also supported (and cross-platform), the documentation does not highlight Linux-native scripting or tools, and there are no bash/shell script examples or explicit Linux guidance. The focus on PowerShell and the absence of Linux-specific automation patterns or examples indicate a bias toward Windows environments.
Recommendations
  • Alternate the order of PowerShell and CLI columns or list CLI first in some tables to avoid implicit prioritization of Windows tools.
  • Add explicit bash/shell script examples for common automation tasks, especially where CLI is supported, to demonstrate Linux parity.
  • Include a section or callout on cross-platform automation, highlighting how Linux users can accomplish the same tasks using Azure CLI, REST, or scripting.
  • Where PowerShell is referenced, clarify that Azure CLI is fully supported on Linux and provide direct links to Linux-specific documentation or tutorials.
  • Consider adding a 'Linux automation' or 'Cross-platform automation' row or column to the support matrix to make Linux support more visible.
  • Review example links to ensure they include both PowerShell and CLI (bash) tabs or code blocks, not just PowerShell.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix-mars-agent.md ...in/articles/backup/backup-support-matrix-mars-agent.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
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, and tooling references are Windows-specific, with no mention of Linux or cross-platform support. Windows tools and patterns (such as registry edits, MMC, PowerShell, DISM.exe) are referenced throughout, and there are no Linux equivalents or guidance. The documentation assumes the reader is using Windows, and Linux is not addressed at all.
Recommendations
  • Clearly state early in the documentation that the MARS agent is only supported on Windows, and provide a reference to Azure Backup solutions for Linux if available.
  • If Linux is not supported, add a section explaining alternative backup solutions for Linux workloads in Azure (such as Azure Backup for Linux VMs or third-party solutions).
  • Where Windows tools or patterns are mentioned (e.g., registry edits, PowerShell, MMC), clarify that these are not applicable to Linux and provide equivalent Linux instructions or explicitly state that no Linux support exists.
  • Consider adding a comparison table or FAQ addressing backup agent support for both Windows and Linux, to help cross-platform administrators quickly understand their options.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/transport-layer-security.md .../blob/main/articles/backup/transport-layer-security.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page is heavily focused on Windows environments, providing only Windows-specific instructions (such as registry edits and KB articles) and omitting any guidance for Linux-based systems. All examples, troubleshooting, and configuration steps are tailored to Windows, with no mention of Linux equivalents or cross-platform considerations. References and links are also Windows-centric.
Recommendations
  • Add a dedicated section for enabling and verifying TLS 1.2 on Linux systems, including common distributions (e.g., Ubuntu, CentOS) and relevant configuration files (such as OpenSSL or system-wide crypto policies).
  • Provide Linux command-line examples (e.g., using openssl, update-alternatives, or editing /etc/ssl/openssl.cnf) for checking and enforcing TLS 1.2 support.
  • Include troubleshooting steps and error messages relevant to Linux environments, such as logs or common misconfigurations.
  • Reference Linux-specific documentation and best practices for TLS configuration in the 'Additional resources' section.
  • Clarify in the introduction or prerequisites which operating systems the instructions apply to, and explicitly state if Linux is not supported or requires different steps.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation assumes SQL Server is running on Windows VMs and does not mention or provide examples for Linux-based SQL Server deployments. There is no discussion of Linux-specific considerations, tools, or commands, and the backup extension and registration workflows are described in a way that presumes a Windows environment. The absence of Linux parity is notable given that SQL Server is supported on Linux.
Recommendations
  • Explicitly state whether the described procedures and Azure Backup support apply to SQL Server on Linux VMs as well as Windows VMs.
  • If Linux is supported, add Linux-specific instructions for registering AG nodes, installing the workload backup extension, and handling failover scenarios.
  • Include examples or notes about any differences in backup workflows, error codes, or limitations for SQL Server AGs on Linux.
  • Mention any Linux-specific prerequisites, such as required packages, permissions, or service management commands.
  • If Azure Backup does not support SQL Server AGs on Linux, clearly state this limitation early in the documentation.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix-iaas.md ...lob/main/articles/backup/backup-support-matrix-iaas.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows-first bias in both structure and content. Windows scenarios, tools, and agents (such as MARS, DPM, MABS, and PowerShell) are described in detail and often appear before or instead of Linux equivalents. Linux support is frequently described in terms of limitations or as 'not supported' for features available to Windows. Examples and tool references (e.g., PowerShell for restore, MARS agent) are Windows-centric, with minimal or no equivalent Linux command-line or tool guidance. Linux-specific backup scenarios are less detailed, and advanced features (like file-level restore, agent-based backup with MARS/DPM/MABS) are not available or not documented for Linux.
Recommendations
  • Provide Linux CLI (az CLI, Bash) examples alongside or before PowerShell examples for all backup and restore operations.
  • Include Linux-specific guidance and parity for agent-based backup and restore, or clearly state roadmap/alternatives if not supported.
  • Where features are Windows-only (e.g., MARS agent, DPM/MABS integration), offer Linux alternatives or workarounds, or explain the technical limitations.
  • Document Linux backup/restore scenarios with the same level of detail as Windows, including step-by-step instructions and troubleshooting.
  • Highlight Linux-specific best practices, supported distributions, and scripting options (e.g., using custom scripts for app-consistent backups) more prominently.
  • Avoid presenting Windows tools and workflows (e.g., PowerShell, Windows agents) as the default or only option; always mention Linux options in parallel where possible.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/guidance-best-practices.md ...s/blob/main/articles/backup/guidance-best-practices.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-centric tools (such as the MARS agent) for automation and hybrid backup scenarios, while not providing equivalent Linux or cross-platform examples. There is a lack of explicit Linux command-line (Bash/CLI) examples or references to Linux-native backup tools and patterns, especially in hybrid and automation contexts. The documentation assumes or highlights Windows/PowerShell workflows and tools, with Linux scenarios either omitted or not given parity.
Recommendations
  • Include explicit Linux/Bash/Azure CLI examples alongside PowerShell for automation and scripting tasks.
  • When referencing the MARS agent (which is Windows-only), clarify Linux alternatives (such as Azure Backup Server, or native Linux agent support) and provide guidance for Linux workloads.
  • Ensure hybrid backup sections mention both Windows and Linux on-premises scenarios, with clear instructions or links for Linux users.
  • Where PowerShell is mentioned for automation (e.g., auto-retry of failed jobs), also provide Azure CLI or Bash script equivalents.
  • Audit all examples and tool mentions to ensure Linux administrators can follow the guidance without needing to translate from Windows-centric instructions.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is exclusively focused on installing and using the Microsoft Azure Recovery Services (MARS) agent for Windows environments. All instructions, examples, and references are specific to Windows operating systems, including references to Windows-specific installers (.exe), wizards, and tools. There is no mention of Linux support, alternatives, or parity, and Linux users are not addressed at all.
Recommendations
  • Clearly state in the introduction and prerequisites whether the MARS agent is supported on Linux. If not, provide links to Linux backup solutions (such as Azure Backup for Linux or third-party options).
  • If Linux support is available or planned, add equivalent installation and usage instructions for Linux systems, including command-line examples (bash, shell scripts) and package management details.
  • Include a comparison table or section outlining backup options for both Windows and Linux, helping users choose the correct tool for their platform.
  • Avoid Windows-centric language such as only referencing .exe installers, Windows wizards, or Windows-specific settings without mentioning Linux equivalents or alternatives.
  • If the product is Windows-only by design, make this explicit at the top of the documentation to set expectations for cross-platform users.
GitHub Create Pull Request
← Previous Page 41 of 65 Next →