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 751-775 of 1604 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/scripts/set-file-folder-backup-policy.md ...ticles/backup/scripts/set-file-folder-backup-policy.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 biased towards Windows, providing only PowerShell script samples and instructions. It exclusively references Windows-specific tools (MARS agent, MSOnlineBackup, PowerShell cmdlets) and registry paths, with no mention of Linux equivalents or cross-platform alternatives. There are no Bash or Linux shell script examples, nor any guidance for Linux administrators.
Recommendations
  • Add equivalent Linux/Bash script samples for creating or modifying backup policies.
  • Include instructions for Linux environments, referencing common backup tools (e.g., rsync, cron, or Azure CLI for Linux).
  • Clearly indicate platform-specific requirements and provide parity in documentation structure and examples.
  • Mention whether the MARS agent or similar functionality is available for Linux, and if not, suggest alternative approaches for Linux users.
  • Ensure that introductory and instructional sections do not assume a Windows-first audience.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/scripts/set-system-state-backup-policy.md ...icles/backup/scripts/set-system-state-backup-policy.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides a PowerShell script for managing system state backup policies with the MARS agent, which is a Windows-only tool. All instructions and examples are tailored to Windows environments, with no mention of Linux equivalents, alternative scripting languages, or cross-platform approaches. The documentation assumes the use of Windows tools and patterns throughout.
Recommendations
  • Clearly state that the MARS agent and the provided script are Windows-only, and mention any Linux alternatives if available.
  • If Linux support exists for similar backup scenarios, provide equivalent Bash or shell script examples, or reference Linux-native backup tools.
  • Add a section comparing Windows and Linux backup management approaches, highlighting differences and guiding users to appropriate solutions for each platform.
  • Ensure that future documentation includes cross-platform considerations, or explicitly notes platform limitations to avoid confusion.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/active-directory-backup-restore.md ...ain/articles/backup/active-directory-backup-restore.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 focused on Windows-based Active Directory environments. All examples, scripts, and tools mentioned (such as PowerShell, ntdsutil.exe, DSRM) are specific to Windows Server. There are no references to Linux-based domain controllers, Samba, or cross-platform backup/restore scenarios. Windows terminology and tools are used exclusively and presented as the default, with no Linux alternatives or parity.
Recommendations
  • Add guidance for environments using Samba (Active Directory on Linux) where applicable, including backup and restore procedures.
  • Provide equivalent examples for Linux-based domain controllers, such as using native Linux tools or scripts for backup and restore.
  • Mention cross-platform considerations, such as interoperability between Windows and Linux domain controllers, if supported.
  • Clarify that the procedures are specific to Windows Server, and explicitly state limitations or alternatives for Linux environments.
  • Include links or references to documentation for Linux-based Active Directory solutions and their backup/restore strategies.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/back-up-azure-stack-hyperconverged-infrastructure-virtual-machines.md ...e-stack-hyperconverged-infrastructure-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 ways: Windows-specific tools and terminology (such as PowerShell cmdlets, NTLM authentication, Hyper-V, and Windows-centric agent installation) are used throughout, with examples and instructions tailored to Windows environments. Linux support is mentioned only briefly and generically, with no concrete examples, commands, or screenshots. All step-by-step instructions, code snippets, and screenshots are Windows-focused, and there is no guidance for Linux users on agent installation, backup, or recovery operations.
Recommendations
  • Add explicit Linux backup and recovery examples, including command-line instructions for agent installation, configuration, and recovery operations on Linux VMs.
  • Provide Linux-specific troubleshooting steps and prerequisites, such as required packages, permissions, and supported distributions.
  • Include screenshots or terminal output relevant to Linux environments, not just Windows GUIs.
  • Clarify any differences in backup/restore workflows for Linux VMs, especially where features are limited (e.g., file-consistent snapshots only).
  • Mention Linux authentication options and provide parity with Windows (e.g., certificate-based authentication steps for Linux).
  • Where PowerShell or Windows tools are referenced, offer equivalent Linux shell commands or procedures.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-backup-glossary.md ...ocs/blob/main/articles/backup/azure-backup-glossary.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The glossary page demonstrates a Windows bias through frequent references to Windows-specific technologies (e.g., VSS, DPM, MARS agent, MABS), and by listing Windows tools and concepts (such as Azure PowerShell and VSS) before or without Linux equivalents. Where backup consistency is discussed, Windows VSS is mentioned first and in detail, while Linux is only briefly referenced as 'pre or post scripts.' There are no concrete Linux examples or references to Linux-native backup concepts, and most workload-specific backup solutions described are Microsoft/Windows-centric.
