Backup

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 126-150 of 520 flagged pages
Backup Back up a SharePoint farm to Azure with MABS ...articles/backup/backup-azure-backup-sharepoint-mabs.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with all examples, tools, and procedures referencing Windows-specific components such as CMD commands, Registry Editor, Windows file paths, and Windows services. There are no Linux equivalents or cross-platform instructions, and all administrative tasks assume a Windows OS context. The use of tools like ConfigureSharePoint.exe, references to NT AUTHORITY\SYSTEM, and registry modifications further reinforce the Windows bias. No Linux or PowerShell Core examples are provided, nor is there mention of how (or if) MABS can be used in non-Windows environments.
Recommendations
  • Explicitly state platform requirements and limitations at the start of the documentation, including whether Linux is supported or not.
  • If MABS is Windows-only, provide guidance or links for Linux-based alternatives for SharePoint backup to Azure.
  • Where possible, offer PowerShell Core or cross-platform command examples, or clarify that only Windows PowerShell/CMD is supported.
  • Include a comparison table or section outlining differences in procedure or support between Windows and Linux environments.
  • If any part of the workflow can be performed from a Linux machine (e.g., Azure CLI for monitoring or notification setup), provide those examples.
  • Clarify whether SharePoint on Linux (if supported in future) or hybrid environments can be protected, and document any limitations.
GitHub Create Pull Request
Backup Back up SQL Server to Azure as a DPM workload ...s/blob/main/articles/backup/backup-azure-backup-sql.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 focused on Windows environments, specifically using Data Protection Manager (DPM), which is a Windows-only tool. All examples, screenshots, and instructions assume the use of Windows Server, Windows-based SQL Server, and DPM management consoles. There are no references to Linux-based SQL Server deployments, nor are there any examples or guidance for backing up SQL Server on Linux. The only automation reference is to PowerShell, which is Windows-centric.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server running on Linux, including supported backup tools and workflows.
  • Mention and provide parity for Linux-native backup tools and automation options (such as Bash scripts, cron jobs, or Azure CLI).
  • Clarify whether Azure Backup supports SQL Server on Linux and, if so, document any differences or limitations.
  • Include screenshots and walkthroughs for Linux environments where applicable.
  • Reference cross-platform automation options (e.g., Azure CLI, REST API) alongside PowerShell.
  • If DPM is not supported on Linux, suggest alternative Azure-native backup solutions for SQL Server on Linux.
GitHub Create Pull Request
Backup Overview of Azure Database for PostgreSQL Backup ...es/backup/backup-azure-database-postgresql-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively recommending and illustrating the use of pgAdmin—a GUI tool most commonly used on Windows—for database management tasks. There are no examples or instructions for Linux-native tools (such as psql CLI), nor is there mention of Linux workflows or command-line alternatives. The screenshots and step-by-step instructions focus on GUI interactions typical of Windows environments, and there is no parity for Linux users who may prefer or require CLI-based management.
Recommendations
  • Add examples and instructions for using psql (the PostgreSQL command-line client) for backup, restore, and user management tasks.
  • Include Linux-specific workflows, such as connecting via terminal, managing firewall rules, and running SQL commands from the shell.
  • Provide screenshots or text-based walkthroughs for Linux environments (e.g., Ubuntu, CentOS) alongside the existing pgAdmin GUI instructions.
  • Explicitly mention cross-platform compatibility and recommend tools available on both Windows and Linux, or clarify when a tool is Windows-specific.
  • Ensure REST API and CLI instructions are highlighted and not only GUI-based, to support automation and Linux-native usage.
GitHub Create Pull Request
Backup Prepare the DPM server to back up workloads .../main/articles/backup/backup-azure-dpm-introduction.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 instructions reference Windows tools (PowerShell, .NET Framework, MARSAgentInstaller.exe), and there are no Linux equivalents or cross-platform alternatives mentioned. The documentation assumes the use of Windows servers and omits guidance for Linux-based backup scenarios, even in sections where general backup agent installation or vault credential usage is discussed.
Recommendations
  • Explicitly state that DPM is a Windows-only product at the beginning of the documentation.
  • Provide links or references to Azure Backup documentation for Linux workloads, such as using MARS agent alternatives or Azure Backup for Linux VMs.
  • Where backup agent installation is discussed, include a note or section on how Linux servers can be backed up to Azure (if supported), or clarify that the instructions are not applicable to Linux.
  • Add parity in troubleshooting and prerequisites sections by mentioning Linux-specific requirements or limitations, if any.
  • In related content, include links to documentation for backing up Linux servers to Azure.
