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 151-175 of 520 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-about-mars.md ...s/blob/main/articles/backup/backup-azure-about-mars.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation exclusively describes backup and recovery scenarios for Windows systems, referencing Windows-specific features (e.g., VSS, USN change journal, System State) and does not mention Linux support or provide Linux examples. All instructions, terminology, and supported scenarios are Windows-centric, with no parity or guidance for Linux environments.
Recommendations
  • Clearly state in the introduction and support matrix whether the MARS agent supports Linux systems. If not, provide alternative solutions or links for Linux backup to Azure.
  • If Linux support is available or planned, add equivalent Linux examples, instructions, and supported scenario tables.
  • Avoid using only Windows-specific terminology (e.g., VSS, System State) without clarifying their scope or providing Linux equivalents.
  • Ensure that any diagrams, screenshots, or walkthroughs include Linux where applicable, or explicitly note platform limitations.
  • Mention and link to Azure backup solutions for Linux (such as Azure Backup Server, Azure VM backup for Linux, or third-party options) to guide Linux users.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-alternate-dpm-server-troubleshoot.md ...ckup/backup-azure-alternate-dpm-server-troubleshoot.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure Backup Server and Data Protection Manager (DPM), which are Windows-based tools. There are no examples or troubleshooting steps for Linux-based backup solutions, and the language assumes the use of Windows Server or Windows Client. No Linux equivalents or cross-platform considerations are mentioned.
Recommendations
  • Include troubleshooting steps or references for Linux-based backup solutions, such as Azure Backup integration with Linux servers.
  • Clarify in the introduction that the guidance is specific to Windows environments, and provide links to Linux-specific documentation if available.
  • Add examples or notes for users managing backups on Linux systems, or explicitly state if Azure Backup Server does not support Linux.
  • Ensure parity by mentioning Linux tools and workflows where applicable, or by providing a comparison table of supported platforms.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-alternate-dpm-server.md ...n/articles/backup/backup-azure-alternate-dpm-server.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes recovery using Azure Backup Server and Data Protection Manager (DPM), which are Windows-only tools. All instructions and screenshots reference the Windows GUI and workflow, with no mention of Linux equivalents, CLI options, or cross-platform alternatives. There are no Linux-specific examples or guidance, and the documentation assumes a Windows environment throughout.
Recommendations
  • Add information about recovering data from Linux servers or workloads, if supported by Azure Backup.
  • Include CLI-based recovery steps (e.g., using Azure CLI, az backup commands, or PowerShell Core on Linux) if available.
  • Explicitly state platform limitations (e.g., 'Azure Backup Server and DPM are Windows-only; for Linux workloads, use XYZ method').
  • Provide parity in examples and screenshots for Linux environments, or link to relevant Linux recovery documentation.
  • Mention and link to alternative backup and recovery solutions for Linux, such as Azure Backup for Linux VMs, and provide guidance for those scenarios.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-cloud-as-tape.md ...n/articles/backup/backup-azure-backup-cloud-as-tape.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing System Center Data Protection Manager (DPM), a Windows-only tool, and linking to a 'backup-windows-with-mars-agent' guide as the next step. There are no Linux-specific tools, examples, or instructions provided, nor are Linux backup scenarios mentioned. The documentation implicitly assumes a Windows environment and does not address Linux users or their needs.
Recommendations
  • Include equivalent Linux backup solutions (e.g., Azure Backup integration with Linux servers, or mention of Azure Backup Server support for Linux).
  • Provide Linux-specific examples and screenshots for backup and retention policy configuration.
  • Add links to documentation for backing up Linux machines with Azure Backup.
  • Avoid referencing only Windows tools (like DPM) without mentioning Linux alternatives or clarifying platform support.
  • Ensure that 'Next steps' includes guides for both Windows and Linux users.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-exchange-server.md ...articles/backup/backup-azure-backup-exchange-server.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes backup procedures using System Center DPM, a Windows-only tool, and focuses on Microsoft Exchange (also Windows-only). All examples, instructions, and screenshots reference Windows interfaces and tools (e.g., DPM Administrator Console, Eseutil.exe, PowerShell). There are no Linux equivalents, alternative cross-platform tools, or even mentions of Linux-based Exchange alternatives. The documentation assumes a Windows environment throughout.
