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 626-650 of 1604 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-restore-vms.md ...b/main/articles/backup/backup-azure-arm-restore-vms.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: Windows-specific examples and links are provided before Linux equivalents (e.g., references to Windows custom images, generalized VMs, and availability sets), PowerShell is frequently mentioned as the method for VM creation and restoration, and Windows tools and patterns (such as bcdedit, netdom, and RDP) are used in troubleshooting and post-restore steps. Linux-specific guidance is minimal, with only brief mentions (e.g., cloud-init password reset) and no detailed Linux CLI or SSH-based examples. There are also links and examples that are Windows-centric, with Linux alternatives either omitted or relegated to notes.
Recommendations
  • Provide Linux-specific examples and links alongside Windows ones (e.g., show how to restore and configure Linux VMs, including SSH key setup, cloud-init, and Linux agent installation).
  • Include Azure CLI and Bash examples for VM creation, disk attachment, and network configuration, not just PowerShell.
  • Reference Linux documentation pages for custom images, generalized VMs, and availability sets, and ensure parity in guidance.
  • Add troubleshooting steps for common Linux restore issues, such as fixing bootloaders, resetting SSH keys/passwords, and agent recovery.
  • Ensure that all scenarios (e.g., restoring with special network configurations, domain controllers, SQL VMs) have Linux equivalents or explicitly state limitations.
  • When mentioning tools (e.g., bcdedit, netdom), provide Linux alternatives (e.g., grub, usermod, systemctl) where applicable.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All instructions, prerequisites, and tooling are centered around Windows environments: the MARS agent is only available for Windows, all examples reference Windows Server or client, and the required utilities (AzureOfflineBackupDiskPrep) and workflows are Windows-specific. Prerequisites include Windows-only browsers (Edge/IE11), and Azure PowerShell is required, with no mention of Bash, Linux, or cross-platform alternatives. There are no Linux examples or guidance for non-Windows environments.
Recommendations
  • Explicitly state Windows-only support for MARS and offline seeding, and clarify if Linux is unsupported.
  • If Linux support is possible, provide equivalent instructions for Linux environments, including compatible tools/utilities.
  • Offer cross-platform alternatives for Azure PowerShell (e.g., Azure CLI) and browser requirements.
  • Add a section addressing Linux users, including any limitations, workarounds, or roadmap for parity.
  • Where possible, use generic terminology (e.g., 'operating system' instead of 'Windows Server') and avoid assuming Windows as the default platform.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
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 workflows assume the use of Windows servers (DPM/MABS), Windows-only utilities (AzureOfflineBackupDiskPrep.exe), and prerequisites such as Microsoft Edge/Internet Explorer and BitLocker. Azure PowerShell is referenced as a requirement, but no Linux equivalents or cross-platform alternatives are mentioned. There are no instructions or examples for performing offline seeding from Linux systems, nor is there any discussion of Linux backup tools or workflows.
Recommendations
  • Clarify platform support: Explicitly state whether offline seeding is supported only for Windows-based backup servers (DPM/MABS), or if Linux-based backup solutions can participate.
  • Provide Linux parity: If supported, add instructions and examples for performing offline seeding from Linux systems, including any required tools, command-line utilities, or workflows.
  • List cross-platform alternatives: If AzureOfflineBackupDiskPrep.exe is Windows-only, mention any Linux-compatible alternatives or provide guidance for Linux users.
  • Browser requirements: Replace or supplement references to Microsoft Edge/Internet Explorer with cross-platform browsers (e.g., Chrome, Firefox) and clarify if any browser-specific features are required.
  • BitLocker alternatives: If disk encryption is required, mention Linux-compatible solutions (e.g., LUKS) for securing disks prior to shipment.
  • PowerShell alternatives: If Azure PowerShell is required, provide equivalent Azure CLI commands and instructions for Linux environments.
  • Explicitly mention limitations: If the workflow is not supported on Linux, clearly state this in the prerequisites and overview to avoid confusion.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-userestapi-createorupdatepolicy.md ...up/backup-azure-arm-userestapi-createorupdatepolicy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily through the use of Windows-centric time zones (e.g., 'Pacific Standard Time'), the absence of Linux-specific examples or references, and the use of terminology and patterns that are more familiar to Windows administrators (such as Azure VM, SQL in Azure VM, and SAP HANA in Azure VM, all of which are commonly deployed on Windows). There are no examples or guidance for Linux-specific backup scenarios, nor are Linux tools, conventions, or time zones mentioned.