GitHub Create Pull Request
Backup Troubleshoot the Azure Backup agent ...main/articles/backup/backup-azure-mars-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page for troubleshooting the Azure Backup (MARS) agent exhibits strong Windows bias. All examples, troubleshooting steps, and tool references are exclusively for Windows environments. There are no Linux equivalents or mentions, and Windows-specific tools (MMC console, Internet Explorer, Task Scheduler, Registry Editor, Device Manager, vssadmin, PowerShell, etc.) are used throughout. The page assumes the user is operating on Windows, with no guidance for Linux users or cross-platform parity.
Recommendations
  • Add explicit statements clarifying platform support (e.g., whether MARS agent is Windows-only, and alternatives for Linux).
  • If Linux is supported, provide troubleshooting steps and examples for Linux environments (e.g., using systemd, cron, Linux file paths, bash commands).
  • Mention Linux equivalents for Windows tools (e.g., use curl/wget for downloads, systemctl for service management, etc.).
  • Include PowerShell alternatives for Linux (such as Bash scripts or Azure CLI commands).
  • Provide parity in error codes and troubleshooting for Linux-based backup agents, if available.
  • If MARS agent is not supported on Linux, clearly state this and link to documentation for Linux backup solutions (such as Azure Backup for Linux VMs or Azure CLI-based backup).
GitHub Create Pull Request
Backup Troubleshoot Azure Backup Server ...main/articles/backup/backup-azure-mabs-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation for Azure Backup Server troubleshooting is heavily oriented towards Windows environments. All examples, paths, registry keys, and troubleshooting steps reference Windows-specific tools, locations, and patterns (e.g., C:\Program Files, Windows registry, Windows services, Windows Server Backup, DPM, MARS agent, and commands like 'net start'). There is no mention of Linux equivalents, nor are there any examples or instructions for Linux-based systems. The documentation assumes the user is operating in a Windows ecosystem, with no guidance for Linux users.
Recommendations
  • Add troubleshooting steps and examples for Linux-based servers where Azure Backup Server or agents may be supported.
  • Include Linux file paths, service management commands (e.g., systemctl), and configuration file locations alongside Windows examples.
  • Provide guidance on configuring antivirus exclusions and backup settings for common Linux distributions.
  • Mention Linux equivalents for registry settings (e.g., configuration files or environment variables).
  • Clarify platform support at the beginning of the documentation and, if only Windows is supported, explicitly state this to avoid confusion.
  • If Linux is not supported, add a note to inform users and direct them to relevant Linux backup solutions.
GitHub Create Pull Request
Backup Private Endpoints Overview: Version 2 Experience ...icles/backup/backup-azure-private-endpoints-concept.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric backup tools (MARS agent, DPM, MABS) and scenarios. There are no explicit Linux backup agent examples, nor are Linux-specific patterns or tools mentioned. The focus is on workloads like SQL Server and SAP HANA in Azure VMs, but only Windows backup agents (MARS, DPM, MABS) are discussed in detail. No Linux command-line or agent instructions are provided, and the documentation does not clarify how private endpoints interact with Linux-based backup solutions.
Recommendations
  • Add explicit examples and instructions for configuring private endpoints with Linux-based backup agents (such as Azure CLI, azbackup, or third-party Linux backup tools).
  • Mention Linux VM scenarios and clarify how private endpoint connectivity works for Linux workloads, including any differences in DNS or agent setup.
  • Include parity in supported backup agents by listing Linux-compatible solutions and their requirements for private endpoint usage.
  • Provide sample configurations or troubleshooting steps for Linux environments, such as modifying /etc/hosts, using systemd-resolved, or integrating with custom DNS on Linux.
  • Ensure that references to tools and agents are balanced between Windows and Linux, and avoid assuming Windows-only environments.
GitHub Create Pull Request
Backup Troubleshoot System Center Data Protection Manager .../articles/backup/backup-azure-scdpm-troubleshooting.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 (e.g., net stop/start), and troubleshooting steps reference Windows tools, services, and concepts (such as NT AUTHORITY\SYSTEM and USN journal) without mention of Linux equivalents or cross-platform scenarios. There are no Linux-specific troubleshooting steps or examples, and Windows terminology is used exclusively and presented first.
Recommendations
  • If DPM or Azure Backup Server supports Linux workloads or agents, include troubleshooting steps and examples for Linux environments (e.g., service management via systemctl, Linux agent installation, file system considerations).
  • Explicitly state platform limitations at the top of the documentation if the product is Windows-only, to avoid confusion for Linux users.
  • Where possible, provide parity in error resolution steps for Linux-based backup agents or workloads, including relevant commands and log locations.
  • Mention and link to documentation for Linux backup solutions if DPM does not support Linux, to guide users to appropriate resources.