Recommendations
  • Clearly state early in the documentation that the described solution is Windows-only and not applicable to Linux environments.
  • If possible, provide references or links to cross-platform or Linux-compatible backup solutions for email servers (e.g., using Azure Backup with Linux servers, or alternatives for backing up Postfix/Dovecot).
  • Include a comparison table or section outlining the lack of Linux support and suggesting next steps for Linux users.
  • Avoid implying that the solution is generally applicable to all environments; specify the Windows focus in the title and introduction.
  • If any part of Azure Backup supports Linux workloads, add a 'See also' or 'Related content' section with links to those resources.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-import-export.md ...n/articles/backup/backup-azure-backup-import-export.md
High Priority View Details →
Scanned: 2025-12-29 18:00
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 instructions, prerequisites, and tools (such as the MARS agent, AzureOfflineBackupDiskPrep utility, and Azure PowerShell) are Windows-specific. There are no examples or guidance for Linux systems, nor is there mention of Linux compatibility or alternatives. The workflow assumes use of Windows-only tools and patterns, such as elevated command prompts, BitLocker, and Internet Explorer/Microsoft Edge.
Recommendations
  • Clearly state in the prerequisites and introduction whether Linux is supported or not. If not, provide a link to Linux-compatible workflows or alternatives.
  • If Linux is supported, add parallel instructions and examples for Linux systems, including command-line equivalents (e.g., Bash scripts, az CLI usage) and supported disk encryption methods.
  • Mention Linux tools and patterns (such as mounting disks, using Linux-compatible browsers, or alternative disk preparation utilities) where appropriate.
  • If the MARS agent and AzureOfflineBackupDiskPrep utility are Windows-only, explicitly call this out and provide guidance for Linux users (e.g., using Azure Data Box or other supported methods).
  • Avoid referencing Windows tools (e.g., PowerShell, BitLocker, Internet Explorer) exclusively; when possible, provide cross-platform alternatives or note platform limitations.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-server-import-export.md ...les/backup/backup-azure-backup-server-import-export.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows environments. All instructions, tools, and workflows are centered around Windows-based products (DPM, MABS), and utilities (AzureOfflineBackupDiskPrep.exe), with prerequisites such as Microsoft Edge/Internet Explorer, BitLocker, and Azure PowerShell. There are no Linux equivalents, examples, or mentions of cross-platform alternatives. The documentation assumes the use of Windows servers and clients throughout.
Recommendations
  • Provide explicit statements about Linux support or lack thereof for DPM/MABS offline seeding workflows.
  • If Linux is not supported, clarify this early in the documentation to set expectations.
  • If any steps can be performed on Linux (e.g., preparing disks, copying data), provide equivalent Linux commands and tools (such as using dd, cryptsetup for encryption, or Azure CLI).
  • Mention and link to any Linux-compatible backup solutions for Azure, if available.
  • If the AzureOfflineBackupDiskPrep utility is Windows-only, suggest or develop a cross-platform version or script.
  • Avoid requiring Windows-specific browsers (Edge/IE11) and instead recommend cross-platform browsers where possible.
  • Include a comparison table or section outlining OS support for the described workflow.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-sharepoint-mabs.md ...articles/backup/backup-azure-backup-sharepoint-mabs.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments. All instructions, examples, and tooling references assume Windows servers, Windows command-line tools (CMD, Registry Editor), and Windows-specific paths and permissions. There are no examples or guidance for Linux-based SharePoint deployments, nor for using Linux-native tools or patterns. The documentation does not mention Linux compatibility or alternatives, and all administrative tasks are described with Windows-centric terminology and steps.
Recommendations
  • Explicitly state platform requirements and limitations (e.g., if MABS only supports Windows-based SharePoint farms, clarify this early in the documentation).
  • If Linux support is possible, provide equivalent instructions for Linux environments, including command-line examples, file paths, and permissions.
  • Mention whether SharePoint on Linux (e.g., via containers) is supported or not, and provide guidance for such scenarios if applicable.
  • Where possible, offer cross-platform alternatives for monitoring, notifications, and backup/restore operations (e.g., using REST APIs, CLI tools, or scripts that work on Linux).
  • Add a section comparing Windows and Linux support, or explicitly state that only Windows is supported if that is the case.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-sharepoint.md ...main/articles/backup/backup-azure-backup-sharepoint.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Powershell Heavy Windows First