Recommendations
  • Include examples for Linux-based Azure VMs, such as those running Ubuntu, CentOS, or other distributions, and clarify any differences in backup policy creation for Linux workloads.
  • Add references to Linux time zones (e.g., 'Europe/Berlin', 'Asia/Kolkata') in the request body examples and documentation, and explain how to specify them.
  • Provide parity in documentation for Linux workloads, such as MySQL/PostgreSQL in Azure VM, and Azure Files mounted on Linux systems.
  • Explicitly mention that the REST API is platform-agnostic and provide sample commands using Linux tools (e.g., curl, jq) alongside any Windows tools.
  • Ensure that terminology and instructions do not assume a Windows-first environment; highlight cross-platform compatibility and considerations.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically System Center DPM and Microsoft Exchange, both of which are Windows-only products. All instructions, examples, and tool references are for Windows (DPM Administrator Console, Eseutil, PowerShell), with no mention of Linux equivalents, cross-platform alternatives, or guidance for non-Windows systems. The only automation reference is to PowerShell, which is primarily a Windows tool.
Recommendations
  • Explicitly state that the guide is Windows-specific and clarify platform limitations at the beginning.
  • Provide links or references to backup solutions for Exchange on Linux (if supported) or for other mail servers commonly used on Linux (e.g., Postfix, Dovecot).
  • Include parity documentation for Linux-based backup solutions to Azure, such as using Azure Backup with Linux servers or open-source mail servers.
  • If PowerShell automation is discussed, mention or provide examples for Bash/shell scripting or cross-platform CLI tools where possible.
  • Highlight any Azure Backup features or agents available for Linux, and provide guidance for their use.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All examples, tools, and procedures assume Windows servers and Windows-specific utilities (e.g., ConfigureSharePoint.exe, Registry Editor, CMD commands, NT AUTHORITY\SYSTEM, Windows file paths, and Windows groups). There is no mention of Linux-based SharePoint deployments, nor are there any examples or instructions for Linux systems, shell commands, or cross-platform alternatives. The documentation presumes the use of Windows Server and Windows administrative patterns throughout.
Recommendations
  • Explicitly state platform requirements and limitations at the beginning of the documentation (e.g., 'MABS and SharePoint farm backup are only supported on Windows Server environments').
  • If any components or procedures can be performed on Linux (e.g., Azure Backup Server agent installation, monitoring, or recovery), provide equivalent Linux instructions and examples.
  • Where possible, mention cross-platform alternatives or clarify that certain tools (e.g., ConfigureSharePoint.exe, Registry Editor) are Windows-only.
  • Provide a comparison table or section outlining differences in backup and recovery procedures between Windows and Linux environments, if applicable.
  • Add links or references to documentation for Linux-based backup solutions for SharePoint or Azure workloads, if available.
  • Ensure that monitoring and notification steps include Linux-compatible methods (e.g., using sendmail/postfix for SMTP, Linux event logs, etc.), if supported.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows environments, specifically focusing on Data Protection Manager (DPM), a Windows-only backup solution. All examples, screenshots, and instructions assume the use of Windows Server, SQL Server on Windows, and DPM management consoles. There are no references to Linux-based SQL Server deployments, nor are there examples or guidance for backing up SQL Server running on Linux or using Linux-native tools. The only automation reference is to PowerShell, which is a Windows-centric scripting environment.