Recommendations
  • Add explicit Linux backup examples and terminology, such as referencing Linux-native snapshot and backup tools (e.g., LVM snapshots, rsync, tar, etc.).
  • When describing backup consistency, provide equal detail for Linux approaches (e.g., how application consistency is achieved on Linux, common patterns, and supported tools).
  • Include Linux CLI commands and workflows alongside Azure PowerShell references, and ensure Azure CLI examples are not Windows-centric.
  • Reference Linux-based backup agents or third-party tools where applicable, and clarify support for Linux workloads in Azure Backup.
  • Avoid listing Windows tools or concepts before Linux equivalents, or provide both in parallel to ensure parity.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-backup-concept.md ...kup/azure-kubernetes-service-cluster-backup-concept.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by listing Azure PowerShell as a primary method for backup and restore operations, sometimes before Azure CLI, and by not providing explicit Linux or Bash examples or references. The 'Next steps' section mentions Azure PowerShell for backup before Azure CLI, and only provides a CLI example for restore, not for backup. There is also a lack of explicit Linux/Bash command-line guidance, which may disadvantage Linux users.
Recommendations
  • Ensure that both Azure CLI and Azure PowerShell examples are provided for all operations, and that CLI (cross-platform) examples are given equal or higher prominence than PowerShell.
  • Explicitly mention and provide Bash/Linux shell command examples where relevant, especially for AKS users who are likely to use Linux environments.
  • In the 'Next steps' section, list Azure CLI and Azure PowerShell options together for both backup and restore, or list CLI first to reflect its cross-platform nature.
  • Where portal instructions are given, clarify that the portal is OS-agnostic, and supplement with CLI/Bash examples for automation scenarios.
  • Audit linked documentation to ensure Linux parity in all referenced guides, especially those covering installation and management operations.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/about-azure-vm-restore.md ...cs/blob/main/articles/backup/about-azure-vm-restore.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 providing detailed references and links exclusively for Windows encrypted VM restore scenarios, mentioning PowerShell as the tool for VM creation, and omitting equivalent Linux scenarios or tools. There are no examples or links for restoring encrypted Linux VMs, and the only scripting tool mentioned is PowerShell, which is primarily associated with Windows environments.
Recommendations
  • Add equivalent Linux restore scenarios, especially for encrypted Linux VMs, including links to relevant documentation.
  • Include examples or references for using Azure CLI or Bash scripts for VM restore operations, not just PowerShell.
  • Ensure restore instructions and references are provided for both Windows and Linux VMs in all scenarios, especially where encryption or OS-specific steps are required.
  • Where possible, present both Windows and Linux options side-by-side, or clarify when a scenario is Windows-only.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/automation-backup.md ...re-docs/blob/main/articles/backup/automation-backup.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently referencing PowerShell as a primary automation tool, mentioning it before CLI and other cross-platform options. Example automation workflows and scenarios (such as retrying failed jobs) are described using PowerShell and Azure Automation Runbooks, with no explicit Linux shell (Bash) or cross-platform CLI examples provided. There is a lack of Linux-specific guidance or parity in the examples, which may make Linux users feel underserved.
Recommendations
  • Provide explicit Bash/CLI examples alongside PowerShell for all automation scenarios.
  • When listing automation methods, avoid listing PowerShell first by default; alternate or group cross-platform tools (CLI, REST API, SDKs) before platform-specific ones.
  • Include sample scripts or links for Linux shell automation (e.g., Bash scripts using Azure CLI) in each scenario.
  • Highlight cross-platform automation tools (Terraform, Ansible) with equal detail and provide end-to-end examples.
  • Ensure that video and walkthrough content includes Linux/CLI demonstrations, not just PowerShell/Windows-based workflows.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-data-lake-storage-backup-support-matrix.md ...ackup/azure-data-lake-storage-backup-support-matrix.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning PowerShell and Azure portal as primary configuration and management methods, with Azure CLI only referenced in passing. There are no explicit Linux-specific examples, nor are Linux-native tools or workflows discussed. The order of presentation (portal, PowerShell, then CLI) prioritizes Windows-centric tools, and there is no mention of Bash, shell scripting, or Linux desktop workflows.