Summary
The documentation is heavily biased towards Windows environments. It exclusively references System Center Data Protection Manager (DPM), a Windows-only tool, and provides no mention of Linux-based backup solutions or cross-platform alternatives. The only automation example referenced is via PowerShell, and there are no Linux command-line or tool examples. All instructions and screenshots are based on Windows tools and UI, with no parity for Linux users.
Recommendations
  • Include information about cross-platform or Linux-compatible backup solutions for SharePoint, if available (e.g., Azure Backup Server on Linux, or third-party tools).
  • Provide equivalent Linux command-line examples (e.g., Bash scripts, Azure CLI) for backup and restore operations, where possible.
  • Mention and link to any Linux-based documentation or tools that can be used for similar backup scenarios.
  • If DPM is required and only available on Windows, clearly state this limitation at the beginning of the article and suggest alternatives for Linux environments.
  • Add automation examples using Azure CLI or REST API, not just PowerShell.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-sql.md ...s/blob/main/articles/backup/backup-azure-backup-sql.md
High Priority View Details →
Scanned: 2025-12-29 18:00
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. It exclusively references Data Protection Manager (DPM), a Windows-only tool, and all examples, screenshots, and instructions are based on the Windows GUI. There are no Linux equivalents or examples, and Linux-based backup tools or scenarios are not mentioned. The only automation reference is to PowerShell, further reinforcing the Windows-centric approach.
Recommendations
  • Include information about Linux-based backup solutions for SQL Server (such as Azure Backup integration with Linux servers or third-party tools).
  • Provide parallel instructions or links for backing up SQL Server on Linux to Azure, if supported.
  • Mention limitations or alternatives for users running SQL Server on Linux.
  • Add automation examples using cross-platform tools (such as Azure CLI or REST API), not just PowerShell.
  • Clarify early in the article that the documented workflow is specific to Windows/DPM, and point Linux users to relevant resources.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-data-protection-use-rest-api-create-update-postgresql-policy.md ...rotection-use-rest-api-create-update-postgresql-policy.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias primarily through repeated references to PowerShell objects as the default or primary way to conceptualize and configure backup policies. The only non-REST API tool mentioned is PowerShell, with no mention of Linux-native tools, CLI, or Bash scripting. The phrase 'default PowerShell object' is used to describe the policy structure, suggesting a Windows-centric approach. There are no Linux-specific examples, nor is there guidance for Linux users on how to perform equivalent operations outside of REST or PowerShell.
Recommendations
  • Add Azure CLI examples for creating and managing backup policies, as the CLI is cross-platform and widely used on Linux.
  • Replace or supplement references to 'default PowerShell object' with neutral or cross-platform terminology, such as 'policy definition' or 'policy JSON object'.
  • Explicitly mention that all REST API operations can be performed from any platform, and provide sample Bash/cURL commands for Linux users.
  • If scripting examples are included, provide both PowerShell and Bash/cURL equivalents.
  • Include a section or note for Linux/macOS users, clarifying supported tools and providing links to relevant cross-platform documentation.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-database-postgresql-overview.md ...es/backup/backup-azure-database-postgresql-overview.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively recommending the use of the pgAdmin GUI tool for database operations, without mentioning or providing examples for Linux-native or cross-platform command-line tools such as psql. All screenshots and workflow steps are centered around the Azure Portal and pgAdmin, which are more commonly used on Windows. There are no examples using Linux CLI tools, and the documentation does not mention or prioritize Linux or cross-platform alternatives. This can make it less accessible for Linux users or those who prefer command-line workflows.
Recommendations
  • Add equivalent examples using the psql command-line tool for tasks such as granting privileges, connecting to the database, and creating users/databases.
  • Include instructions and screenshots for performing operations via the Azure CLI (az), which is cross-platform, alongside or before GUI-based instructions.
  • Explicitly mention that pgAdmin is available on Linux and macOS, and provide installation links for those platforms.
  • Wherever possible, provide both GUI (pgAdmin/Azure Portal) and CLI (psql/Azure CLI) instructions in parallel.
  • Highlight any platform-specific differences or prerequisites for Linux users, such as firewall configuration or client installation steps.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dpm-introduction.md .../main/articles/backup/backup-azure-dpm-introduction.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented towards Windows environments. All examples, prerequisites, and instructions assume the use of Windows tools (e.g., PowerShell, .NET Framework, .exe installers) and the DPM server itself, which is a Windows-only product. There are no examples or instructions for Linux environments, and Windows tools and patterns are mentioned exclusively and before any Linux equivalents (which are absent).