Recommendations
  • Include guidance and examples for backing up SQL Server running on Linux, using Azure Backup or other supported methods.
  • Mention and provide parity for Linux-native backup tools and workflows, such as using cron jobs, shell scripts, or native SQL Server backup commands on Linux.
  • Add screenshots and walkthroughs for Linux environments, including command-line instructions and configuration steps.
  • Reference automation options for Linux, such as Bash scripts or Azure CLI, in addition to PowerShell.
  • Clarify in the prerequisites and supported scenarios sections whether Linux-based SQL Server deployments are supported or not, and provide links to relevant documentation if available.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows-centric tools and workflows, specifically System Center Data Protection Manager (DPM), which is a Windows-only backup solution. All examples, instructions, and screenshots reference DPM and related Windows utilities (e.g., ConfigureSharePoint.exe, PowerShell). There are no mentions of Linux alternatives, cross-platform backup tools, or guidance for non-Windows environments. The documentation assumes the user is operating in a Windows ecosystem and does not provide parity for Linux administrators.
Recommendations
  • Include information about cross-platform or Linux-compatible backup solutions for SharePoint, if available.
  • Provide equivalent examples and instructions for Linux environments, such as using Azure CLI or other supported tools.
  • Mention any limitations or lack of support for Linux explicitly, so users are aware of platform constraints.
  • If DPM is Windows-only, suggest alternative Azure-native backup strategies for SharePoint running on Linux (if supported).
  • Add a section comparing Windows and Linux backup options for SharePoint, highlighting differences and best practices.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-database-postgresql.md ...in/articles/backup/backup-azure-database-postgresql.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. PowerShell is presented as the primary scripting method for granting database privileges, with explicit instructions and screenshots for setting environment variables via Windows Control Panel and System Properties. There are no equivalent Linux instructions or examples for running the script, setting environment variables, or using Linux-native tools. The order of presentation and screenshots consistently favor Windows workflows, and Linux alternatives are only briefly mentioned (e.g., 'Alternatively, you can assign these privileges by using the pgAdmin or PSQL tool') without detail.
Recommendations
  • Provide explicit Linux instructions for running the PowerShell (or shell) script, including how to set environment variables using bash/zsh.
  • Include screenshots or terminal examples for Linux environments (e.g., using export to set PATH, running scripts from the command line).
  • Offer Linux shell script alternatives to PowerShell scripts, or clarify cross-platform compatibility.
  • Present Linux and Windows workflows in parallel, rather than Windows-first, to ensure parity.
  • Expand on the use of pgAdmin and PSQL with step-by-step guidance for Linux users.
  • Add troubleshooting notes relevant to Linux environments (e.g., permissions, network configuration).
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the pgAdmin GUI tool for database management tasks, which is most commonly used on Windows. There are no examples or instructions for Linux-native tools (such as psql CLI), nor are there any command-line examples for Linux users. The screenshots and workflow descriptions focus on GUI-based, portal-driven, or Windows-centric patterns, with no mention of Linux equivalents or parity in tooling or workflow. This may disadvantage Linux users who prefer or require CLI-based operations.
Recommendations
  • Include examples using the psql command-line tool for backup, restore, and user management tasks, alongside pgAdmin instructions.
  • Provide explicit instructions or screenshots for Linux environments, such as connecting via psql, managing firewall rules, and granting permissions using CLI tools.
  • Mention cross-platform compatibility of Azure portal and REST API, and clarify that all operations can be performed from Linux, macOS, or Windows.
  • Add a section comparing GUI (pgAdmin) and CLI (psql) workflows, highlighting steps for both Windows and Linux users.
  • Ensure that code snippets and automation examples (such as ARM templates or scripts) are platform-agnostic or provide both PowerShell and Bash/CLI versions where relevant.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-disks.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-disks.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias. In the 'Next steps' section, Azure PowerShell is listed before Azure CLI, which is more commonly used on Linux. The only explicit cross-platform tool mentioned is Azure CLI, but no Linux-specific examples or shell commands are provided anywhere in the main content. Additionally, the link for assigning permissions refers to a PowerShell-focused page ('backup-managed-disks-ps.md'), with no mention of a Linux/CLI equivalent in the main flow. The documentation does not provide parity for Linux users in terms of examples or guidance.