Recommendations
  • Provide explicit Linux/Bash examples for configuring and managing vaulted backups, such as step-by-step instructions using Azure CLI in a Linux shell.
  • Reorder example lists to alternate or start with cross-platform tools (e.g., Azure CLI) before Windows-specific tools like PowerShell.
  • Include references to Linux desktop environments and workflows, such as using the Azure CLI in GNOME Terminal or KDE Konsole.
  • Add troubleshooting and usage notes relevant to Linux users, such as authentication methods and file system considerations.
  • Ensure parity in screenshots and UI walkthroughs by including examples from Linux environments where applicable.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-restore.md ...les/backup/azure-kubernetes-service-cluster-restore.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily by referencing Azure PowerShell as an alternative restore method, without mentioning or providing examples for Azure CLI or Linux-native tools. The only non-portal automation method highlighted is PowerShell, which is most commonly used on Windows. There are no Linux-specific instructions, nor is there parity in command-line examples for Linux users.
Recommendations
  • Add equivalent Azure CLI instructions for restoring AKS clusters, ensuring Linux users have clear, supported automation paths.
  • Mention Azure CLI alongside Azure PowerShell in the introduction and throughout the documentation where automation is discussed.
  • Provide example commands and scripts for both PowerShell and Azure CLI, and clarify platform compatibility for each.
  • Include notes or sections on using the documented procedures from Linux/macOS environments, addressing any platform-specific considerations.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-vms-prepare.md ...b/main/articles/backup/backup-azure-arm-vms-prepare.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows a Windows bias in the 'Install the VM agent' section, where Windows instructions (MSI installer, file path, executable verification) are presented first and in greater detail than Linux instructions. The Linux instructions are less specific, lacking concrete commands or examples, and do not mention verification steps. The rest of the documentation is mostly platform-neutral, but the agent installation section favors Windows in both order and depth.
Recommendations
  • Present Linux and Windows instructions in parallel, with equal detail and clarity.
  • Provide explicit Linux installation commands (e.g., apt, yum, zypper) and verification steps for the agent version.
  • Include example file paths and commands for Linux agent verification, similar to the Windows example.
  • Avoid listing Windows instructions first by default; alternate or group by platform.
  • Mention both MSI (Windows) and package manager (Linux) methods with equal prominence and detail.
GitHub Create Pull Request
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses exclusively on troubleshooting data recovery from Microsoft Azure Backup Server, which is a Windows-based solution. All examples and recommendations reference Windows Server, Windows Client, and tools such as the Azure Backup agent, with no mention of Linux equivalents or cross-platform scenarios. There are no troubleshooting steps or examples for Linux systems, nor are Linux backup agents or recovery patterns discussed.
Recommendations
  • Clarify in the introduction that Azure Backup Server is a Windows-only solution, if applicable, or provide guidance for Linux users.
  • Add troubleshooting sections or links for Linux-based backup and recovery scenarios using Azure Backup.
  • Include examples and recommendations for Linux backup agents and recovery processes, if supported.
  • Mention alternative cross-platform backup solutions in Azure for organizations using Linux servers.
GitHub Create Pull Request
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-08 00:53
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, prerequisites, and tooling (MARS agent, AzureOfflineBackupDiskPrep utility, Azure PowerShell, command prompt usage, and browser requirements) are specific to Windows. There is no mention of Linux support, Linux-compatible tools, or alternative workflows for non-Windows systems. The documentation assumes the use of Windows servers and clients throughout, and does not provide parity for Linux users.
Recommendations
  • Explicitly state whether Linux is supported or not for the offline seeding workflow. If not supported, clarify this early in the documentation.
  • If Linux support exists or is planned, provide equivalent Linux workflows, including supported agents, utilities, and command-line examples (e.g., Bash, Azure CLI).
  • Mention Linux-compatible browsers and clarify if browser requirements (Edge/IE11) are only for Windows or if alternatives exist for Linux.
  • Provide guidance on preparing disks from Linux systems, including mounting, formatting, and running any required utilities.
  • Include troubleshooting and FAQ sections for Linux users, or link to relevant resources.
  • Ensure that prerequisites and steps do not assume Windows-only environments; offer cross-platform instructions where possible.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/archive-tier-support.md ...docs/blob/main/articles/backup/archive-tier-support.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by focusing exclusively on Azure Virtual Machines (which are often Windows-based), SQL Server, and SAP HANA in Azure VMs as supported workloads, with no mention of Linux-specific backup scenarios or workloads. In the 'Supported clients' section, PowerShell is listed before CLI, and there are no Bash or Linux shell examples. There are no references to Linux tools, commands, or patterns, nor are there examples or guidance for Linux users. The screenshots and instructions are tailored to the Azure portal and PowerShell, which are more commonly used by Windows users.