Recommendations
  • Explicitly state that DPM is a Windows-only product early in the documentation to set expectations for cross-platform users.
  • If Azure Backup supports Linux workloads via other agents or methods, provide links or references to those alternatives for Linux users.
  • Where possible, mention Linux backup options (such as Azure Backup for Linux VMs or MARS agent alternatives) and link to their documentation.
  • If any steps (such as downloading vault credentials or configuring storage) are relevant to both Windows and Linux, provide parallel Linux examples or clarify platform applicability.
  • Add a section summarizing backup options for non-Windows workloads to help guide Linux administrators.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-encrypted-vm-troubleshoot.md ...icles/backup/backup-azure-encrypted-vm-troubleshoot.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary CLI example for configuring permissions, without mentioning Linux alternatives such as Azure CLI or Bash. No Linux-specific instructions or examples are provided for troubleshooting or automation, and Windows tooling (PowerShell) is mentioned before any cross-platform solutions.
Recommendations
  • Include equivalent Linux/Unix instructions using Azure CLI and Bash where PowerShell is referenced.
  • Add explicit examples for configuring Key Vault permissions and restoring VMs using Azure CLI commands.
  • Ensure troubleshooting steps and automation guidance are platform-neutral or provide both Windows and Linux options.
  • Review linked pages to confirm Linux parity in referenced step-by-step instructions.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-exchange-mabs.md ...lob/main/articles/backup/backup-azure-exchange-mabs.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows environments, specifically Microsoft Exchange Server and Azure Backup Server (MABS), which are Windows-only products. All instructions, screenshots, and tool references (such as Eseutil.exe, Ese.dll, and file paths like C:\Program Files\...) are Windows-centric. There are no examples, notes, or guidance for Linux-based Exchange alternatives or backup scenarios, nor any mention of Linux-compatible tools or commands.
Recommendations
  • Clarify early in the documentation that MABS and Exchange Server are Windows-only products, and explicitly state platform requirements.
  • If Azure Backup supports Linux workloads, provide parallel documentation or links for backing up Linux-based mail servers (e.g., Postfix, Dovecot) using Azure Backup.
  • Where possible, mention Linux equivalents for backup and recovery (such as using Azure Backup Agent for Linux or third-party tools).
  • Include a section on limitations or alternatives for Linux users, and direct them to relevant resources.
  • Avoid hardcoding Windows file paths and tools without noting platform constraints.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-manage-mars.md .../blob/main/articles/backup/backup-azure-manage-mars.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on the Microsoft Azure Recovery Services (MARS) Agent, which is a Windows-only backup solution. All instructions, screenshots, and tool references are for Windows environments (e.g., MARS console, Windows file paths, use of %ProgramFiles%, and Windows-specific antivirus configuration). There are no Linux or cross-platform examples, nor any mention of Linux equivalents or alternative approaches for non-Windows systems. This creates a strong Windows bias and excludes Linux administrators from relevant guidance.
Recommendations
  • Clearly state at the beginning of the documentation that MARS Agent is only supported on Windows, and provide links to Linux backup solutions (such as Azure Backup for Linux VMs or Azure CLI/agent-based solutions for Linux).
  • Where possible, include a comparison table or section that outlines backup and recovery options for both Windows and Linux, with links to relevant documentation for Linux.
  • If any features or workflows are available for Linux (e.g., via Azure CLI, REST API, or other agents), provide equivalent examples and instructions.
  • Avoid using Windows-specific terminology (such as %ProgramFiles%) without clarification, or provide Linux path equivalents where relevant.
  • Add a 'Linux support' or 'Cross-platform considerations' section to clarify platform limitations and direct Linux users to appropriate resources.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-monitoring-built-in-monitor.md ...les/backup/backup-azure-monitoring-built-in-monitor.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric backup tools (DPM, MABS, MARS) and linking to management guides specifically for Windows Server. There are no explicit Linux backup tool examples or instructions, and Windows tools are mentioned exclusively when discussing backup item visibility and naming conventions.