Recommendations
  • Add explicit Azure CLI examples for all operations, especially for permission assignment, alongside or before PowerShell examples.
  • Reference both PowerShell and CLI documentation in prerequisite and permission assignment sections, not just PowerShell.
  • Where command-line examples are given, show both Windows (PowerShell) and Linux (Bash/CLI) syntax.
  • In 'Next steps', list Azure CLI before PowerShell or present them together to avoid implicit prioritization.
  • Include notes or sections for Linux users, highlighting any OS-specific considerations or differences.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-delete-vault.md ...blob/main/articles/backup/backup-azure-delete-vault.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a clear Windows bias: PowerShell is the primary automation method, with detailed script and command examples, while Linux alternatives are absent. Windows-specific tools and management consoles (MARS, MABS, DPM) are referenced exclusively, and the ARMClient installation instructions use Chocolatey (a Windows package manager). Azure CLI coverage is minimal and limited to VM backups, with no Linux shell or cross-platform scripting guidance. The documentation consistently presents Windows-centric workflows first and omits Linux-native or cross-platform automation options.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for all major operations, especially for deleting vaults and backup items.
  • Document how to perform vault deletion and dependency removal from Linux/macOS environments, including prerequisites and troubleshooting.
  • Include instructions for installing and using ARMClient on Linux/macOS (e.g., via npm or manual download), not just via Chocolatey.
  • Reference cross-platform management tools and clarify which steps are OS-agnostic.
  • Where PowerShell is used, note how to run it on Linux/macOS, or offer alternative scripts in Bash.
  • Expand Azure CLI support and documentation to cover more backup item types, and advocate for parity in CLI functionality.
  • Review all screenshots and UI references to ensure they are not Windows-specific, or provide Linux/macOS equivalents where relevant.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows environments, specifically System Center Data Protection Manager (DPM), which is a Windows-only product. All examples, prerequisites, and tooling references are Windows-centric (e.g., PowerShell, .NET Framework, MARSAgentInstaller.exe). There are no Linux equivalents or cross-platform instructions, and Windows tools and patterns are mentioned exclusively and first throughout the page.
Recommendations
  • Clarify early in the documentation that DPM is a Windows-only solution, and provide links or references to Azure Backup solutions for Linux workloads.
  • Add a section comparing DPM with Azure Backup options for Linux servers, such as using the Azure Backup agent for Linux or Azure VM backup for Linux VMs.
  • Where PowerShell or Windows-specific tools are referenced, mention if there are equivalent CLI or automation options for Linux environments (e.g., Azure CLI, REST API).
  • Include troubleshooting and setup guidance for Linux-based backup scenarios, or link to relevant documentation.
  • Ensure that examples and instructions for backup to Azure cover both Windows and Linux server scenarios, or clearly state the scope is limited to Windows/DPM.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically referencing the MARS agent, which is only available for Windows. All examples, screenshots, and instructions are for Windows tools (MARS console, Windows Server, DPM/MABS, Windows file paths, and Windows UI patterns). There are no Linux equivalents mentioned, nor any cross-platform guidance. Antivirus configuration, backup management, and recovery instructions are all Windows-centric, with no mention of Linux support or alternatives.