GitHub Create Pull Request
Backup Back up SQL Server databases to Azure ...blob/main/articles/backup/backup-azure-sql-database.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 biased towards Windows environments. All instructions, examples, and tooling references (such as SSMS, NT SERVICE accounts, Windows authentication, PowerShell scripts, and Windows file paths) are specific to Windows. There is no mention of Linux-based SQL Server VMs, nor any guidance for Linux authentication, file permissions, or command-line equivalents. The backup extension is named 'AzureBackupWindowsWorkload', and all operational steps assume a Windows OS, leaving Linux users without clear instructions.
Recommendations
  • Add explicit guidance for Linux-based SQL Server VMs, including any differences in extension installation, service accounts, and authentication.
  • Provide Linux-specific examples for setting SQL Server permissions (e.g., using sqlcmd or other CLI tools on Linux).
  • Include file path and permission instructions for Linux (e.g., using chmod/chown instead of Windows Security tab).
  • Offer Bash or shell script equivalents for PowerShell automation steps.
  • Clarify whether the AzureBackupWindowsWorkload extension is supported or available for Linux VMs, and if not, document alternatives.
  • Document any limitations or differences for SQL Server on Linux in Azure VMs, and link to relevant Linux documentation.
GitHub Create Pull Request
Backup Back Up and Restore Encrypted Azure VMs ...ob/main/articles/backup/backup-azure-vms-encryption.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides some parity between Windows and Linux in conceptual coverage, but exhibits bias in several areas. PowerShell is used as the only example for identifying a VM's associated key vault, with no equivalent Linux or Azure CLI example. Windows tooling (PowerShell) is mentioned before Linux alternatives, and there are no explicit Linux command-line examples. The documentation refers to Windows and Linux VMs in general, but practical steps and code samples favor Windows/PowerShell, leaving Linux users without direct guidance.
Recommendations
  • Add Azure CLI and/or Bash examples alongside PowerShell commands for key vault and VM operations.
  • When referencing command-line operations, present both Windows (PowerShell) and Linux (CLI/Bash) examples, or use Azure CLI as the default cross-platform tool.
  • Explicitly mention Linux-specific considerations or steps where relevant, especially in sections that currently only show Windows tooling.
  • Ensure screenshots and instructions do not assume a Windows-centric workflow (e.g., referencing PowerShell as the default).
  • Review related links and troubleshooting guides to ensure Linux scenarios are covered with equal depth.
GitHub Create Pull Request
Backup About agentless multi-disk crash-consistent backup for Azure Virtual Machines by using Azure Backup ...ure-vms-agentless-multi-disk-crash-consistent-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by mentioning Windows-specific backup mechanisms (VSS) before Linux equivalents (fsfreeze), and by linking only to Windows VM Agent and snapshot extension documentation. There are no Linux-specific examples, links, or tools referenced, and Linux backup patterns (such as pre/post scripts) are only mentioned in passing as a reason not to use crash-consistent backups.
Recommendations
  • Provide equal prominence to Linux backup mechanisms (e.g., link to documentation for fsfreeze and Linux VM Agent/extensions).
  • Include Linux-specific examples or scenarios, such as how crash-consistent backups interact with common Linux workloads.
  • Add links to Linux documentation for VM Agent and snapshot extensions, similar to the Windows links.
  • Clarify the behavior for Linux VMs in agentless backup scenarios, including any limitations or best practices.
  • List both Windows and Linux tools/patterns together when describing backup consistency mechanisms.
GitHub Create Pull Request
Backup Script Sample - Create a new or modify the current system state backup policy ...icles/backup/scripts/set-system-state-backup-policy.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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. There are no examples, instructions, or mentions of Linux or cross-platform alternatives. All tooling and scripting patterns are Windows-centric, and the guidance assumes a Windows environment from the outset.
Recommendations
  • Add equivalent examples or guidance for Linux systems, if supported, using Bash, Python, or other relevant scripting languages.
  • Clearly state platform limitations (e.g., if MARS agent is Windows-only) and provide links or references to Linux backup solutions if applicable.
  • Include a section comparing Windows and Linux backup policy management, highlighting differences and cross-platform considerations.
  • If Linux is not supported, explicitly mention this in the prerequisites or introduction to set expectations for cross-platform users.