Recommendations
  • Add explicit examples and instructions for Linux-based workloads, such as Linux VMs, PostgreSQL, or MySQL in Azure.
  • Include CLI (az) and Bash shell examples alongside or before PowerShell examples to ensure parity.
  • Mention Linux-specific backup scenarios and considerations, such as file system types, application consistency, or integration with Linux backup tools.
  • Provide screenshots or walkthroughs using Linux environments where relevant.
  • Clarify that the archive tier is available for both Windows and Linux VMs, if applicable, and highlight any differences.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-backup-overview.md ...les/backup/azure-kubernetes-service-backup-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias primarily through its ordering and emphasis on Windows-centric tools. In the 'Related content' section, PowerShell (a Windows-first tool) is listed before Azure CLI (cross-platform), suggesting a preference for Windows workflows. The documentation references Azure PowerShell and does not provide explicit Linux shell or bash examples for backup/restore operations, nor does it mention Linux-specific tools or patterns. The only command-line examples shown are generic YAML or JSON, not shell commands, and there is no mention of Linux-native scripting or usage patterns.
Recommendations
  • Ensure that Azure CLI (cross-platform) examples are presented before or alongside PowerShell examples in both the main documentation and related content.
  • Include explicit bash or Linux shell command examples for backup and restore operations, demonstrating parity with PowerShell instructions.
  • Reference Linux-native tools and workflows where appropriate, such as kubectl usage in bash, and clarify that all operations can be performed on Linux, macOS, and Windows equally.
  • Add a section or note highlighting cross-platform compatibility and provide links to Linux/macOS-specific guides if available.
  • Review and update related content ordering to avoid implicit prioritization of Windows tools.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-backup-support-matrix.md ...azure-kubernetes-service-cluster-backup-support-matrix.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure Kubernetes Service (AKS) backup support matrix exhibits Windows bias in several ways. It references Azure PowerShell and Windows-based node pools, and lists Azure PowerShell before Linux-native tools (e.g., Azure CLI, Terraform) in the 'Next steps' section. There is a lack of explicit Linux command-line examples or guidance, and the documentation does not provide parity for Linux users in terms of tooling or operational instructions. Additionally, the documentation mentions that the Backup Extension cannot be installed on Windows-based node pools, but does not provide Linux-specific setup or troubleshooting examples.
Recommendations
  • Provide explicit Linux command-line examples (e.g., bash, Azure CLI) alongside or before PowerShell examples.
  • Ensure that Linux-native tools (Azure CLI, Terraform) are listed before or equally with Windows tools (PowerShell) in all sections.
  • Add troubleshooting and setup guidance specifically for Linux environments, including Ubuntu and Azure Linux node pools.
  • Clarify operational differences for Linux users, such as permissions, file paths, and environment variables.
  • Include references to Linux documentation or best practices for AKS backup operations.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/back-up-file-data.md ...re-docs/blob/main/articles/backup/back-up-file-data.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for backing up file data with MABS demonstrates Windows bias. All instructions and terminology are tailored to Windows environments, referencing Windows-specific features (such as Data Deduplication, Volume Shadow Copy Service, and file/folder selection patterns). There are no examples, instructions, or clarifications for Linux systems, nor any mention of Linux-specific backup considerations or tools. The documentation assumes the use of Windows consoles and features, and does not address cross-platform scenarios.
Recommendations
  • Add explicit instructions and examples for backing up Linux machines with MABS, including agent installation and supported file systems.
  • Clarify which features (e.g., deduplication, VSS, EUR) are Windows-only and provide Linux alternatives or note limitations.
  • Include Linux-specific terminology and workflows, such as typical Linux directory structures, permissions, and recovery patterns.
  • Mention any differences in backup and recovery procedures for Linux clients, and provide troubleshooting steps for common Linux issues.
  • Ensure parity in documentation by presenting Linux and Windows steps side-by-side where applicable.