Recommendations
  • Explicitly state in the introduction that the MARS agent is only supported on Windows, and provide links to Linux backup solutions (such as Azure Backup for Linux or Azure VM Backup).
  • Add a comparison table or section outlining backup options for Linux systems and how they differ from MARS agent usage.
  • Where possible, provide parity examples for Linux (e.g., using Azure CLI, shell scripts, or Linux-based backup agents) or direct users to relevant documentation.
  • Clarify in each section that instructions are Windows-specific, and suggest alternatives for Linux users.
  • Include guidance on monitoring, reporting, and antivirus configuration for Linux environments if supported by other Azure backup solutions.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-manage-vms.md ...s/blob/main/articles/backup/backup-azure-manage-vms.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows bias, particularly in the section on reinstalling the VMSnapshot backup extension. The Windows process is described in extensive detail, including PowerShell cmdlets, registry edits, service management, and folder operations, with multiple screenshots. In contrast, the Linux instructions are minimal, lacking step-by-step guidance, explanations, or screenshots. Throughout the document, examples and tooling references (such as PowerShell and Windows registry) are specific to Windows, with Linux equivalents either missing or significantly less detailed.
Recommendations
  • Provide equally detailed, step-by-step instructions for Linux VM extension management, including relevant shell commands, file paths, and troubleshooting steps.
  • Include screenshots or terminal output examples for Linux procedures, similar to those provided for Windows.
  • When referencing tools (e.g., PowerShell, Registry Editor), also mention and demonstrate Linux equivalents (e.g., Bash, relevant config files).
  • Ensure that for every Windows-specific example or tool, a Linux counterpart is presented either alongside or in a parallel section.
  • Review the document for other areas where Windows terminology or tools are used exclusively, and add Linux alternatives where applicable.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-mabs-troubleshoot.md ...main/articles/backup/backup-azure-mabs-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for Azure Backup Server troubleshooting is heavily oriented toward Windows environments. All examples, file paths, registry keys, and troubleshooting steps reference Windows-specific tools, locations, and patterns (e.g., C:\ paths, Windows registry, Windows services, Windows Server Backup, DPM, and MARS agent). There are no examples, instructions, or troubleshooting steps for Linux systems, nor any mention of Linux equivalents or cross-platform considerations. Windows tools and concepts are presented exclusively and without alternatives.
Recommendations
  • Add troubleshooting steps and examples for Linux-based backup servers, if supported.
  • Include Linux file paths, service management commands (e.g., systemctl), and configuration locations alongside Windows equivalents.
  • Mention and document Linux-compatible backup agents or tools, if available.
  • Provide parity in antivirus configuration guidance for Linux (e.g., paths, processes, exclusion patterns).
  • Clarify platform support at the beginning of the documentation and, if Windows-only, make this explicit to avoid confusion.
  • If Azure Backup Server is Windows-only, consider linking to Linux backup solutions in Azure and their troubleshooting guides.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-mars-troubleshoot.md ...main/articles/backup/backup-azure-mars-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, with all troubleshooting steps, examples, and tool references tailored exclusively for Windows environments. There are no Linux equivalents or examples provided, and Windows tools (MMC console, Task Scheduler, Internet Explorer, Device Manager, Registry Editor, vssadmin, PowerShell) are referenced throughout. The documentation assumes the use of Windows Server and does not mention or support Linux-based backup agents or troubleshooting steps.
Recommendations
  • Clearly state at the beginning whether the MARS agent is Windows-only, and if so, provide links or references to Linux backup solutions (such as Azure Backup for Linux VMs) and their troubleshooting guides.
  • If Linux support exists, add equivalent troubleshooting steps, examples, and tool references for Linux environments (e.g., systemctl for services, cron for scheduling, bash commands for file operations, Linux proxy settings, etc.).
  • Where PowerShell is referenced, provide Bash or shell script equivalents for Linux.
  • Avoid referencing Windows-specific tools (Internet Explorer, Task Scheduler, Registry Editor) without mentioning Linux alternatives or clarifying their scope.
  • Add a section or note for Linux users, guiding them to appropriate documentation if this article does not apply.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-monitor-troubleshoot.md ...n/articles/backup/backup-azure-monitor-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively references Windows tools and workflows (Task Manager, Control Panel, Windows file paths) for troubleshooting Azure Backup monitoring issues. No Linux equivalents or cross-platform instructions are provided, and all examples use Windows-specific terminology and locations.