Recommendations
  • Include examples and instructions for monitoring Linux-based backup workloads, such as Azure Backup for Linux VMs or native Linux backup agents.
  • Reference Linux-compatible backup tools and workflows alongside Windows tools, ensuring parity in documentation.
  • Add links to Linux-specific management guides and clarify any differences in monitoring or notification capabilities for Linux workloads.
  • When discussing naming conventions or limitations, specify if these apply to Linux workloads or provide Linux-specific guidance if different.
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-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All examples, instructions, and tooling references are Windows-centric, including exclusive use of Windows service accounts, PowerShell scripts, Windows file paths, and SSMS (SQL Server Management Studio). There is no mention of Linux-based SQL Server VMs, nor any Linux-specific instructions or parity for backup configuration, permissions, or troubleshooting.
Recommendations
  • Add explicit support and instructions for SQL Server on Linux VMs, including any differences in extension installation, service accounts, and permissions.
  • Provide Linux command-line examples (e.g., Bash scripts, use of sqlcmd on Linux) alongside PowerShell examples.
  • Document the location of configuration files and logs for Linux-based SQL Server VMs.
  • Clarify whether the AzureBackupWindowsWorkload extension or an equivalent is available for Linux, and if not, state the limitation clearly.
  • Include troubleshooting steps and permission-setting instructions for Linux environments (e.g., using chown/chmod, systemd service accounts).
  • Ensure that all file path examples are provided in both Windows and Linux formats where applicable.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-restore-files-from-vm.md .../articles/backup/backup-azure-restore-files-from-vm.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions, tools, and troubleshooting steps are consistently presented before Linux equivalents. Windows-specific tools (e.g., registry edits, Windows Explorer, .NET requirements) are described in detail, while Linux instructions are sometimes less detailed or presented after Windows. PowerShell is referenced as a primary automation method, and some troubleshooting (e.g., registry changes) is only described for Windows. Linux examples are present but often less emphasized or detailed.
Recommendations
  • Present Linux and Windows instructions in parallel or in clearly separated, equally detailed sections, rather than always listing Windows first.
  • Provide Linux troubleshooting steps with the same level of detail as Windows (e.g., registry edits for Windows vs. config file changes for Linux).
  • Include Linux automation examples (e.g., Bash scripts or CLI commands) alongside PowerShell references.
  • Ensure that all screenshots and examples are balanced between Windows and Linux environments.
  • Mention Linux tools and patterns (e.g., file managers, mount utilities) with the same prominence as Windows tools.
  • Where possible, avoid language that implies Windows is the default or primary platform.
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-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows Only 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is exclusively focused on restoring System State for Windows Server using Azure Backup. All instructions, examples, and tools referenced (MARS agent, Windows Server Backup, wbadmin, Win RE) are specific to Windows environments. There are no references to Linux equivalents, nor any mention of how to perform similar operations on Linux servers. The documentation assumes the reader is using Windows and does not provide parity for Linux users.
Recommendations
  • Add a section or a separate article for restoring system state or equivalent on Linux servers using Azure Backup, if supported.
  • Include Linux-specific tools and commands (e.g., rsync, tar, dd, or native Linux backup/restore utilities) where applicable.
  • If Azure Backup supports Linux VM backup and restore, provide step-by-step instructions for Linux, including screenshots and command-line examples.
  • Clearly indicate at the beginning of the article that the instructions are Windows-specific, and provide links to Linux documentation if available.
  • Ensure that future documentation covers both Windows and Linux scenarios, or explicitly states platform limitations.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-restore-key-secret.md ...ain/articles/backup/backup-azure-restore-key-secret.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows and PowerShell. All command-line examples use PowerShell cmdlets, and file paths are given in Windows format (e.g., C:\ paths). There are no examples using Bash, Azure CLI, or cross-platform scripting. Even when Linux VMs are mentioned, the instructions still use PowerShell, which is not the default or most common shell on Linux. There is no guidance for users who may be working from a Linux or macOS environment.