GitHub Create Pull Request
Backup Soft delete for virtual machines ...b/main/articles/backup/soft-delete-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and cmdlets for managing soft delete operations, referencing Windows-centric tools and patterns, and omitting equivalent Linux CLI (Azure CLI, Bash) examples. The PowerShell workflow is described in detail, while no Linux-native or cross-platform command-line instructions are given. The ordering also places PowerShell before REST API, and there is no mention of Azure CLI or Bash scripting, which are commonly used on Linux and macOS.
Recommendations
  • Add equivalent Azure CLI examples for all operations (delete backup, undelete, resume backup) to ensure Linux and cross-platform parity.
  • Include Bash script snippets where appropriate, demonstrating how to interact with Azure Backup using REST API or Azure CLI.
  • Explicitly mention that all operations can be performed from Linux/macOS environments using Azure CLI or REST API.
  • Reorder sections so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell to avoid implicit prioritization of Windows tools.
  • Add a note clarifying tool availability and platform compatibility for each method.
GitHub Create Pull Request
Backup Upgrade the Microsoft Azure Recovery Services (MARS) agent for Azure Backup ...e-docs/blob/main/articles/backup/upgrade-mars-agent.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation exclusively describes upgrading the MARS agent on Windows environments, referencing Windows-specific tools (Remote Desktop, DPM Console, agent installer wizards) and omitting any mention of Linux systems, commands, or upgrade procedures. All examples, screenshots, and next steps are Windows-centric, with no Linux parity or cross-platform guidance.
Recommendations
  • Clarify in the introduction whether the MARS agent is Windows-only, or explicitly state platform limitations.
  • If Linux support exists, add equivalent Linux upgrade instructions, including command-line examples (e.g., Bash, SSH, package managers).
  • Include Linux-specific troubleshooting steps, firewall configuration, and agent version discovery methods.
  • Provide parity in screenshots and step-by-step guides for Linux environments.
  • If the agent is not available for Linux, add a note explaining this to avoid confusion for cross-platform administrators.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the method to recreate VMs after restoring encrypted disks, and by linking only to Windows-specific encrypted VM documentation (including Microsoft Entra ID scenarios). There are no Linux-specific examples, instructions, or links for restoring encrypted Linux VMs, nor are Linux tools or command-line patterns mentioned. The restore process for encrypted VMs is described only for Windows, and PowerShell is presented as the default tool.