Recommendations
  • Add troubleshooting steps for Linux environments, such as using systemctl or service commands to check and restart the agent process.
  • Include Linux file path examples (e.g., /var/lib/azurebackup/...) alongside Windows paths.
  • Mention Linux tools (e.g., ps, journalctl, top) for process and log inspection.
  • Clearly indicate which steps apply to Windows and which to Linux, or provide a cross-platform troubleshooting section.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific backup tools (DPM, MABS, MARS) and providing links and examples that focus on Windows Server management. There are no explicit examples or mentions of Linux backup agents or Linux-specific monitoring workflows. The order of presentation and tool selection prioritizes Windows environments, with no parity for Linux workloads.
Recommendations
  • Add explicit examples and instructions for monitoring Linux-based backup workloads, including Azure Backup for Linux VMs and file systems.
  • Mention Linux backup agents and their monitoring capabilities alongside Windows tools like DPM, MABS, and MARS.
  • Provide links to documentation or tutorials for managing and monitoring Linux backup items in Recovery Services vault and Backup vault.
  • Ensure that terminology and examples are inclusive of both Windows and Linux environments, and avoid presenting Windows tools or workflows first unless justified by usage statistics.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-microsoft-azure-backup.md ...articles/backup/backup-azure-microsoft-azure-backup.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits strong Windows bias. All installation, configuration, and usage instructions are exclusively for Windows Server environments, with no mention of Linux support or examples. Windows-specific tools (e.g., PowerShell cmdlets, registry edits, Windows Server Deduplication) are referenced throughout, and all prerequisites, troubleshooting, and upgrade paths assume a Windows platform. There are no Linux equivalents or alternative instructions provided, and the documentation does not acknowledge or support non-Windows operating systems.
Recommendations
  • Explicitly state platform limitations and clarify if Linux is unsupported, or provide guidance for Linux users if support exists.
  • If possible, add Linux installation and configuration instructions, or link to relevant documentation for Linux-based backup solutions.
  • Include Linux command-line examples (e.g., Bash scripts, CLI commands) alongside PowerShell examples where applicable.
  • Mention Linux-compatible backup agents or third-party tools if Azure Backup Server is Windows-only, and provide migration or integration guidance.
  • Add a comparison table of supported platforms and features to help users understand OS-specific requirements and limitations.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-move-recovery-services-vault.md ...es/backup/backup-azure-move-recovery-services-vault.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is presented as the primary scripting example for moving Recovery Services vaults, with detailed cmdlets and instructions. The CLI example is present but less detailed, and there are no Bash or Linux shell script examples. Windows-specific guidance (e.g., installing Windows updates) is mentioned before Linux equivalents, and Linux instructions are less explicit. There is no mention of Linux-native tools or automation patterns, and the documentation does not provide parity for Linux users in terms of step-by-step examples or troubleshooting.
Recommendations
  • Expand CLI section with more detailed, step-by-step instructions equivalent to PowerShell examples.
  • Include Bash or Linux shell script examples for common operations, such as moving resources and post-migration tasks.
  • Provide troubleshooting steps and automation patterns for Linux users, similar to those given for Windows/PowerShell.
  • When mentioning OS-specific prerequisites (e.g., certificates), present Windows and Linux guidance in parallel, with equal detail.
  • Add references to Linux-native tools (e.g., curl, jq) for scripting Azure operations, where appropriate.
  • Ensure that all examples and instructions are OS-neutral or provide both Windows and Linux variants.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-recovery-services-vault-overview.md ...ackup/backup-azure-recovery-services-vault-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools and workloads (System Center DPM, Windows Server, Azure Backup Server) are mentioned explicitly and repeatedly, while Linux equivalents or examples are largely absent. References to backup scenarios and monitoring focus on Windows-centric technologies, and the 'Next steps' section provides a direct link for backing up Windows Server, but not for Linux servers. There are no Linux-specific backup examples, tools, or guidance, and Windows terminology appears first or exclusively in several sections.