Recommendations
  • Provide equivalent examples using Azure CLI (az commands) and Bash scripting, which are native to Linux and cross-platform environments.
  • Use platform-agnostic file paths or show both Windows and Linux path formats in examples.
  • Explicitly mention and provide steps for performing the same operations from Linux/macOS, including prerequisites such as installing Azure CLI.
  • Reorganize sections so that instructions for Linux and Windows are presented with equal prominence, or group platform-specific instructions clearly.
  • Add notes clarifying which steps are platform-specific and provide alternatives where necessary (e.g., for downloading blobs or manipulating JSON files).
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-rbac-rs-vault.md ...docs/blob/main/articles/backup/backup-rbac-rs-vault.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. It explicitly references Windows-specific backup tools (Azure Backup agent client UI, System Center Data Protection Manager UI, Azure Backup Server UI) and on-premises Windows Server/client registration, without mentioning Linux equivalents or cross-platform backup agents. Windows tools and scenarios are mentioned exclusively in several places, and there are no examples or guidance for Linux-based backup management or registration. The documentation does not provide parity for Linux server backup scenarios or mention Linux-specific tools or processes.
Recommendations
  • Include references to Linux backup agents and management tools where applicable, such as Azure Backup for Linux VMs or third-party Linux backup solutions.
  • Add examples and guidance for registering and managing backups for Linux servers, including any differences in role assignments or permissions.
  • Mention Linux equivalents alongside Windows tools (e.g., if referencing Azure Backup agent for Windows, also reference Azure Backup for Linux or other supported Linux backup mechanisms).
  • Ensure that on-premises backup scenarios cover both Windows and Linux environments, and clarify any platform-specific limitations or requirements.
  • Review tables and descriptions to explicitly state support for Linux workloads and provide links to relevant documentation for Linux backup management.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-scdpm-troubleshooting.md .../articles/backup/backup-azure-scdpm-troubleshooting.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates Windows bias by exclusively referencing Windows tools and patterns (e.g., 'net stop dpmra', NT AUTHORITY\SYSTEM, MARS agent), and does not provide any Linux-specific troubleshooting steps or examples. There are no mentions of Linux equivalents, nor are any Linux commands or environments addressed, despite the potential for cross-platform backup scenarios.
Recommendations
  • Add troubleshooting steps and examples relevant to Linux environments, if Data Protection Manager or Azure Backup Server supports Linux workloads.
  • Include Linux command-line equivalents (e.g., systemctl or service commands) alongside Windows commands like 'net stop/start'.
  • Mention Linux-specific agents, permissions, and error messages where applicable.
  • Clarify in the introduction or prerequisites if the product or documentation is Windows-only; if not, ensure Linux parity in all examples and troubleshooting steps.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-security-feature.md .../main/articles/backup/backup-azure-security-feature.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. It exclusively discusses Microsoft-centric backup tools (MABS, DPM, MARS), which are Windows-only. All examples, workflows, and troubleshooting steps reference Windows tools and interfaces, with no mention of Linux equivalents or support. There are no Linux-specific instructions, commands, or scenarios, and the documentation does not clarify Linux support or alternatives. Even PowerShell commands are referenced without Bash or Linux CLI equivalents.
Recommendations
  • Clearly state in the introduction whether Linux workloads are supported by these security features and, if not, provide links to Linux backup documentation.
  • If Linux support exists, add equivalent examples and workflows for Linux, including CLI commands (e.g., Bash, az CLI) and Linux agent usage.
  • Include troubleshooting steps and error messages relevant to Linux environments.
  • Mention Linux backup tools (such as Azure Backup for Linux, if available) alongside Windows tools, and provide parity in feature descriptions.
  • For PowerShell commands, provide equivalent Bash or shell commands where possible.
  • Add a comparison table summarizing feature availability and steps for both Windows and Linux platforms.
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-12-29 18:00
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 migration support, mentioning PowerShell before CLI, and omitting explicit Linux shell examples. The only command-line reference is to Azure CLI and PowerShell, with no Bash or Linux-specific instructions or screenshots. The portal instructions and screenshots are platform-neutral, but command-line guidance is not inclusive of Linux users.
Recommendations
  • Add explicit Bash/Linux shell examples for CLI commands, showing usage in a Linux terminal.
  • When mentioning command-line tools, list Azure CLI before PowerShell or present both together to avoid Windows-first ordering.
  • Include notes or examples for Linux users, such as installation instructions for Azure CLI on Linux and any OS-specific considerations.
  • Clarify that Azure CLI is cross-platform and provide sample commands in both Windows (PowerShell) and Linux (Bash) contexts.
  • Add screenshots or terminal output examples from Linux environments where relevant.