Recommendations
  • Add equivalent instructions and examples for restoring encrypted Linux VMs, including references to Linux-specific documentation.
  • Mention and provide examples using Linux command-line tools (such as Azure CLI or Bash scripts) for VM recreation after disk restore.
  • Ensure that links to encrypted VM restore scenarios include both Windows and Linux guides.
  • Avoid presenting Windows/PowerShell as the only or primary method; instead, provide parity by listing Linux methods alongside Windows methods.
  • Clarify in each scenario whether the instructions apply to both Windows and Linux VMs, or provide separate sections for each OS.
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: 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 oriented toward Windows environments, specifically Windows Server domain controllers. All examples and procedures reference Windows tools (PowerShell, ntdsutil.exe), Windows-specific concepts (Directory Services Restore Mode, tombstone lifetime for Windows Server), and do not mention or provide guidance for Linux-based domain controllers or cross-platform scenarios. The documentation assumes the use of Windows Server and does not offer Linux equivalents, examples, or considerations.
Recommendations
  • Explicitly state that the guidance is for Windows-based Active Directory and clarify whether Azure Backup supports Linux-based domain controllers (such as Samba AD DC).
  • If Linux-based Active Directory domain controllers (e.g., Samba) are supported, provide equivalent backup and restore procedures, including Linux command-line examples and tools.
  • Include a section comparing Windows and Linux domain controller backup/restore scenarios, highlighting any differences and limitations.
  • Mention cross-platform considerations for hybrid environments where both Windows and Linux domain controllers may exist.
  • If Linux is not supported, add a note explaining this and suggest alternative backup strategies for Linux-based AD environments.
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: 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 lists PowerShell as a supported client before CLI, and provides no explicit Linux or cross-platform examples. The only command-line interface mentioned by name is PowerShell, which is Windows-centric, while the Azure CLI (which is cross-platform) is listed after PowerShell. There are no Linux-specific instructions, screenshots, or examples, and no mention of Bash or Linux tools. This suggests a Windows-first and PowerShell-heavy bias, with missing Linux parity in examples and guidance.
Recommendations
  • Provide explicit Linux/Bash/Azure CLI examples alongside or before PowerShell examples, ensuring parity.
  • Include screenshots or walkthroughs using Azure CLI on Linux or macOS, not just the Azure portal or PowerShell.
  • Clarify that Azure CLI is cross-platform and provide links or instructions for Linux users.
  • If there are any differences in behavior or prerequisites on Linux, document them clearly.
  • Consider reordering the 'Supported clients' section to list Azure CLI before PowerShell, or group them together as 'Command-line tools'.
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: 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 consistently mentioning PowerShell first when listing automation methods and in scenario explanations. Practical examples and workflow descriptions focus on PowerShell and Azure Automation Runbooks, with no explicit Linux shell (Bash) or cross-platform CLI examples provided. While Azure CLI is mentioned, there are no concrete Bash/Linux shell command examples, and the automation scenarios default to Windows-centric tools and patterns.
Recommendations
  • Provide explicit Bash/Linux shell examples alongside or before PowerShell examples in all automation scenarios.
  • When listing automation methods, alternate the order or list CLI/Bash before PowerShell to avoid Windows-first bias.
  • Include sample scripts and workflows using Azure CLI in Bash for common tasks such as configuring backups, exporting data, and automating responses.
  • Highlight cross-platform tools (e.g., Ansible, Terraform) with practical Linux-based examples, not just links.
  • Clarify that all automation methods are supported on both Windows and Linux, and add notes or sections for Linux users where appropriate.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The Azure Backup glossary page demonstrates a Windows bias in several ways. Windows-specific technologies and tools (such as VSS, DPM, MABS, MARS agent, System State backup, and references to Windows clients) are mentioned frequently and often before or instead of Linux equivalents. The only explicit mention of Linux is in the context of application-consistent backups, where 'pre or post scripts for Linux' is briefly noted, but no further detail or links are provided. There are references to Azure PowerShell and ARM templates, but Linux-native tools or workflows are not highlighted. There are no Linux-specific backup scenarios, tools, or examples, and the glossary omits terms or links relevant to Linux backup practices.
Recommendations
  • Add Linux-specific backup terms and scenarios, such as describing how Azure Backup interacts with Linux VMs, file systems, and application consistency (e.g., pre/post scripts, fsfreeze, etc.).
  • Provide equal detail and links for Linux backup mechanisms as are given for Windows (e.g., link to documentation on Linux application-consistent backups, Linux agent installation, and recovery processes).
  • Include references to Linux-native tools and commands where relevant, and ensure that examples and explanations are not Windows-centric.
  • When describing features like VSS, also mention and link to Linux equivalents or approaches, and avoid presenting Windows tools first or exclusively.
  • Add glossary entries for Linux-specific backup agents, scripts, or integration points if applicable.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-data-lake-storage-backup-configure-quickstart-arm-bicep.md ...ata-lake-storage-backup-configure-quickstart-arm-bicep.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides only PowerShell-based deployment instructions for both ARM and Bicep templates, specifically referencing Azure Cloud Shell and the New-AzResourceGroupDeployment cmdlet. There are no examples using Azure CLI, Bash, or Linux-native tooling. The deployment steps are written with a Windows/PowerShell-first perspective, and there is no mention of Linux or cross-platform alternatives.