Recommendations
  • Include explicit examples and guidance for backing up Linux servers, both on-premises and in Azure VMs.
  • Mention Linux-compatible backup tools or agents where Windows tools are listed (e.g., alternatives to MARS agent for Linux).
  • Provide parity in 'Next steps' by adding links for Linux server backup procedures.
  • Ensure monitoring and management sections reference Linux workloads and their integration with Recovery Services vaults.
  • Balance references to Windows and Linux throughout the documentation, especially in lists and feature descriptions.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-private-endpoints-concept.md ...icles/backup/backup-azure-private-endpoints-concept.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by repeatedly referencing Windows-specific backup tools (MARS agent, DPM, MABS) and scenarios, without mentioning or providing parity for Linux backup agents or Linux VM scenarios. All concrete agent examples and recommendations are for Windows workloads, and there are no Linux-specific instructions, examples, or clarifications. The documentation implicitly assumes the use of Windows-based backup tooling and omits Linux equivalents, leading to a lack of guidance for Linux users.
Recommendations
  • Add explicit references to Linux VM backup scenarios, including how private endpoints affect backup/restore operations for Linux workloads.
  • Include examples or notes for Linux backup agents (such as Azure VM extension for Linux) and clarify any differences in connectivity, DNS setup, or agent behavior.
  • Provide parity in recommendations and supported scenarios for Linux-based workloads, not just SQL Server, SAP HANA, MARS agent, DPM, and MABS.
  • If there are limitations or differences for Linux, document them clearly to help Linux users plan their backup and private endpoint strategies.
  • Add sample configurations or troubleshooting steps for Linux environments, such as DNS resolution or agent installation on Linux VMs.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by frequently presenting Windows steps, tools, and troubleshooting before their Linux equivalents. Windows-specific concepts (e.g., registry edits, Storage Spaces, drive letters, File Explorer) are described in detail, while Linux instructions are sometimes less detailed or presented after Windows. The 'Next steps' section highlights PowerShell before CLI, and troubleshooting for large disks is more elaborate for Windows. Some Linux-specific patterns (e.g., LVM/RAID) are covered, but overall, Windows terminology and workflows dominate.
Recommendations
  • Present Windows and Linux instructions in parallel, with equal detail and prominence.
  • Ensure Linux troubleshooting steps (e.g., for large disks, permissions, mount issues) are as comprehensive as Windows.
  • Include Linux-specific examples and screenshots (e.g., file browsing, mount/unmount workflows) alongside Windows equivalents.
  • In 'Next steps', list CLI and Linux automation options before or alongside PowerShell.
  • Expand on Linux file system and permission considerations, matching the depth given to Windows ACLs and registry.
  • Avoid Windows-centric terminology (e.g., 'drive letters', 'File Explorer') without Linux equivalents or explanations.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on troubleshooting System Center Data Protection Manager (DPM), which is a Windows-only product. All examples, commands, and troubleshooting steps reference Windows tools (e.g., command prompt, net stop/start, NT AUTHORITY\SYSTEM, MARS agent), with no mention of Linux equivalents or cross-platform scenarios. Linux systems, tools, or troubleshooting patterns are absent, and Windows terminology is used exclusively and first throughout the document.
Recommendations
  • Clarify in the introduction that DPM is a Windows-only product, and explicitly state platform limitations.
  • If there are any cross-platform backup or recovery scenarios (e.g., protecting Linux workloads via agents or interoperability with Azure Backup), include troubleshooting steps and examples for those cases.
  • Where possible, mention Linux-compatible alternatives (such as Azure Backup for Linux) and link to relevant documentation.
  • If troubleshooting steps involve command-line actions, consider providing PowerShell and Bash equivalents where applicable, or note when only Windows commands are supported.
  • Review documentation for opportunities to generalize troubleshooting advice for hybrid environments, if supported by the product.