GitHub Create Pull Request
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-08 00:53
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 oriented toward Windows environments, specifically System Center Data Protection Manager (DPM) and Microsoft Azure Backup Server (MABS), both of which are Windows-only products. All examples, prerequisites, and tooling (such as AzureOfflineBackupDiskPrep.exe and Azure PowerShell) are Windows-centric. There is no mention of Linux equivalents, nor are Linux-compatible workflows, tools, or examples provided. The documentation assumes the use of Windows features (BitLocker, Edge/IE, command prompt) and does not address Linux scenarios or alternatives.
Recommendations
  • Clearly state that DPM and MABS are Windows-only and provide guidance for Linux users (e.g., suggest MARS agent or other Azure Backup solutions that support Linux).
  • If Azure Import/Export can be used with Linux-based backup workflows, provide equivalent Linux instructions, including disk preparation and import job creation using Linux tools (e.g., Bash, Azure CLI).
  • Include examples using Azure CLI instead of (or in addition to) Azure PowerShell, as Azure CLI is cross-platform.
  • Mention browser requirements in a cross-platform way (e.g., Chrome, Firefox) and clarify if any steps are Windows-specific.
  • If BitLocker is required, suggest Linux alternatives for disk encryption (e.g., LUKS) or clarify that BitLocker is only needed for Windows environments.
  • Add a section or links for Linux backup workflows to Azure, if supported, or explicitly state limitations for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-data-lake-storage-configure-backup.md ...les/backup/azure-data-lake-storage-configure-backup.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is featured as a primary method for command-line configuration, with detailed step-by-step examples and cmdlets. The Azure CLI section is present and reasonably detailed, but PowerShell is listed before CLI in both the title and zone pivots, and the prerequisites for PowerShell include explicit instructions for installing Azure PowerShell (a Windows-centric tool). There is no mention of Linux-specific shell environments (e.g., bash), nor any guidance for Linux users regarding prerequisites or environment setup. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users beyond the Azure CLI commands.
Recommendations
  • Add explicit instructions and prerequisites for Linux users, such as installing Azure CLI on Linux and verifying shell compatibility.
  • Include bash or shell script examples alongside PowerShell, especially for common tasks like fetching ARM IDs or manipulating JSON.
  • Reorder the pivots and title to present Azure CLI before PowerShell, or at least equally, to avoid Windows-first perception.
  • Mention cross-platform compatibility for all command-line tools, clarifying which steps work identically on Linux, macOS, and Windows.
  • Provide troubleshooting tips or notes for Linux users, such as handling file paths, environment variables, or permissions.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-manage-backups.md ...kup/azure-kubernetes-service-cluster-manage-backups.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily provides Azure CLI commands and Azure portal instructions, which are cross-platform. However, in the 'Next steps' section, Azure PowerShell is explicitly mentioned as a method for backup, but there is no mention of Linux-native tools or shell scripting alternatives. There are no examples or references to Linux-specific workflows, such as using Bash scripts, kubectl, or Linux file system tools. The documentation does not provide parity for Linux users in terms of command-line examples or troubleshooting steps, and the mention of PowerShell in 'Next steps' may imply a Windows-centric approach.
Recommendations
  • Add explicit Bash shell examples for all CLI commands, showing usage in Linux environments.
  • Include troubleshooting steps and examples using kubectl and Linux-native tools for managing AKS backups.
  • Mention and link to Linux-specific documentation or guides for AKS backup management.
  • Ensure parity in 'Next steps' by referencing Bash/Linux shell scripting alongside PowerShell.
  • Clarify that Azure CLI commands are cross-platform and provide any OS-specific caveats if relevant.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-architecture.md ...-docs/blob/main/articles/backup/backup-architecture.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a clear Windows bias. Backup methods and tools (MARS agent, DPM, MABS) are described almost exclusively for Windows environments, with explicit statements that Linux is not supported in key scenarios (e.g., MARS agent). Windows-centric technologies (VSS, MARS agent, DPM/MABS) are referenced throughout, and Linux alternatives or parity features are not discussed. Examples and step-by-step instructions focus on Windows, with no equivalent Linux walkthroughs or tooling mentioned. The documentation structure and example order consistently prioritize Windows scenarios over Linux.