Recommendations
  • Add Azure CLI (az deployment group create) examples for deploying both ARM and Bicep templates, alongside or before PowerShell examples.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide Bash/CLI instructions.
  • Ensure that all scripts and commands are cross-platform or provide platform-specific alternatives (e.g., Bash for Linux/macOS, PowerShell for Windows).
  • Update the documentation to avoid implying PowerShell is the default or only supported method for deployment.
  • Where possible, use generic terms like 'run the following command' instead of 'run the following PowerShell script', unless only PowerShell is supported.
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: 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 references PowerShell and the Azure portal as primary configuration methods, with only a brief mention of Azure CLI. There are no explicit Linux or cross-platform command examples, and the ordering of tools (Azure portal, PowerShell, then Azure CLI) suggests a Windows-first bias. No Linux-specific tools, shell commands, or considerations are provided.
Recommendations
  • Provide explicit, step-by-step examples using Azure CLI for all major operations (configuration, restore, management), and ensure these are presented alongside or before PowerShell examples.
  • Include Linux/macOS shell command examples where relevant, especially for scripting or automation scenarios.
  • Reorder tool mentions to avoid always listing PowerShell before Azure CLI; consider grouping Azure CLI and PowerShell together as 'command-line options' or alternating their order.
  • Add a section or notes highlighting parity and any differences between Windows and Linux environments for backup operations.
  • Ensure that screenshots, code snippets, and troubleshooting steps are platform-agnostic or include both Windows and Linux variants.
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: 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 exhibits subtle Windows bias. In the 'Next steps' section, Azure PowerShell is listed before Azure CLI for backup operations, and both backup and restore examples reference PowerShell, which is more commonly used on Windows. There are no explicit Linux shell (bash) or cross-platform command-line examples, and no mention of Linux-specific tools or patterns. The documentation assumes use of the Azure portal and PowerShell, which may not be the primary tools for Linux users. There are no explicit bash or shell script examples, and the documentation does not clarify cross-platform parity for command-line operations.
Recommendations
  • Ensure all command-line examples are provided for both Azure CLI (bash/shell) and Azure PowerShell, with CLI examples listed first or equally.
  • Explicitly mention that all operations can be performed from Linux, macOS, or Windows, and clarify any platform-specific requirements.
  • Add bash/shell script examples for common operations (e.g., installing the Backup Extension, enabling Trusted Access) alongside PowerShell examples.
  • Where the Azure portal is referenced, clarify that it is web-based and platform-agnostic.
  • Review the order of tool mentions in the 'Next steps' section to avoid implying Windows-first workflows.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-backup.md ...cles/backup/azure-kubernetes-service-cluster-backup.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 Azure PowerShell as the only CLI alternative to the portal, both in the introduction and in the 'Next steps' section. There are no examples or instructions for using Azure CLI, Bash, or Linux-native tools for AKS backup configuration or management. The documentation does not mention or provide parity for Linux users, who typically use Azure CLI and Bash scripts for automation.
Recommendations
  • Add Azure CLI examples for all backup and restore operations, including installation of the Backup extension, creation of Backup vaults, policies, and backup configuration.
  • Reference Azure CLI as an alternative to PowerShell in the introduction and 'Next steps' sections, ensuring both Windows and Linux users are addressed.
  • Include Bash script samples for deploying backup hooks and managing AKS backups, in addition to the existing kubectl example.
  • Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux environments.
  • Ensure screenshots and instructions do not assume use of Windows-only tools or UI patterns.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented towards Windows environments. All instructions, terminology, and referenced tools (e.g., MABS console, Volume Shadow Copy Service, Data Deduplication, SAN hardware snapshots) are Windows-specific. There are no examples, instructions, or notes for Linux systems, nor any mention of Linux client support, agent installation, or recovery scenarios. This creates a strong Windows bias and leaves Linux administrators without guidance.
Recommendations
  • Add explicit sections or notes describing support for Linux machines, including any limitations or prerequisites.
  • Provide step-by-step examples for backing up and recovering file data from Linux servers/clients, including agent installation and configuration.
  • Mention Linux-specific considerations (e.g., supported file systems, required packages, SELinux/AppArmor notes, etc.).
  • If Linux is not supported, clearly state this early in the prerequisites.
  • Reference Linux equivalents for Windows features (e.g., alternatives to VSS, deduplication, etc.), or clarify if such features are unavailable.
  • Include screenshots or CLI examples relevant to Linux where applicable.
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: 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 page exhibits a strong Windows bias. Backup scenarios and tooling are described primarily for Windows environments, with the MARS agent and DPM/MABS servers only supporting Windows. Linux support is either absent or mentioned only to note its lack of support. Examples, agent descriptions, and architecture diagrams focus on Windows tools and workflows, with no equivalent Linux guidance or parity in backup methods for on-premises machines.
Recommendations
  • Add explicit sections describing backup options for on-premises Linux machines, including supported agents, workflows, and limitations.
  • If Linux is not supported for certain backup scenarios (e.g., MARS agent), clarify alternative solutions or recommend third-party/complementary Azure services for Linux backup.
  • Provide Linux-centric examples and diagrams where applicable, such as backup of Azure Linux VMs, and ensure parity in feature tables.
  • Mention Linux tools and patterns (e.g., CLI commands, cron-based scheduling, integration with native Linux backup utilities) alongside Windows/Powershell equivalents.
  • Review all 'next steps' and scenario lists to include Linux-focused guidance and links, not just Windows and Windows-centric tools.
GitHub Create Pull Request
← Previous Page 6 of 21 Next →