Recommendations
  • Add explicit sections and examples for Linux backup scenarios, including supported agents, workflows, and limitations.
  • Clearly state Linux support status for each backup method and provide links to Linux-specific documentation where available.
  • If Linux is not supported for a given method (e.g., MARS agent), suggest alternative Azure-native backup solutions for Linux workloads.
  • Include parity tables or comparison charts showing feature availability for both Windows and Linux.
  • Provide Linux command-line examples (e.g., Bash, Azure CLI) alongside PowerShell/Windows examples.
  • Reference Linux backup tools and patterns (e.g., Azure Backup for Linux VMs, integration with native Linux backup utilities) where appropriate.
  • Ensure that documentation navigation and 'Next steps' include Linux-focused guides and scenarios.
GitHub Create Pull Request
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: 2026-01-08 00:53
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 Azure Backup Server and System Center Data Protection Manager (DPM), which are Windows-only tools. All instructions, screenshots, and terminology are specific to the Windows ecosystem, with no mention of Linux equivalents, cross-platform tools, or CLI-based recovery options. There are no examples or guidance for Linux users or administrators using non-Windows backup solutions.
Recommendations
  • Explicitly state the platform requirements and limitations at the beginning of the document.
  • Provide guidance or links for Linux-based backup and recovery solutions in Azure, such as using Azure Backup for Linux VMs or Azure CLI/PowerShell cross-platform commands.
  • Include examples or references for recovering data from Linux systems, if supported, or direct users to appropriate documentation.
  • Clarify whether any steps can be performed using cross-platform tools, and if so, provide those instructions alongside the Windows/DPM workflow.
  • Add a comparison table or section outlining differences and available features for Windows and Linux environments in Azure Backup.
GitHub Create Pull Request
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page exclusively describes backup and restore operations using System Center Data Protection Manager (DPM), a Windows-only tool. All instructions, tool references, and screenshots are based on Windows environments. The only automation example referenced is via PowerShell, with no mention of Linux-compatible tools, commands, or workflows. There are no examples or guidance for performing similar operations on Linux or cross-platform environments.
Recommendations
  • Provide equivalent instructions for Linux environments, including supported backup tools (e.g., Azure CLI, third-party solutions, or native Linux backup utilities).
  • Include Linux-specific prerequisites and setup steps, such as agent installation and configuration.
  • Offer automation examples using Bash scripts or Azure CLI commands alongside PowerShell.
  • Clarify platform limitations and suggest alternatives for non-Windows users.
  • Add screenshots and walkthroughs for Linux-based backup and restore processes where possible.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/back-up-hyper-v-virtual-machines-mabs.md ...ticles/backup/back-up-hyper-v-virtual-machines-mabs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Windows Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server, with detailed procedures and prerequisites for Windows Server VMs. Linux support is mentioned only briefly and lacks detailed guidance or examples. All backup and recovery steps, screenshots, and item-level recovery features are described for Windows Server VMs, with no equivalent instructions for Linux VMs. Windows-specific tools, features, and registry keys are referenced throughout, while Linux tools and patterns are absent.
Recommendations
  • Add step-by-step backup and recovery instructions for Linux VMs, including screenshots and console workflows.
  • Clarify limitations and supported features for Linux VMs (e.g., item-level recovery, snapshot types) in dedicated sections.
  • Include examples of restoring files from Linux VMs, noting differences in process or supported features.
  • Reference Linux-specific tools or commands where relevant, and provide parity in troubleshooting and configuration guidance.
  • Present Linux prerequisites and scenarios alongside Windows, rather than as a brief note.
  • Avoid Windows-centric registry key instructions unless Linux alternatives or notes are provided.
GitHub Create Pull Request
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for the MARS agent is heavily focused on Windows environments. All backup and recovery scenarios, technical details, and process descriptions reference Windows-specific features (such as VSS, USN change journal, and system state), with no mention of Linux support, Linux filesystems, or Linux equivalents. There are no examples, instructions, or references for Linux systems, and Windows terminology and tools are used exclusively throughout the page.
Recommendations
  • Explicitly state whether the MARS agent supports Linux systems. If not, clarify its Windows-only scope early in the documentation.
  • If Linux support exists, add equivalent Linux examples and instructions for backup and recovery scenarios.
  • Mention Linux backup tools or patterns where applicable, or provide links to Azure Backup solutions for Linux.
  • Avoid using Windows-specific terminology (e.g., VSS, USN) without explaining their relevance or alternatives for other platforms.
  • Provide a comparison table or section outlining platform support and differences between Windows and Linux backup agents in Azure.
GitHub Create Pull Request
← Previous Page 31 of 65 Next →