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 726-750 of 1604 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-sql-backup.md ...-docs/blob/main/articles/backup/tutorial-sql-backup.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 oriented toward SQL Server running on Windows-based Azure VMs. It exclusively references Windows-specific tools and patterns, such as the 'AzureBackupWindowsWorkload' extension, NT Service accounts, and SQLIaaSExtension, with no mention of Linux-based SQL Server deployments. There are no examples or instructions for backing up SQL Server on Linux VMs, nor any references to Linux-specific prerequisites, extensions, or service accounts. The guidance assumes a Windows environment throughout.
Recommendations
  • Add explicit support and instructions for SQL Server running on Linux Azure VMs, including prerequisites, extension installation, and service account setup.
  • Provide Linux-specific examples and screenshots for backup configuration steps.
  • Clarify which steps and features are Windows-only and which are supported on Linux, including any limitations or differences.
  • Mention Linux equivalents for service accounts and extensions, or note if certain features are unavailable on Linux.
  • Include troubleshooting guidance for common Linux-specific issues (e.g., permissions, extension compatibility).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/troubleshoot-azure-files.md .../blob/main/articles/backup/troubleshoot-azure-files.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell scripts for key troubleshooting tasks (such as finding Recovery Services vaults and undeleting file shares), without providing equivalent CLI or Bash examples for Linux users. The scripts and automation guidance are Windows-centric, and there is no mention of Linux tools or cross-platform alternatives. This may hinder Linux administrators from efficiently performing the same operations.
Recommendations
  • Provide Azure CLI or Bash script equivalents for all referenced PowerShell scripts, and link to them alongside the PowerShell options.
  • Explicitly mention that troubleshooting steps can be performed on Linux and macOS, and provide platform-agnostic instructions where possible.
  • Add examples using Azure CLI for common tasks such as vault discovery and file share undeletion.
  • Review all automation/script references to ensure Linux parity and cross-platform accessibility.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-postgresql-backup.md ...lob/main/articles/backup/tutorial-postgresql-backup.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates bias toward Windows by primarily referencing PowerShell scripts for privilege assignment and not providing equivalent Linux/Unix command examples. The only explicit script-based example is PowerShell, and while alternatives like PG admin or PSQL are mentioned, they are not documented or exemplified. This prioritizes Windows tooling and patterns, leaving Linux users with less guidance.
Recommendations
  • Provide explicit examples using Linux/Unix command-line tools (e.g., psql) for granting database privileges.
  • Include step-by-step instructions for using pgAdmin and psql alongside PowerShell, ensuring parity.
  • Add screenshots or terminal output for Linux-based workflows where appropriate.
  • Clarify that PowerShell scripts can be run on Linux (via PowerShell Core), or offer native Bash alternatives.
  • Reorder sections to present platform-neutral or Linux options before or alongside Windows/PowerShell instructions.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/upgrade-mars-agent.md ...e-docs/blob/main/articles/backup/upgrade-mars-agent.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 exclusively describes upgrading the MARS agent on Windows environments, referencing Windows-specific tools (Remote Desktop, DPM Console) and providing no guidance or examples for Linux systems. All screenshots and instructions assume a Windows OS, and there is no mention of Linux compatibility or alternative upgrade procedures.
Recommendations
  • Clarify whether the MARS agent is Windows-only or provide explicit Linux support status.
  • If Linux is supported, add equivalent upgrade instructions for Linux systems, including command-line examples (e.g., Bash, SSH) and package management steps.
  • Mention Linux tools and workflows where appropriate, such as using SCP/SFTP for file transfer, SSH for remote access, and Linux package managers for installation.
  • Add screenshots or terminal output examples for Linux environments.
  • Ensure parity in troubleshooting and firewall configuration guidance for Linux systems.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/use-archive-tier-support.md .../blob/main/articles/backup/use-archive-tier-support.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 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. The Azure portal and PowerShell (Windows-native) are presented before CLI (cross-platform), and all code examples for scripting and automation use PowerShell or Azure CLI, with no mention of Linux-native tools or shell scripting. The 'Get started' sections for PowerShell include instructions for downloading PowerShell from GitHub, which is primarily a Windows tool, and the portal instructions assume a GUI workflow typical of Windows environments. There are no Linux-specific examples, nor are Linux shell commands (bash, zsh) or automation patterns (cron, systemd) discussed. The documentation assumes familiarity with Windows/PowerShell paradigms and does not address Linux user needs directly.
Recommendations
  • Add Linux-specific examples, such as bash scripts for automation, and reference Linux-native tools where applicable.
  • Explicitly mention cross-platform compatibility for CLI commands and clarify any differences in usage or prerequisites on Linux vs Windows.
  • Include instructions for integrating archive tier operations into Linux automation workflows (e.g., cron jobs, systemd timers).
  • Provide troubleshooting and environment setup guidance for Linux users, including package installation and environment variables.
  • Balance the order of presentation so that CLI and Linux-friendly approaches are not always after Windows/PowerShell examples.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/about-restore-microsoft-azure-recovery-services.md ...kup/about-restore-microsoft-azure-recovery-services.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 for Microsoft Azure Recovery Services (MARS) agent demonstrates a clear Windows bias. All restore options and examples are focused exclusively on Windows environments, referencing Windows Server System State, PowerShell for automation, and Windows-specific tools like robocopy. There is no mention of Linux support, Linux restore scenarios, or equivalent Linux tools or commands. The documentation assumes the reader is using Windows, with no guidance for Linux users.
Recommendations
  • Clarify platform support for the MARS agent, explicitly stating whether Linux is supported or not.
  • If Linux is supported, provide equivalent restore instructions, examples, and automation scripts for Linux environments (e.g., using Bash, rsync, cp, etc.).
  • Include Linux-specific prerequisites and troubleshooting steps.
  • If MARS agent is Windows-only, add a prominent note at the beginning of the documentation to inform users and suggest alternative Azure backup solutions for Linux.
  • Ensure parity in tool recommendations by mentioning Linux equivalents (e.g., use rsync for multi-threaded copy on Linux instead of robocopy).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/back-up-managed-disks-tutorial.md ...main/articles/backup/back-up-managed-disks-tutorial.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 primarily focuses on using the Azure portal for backup operations, which is platform-agnostic. However, when scripting or automation is mentioned, PowerShell is listed before Azure CLI, and there are no explicit Linux-specific examples or references. The scripting guidance leans toward Windows/PowerShell, and Linux parity is not emphasized.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform and widely used on Linux.
  • Explicitly mention Linux compatibility and provide examples or screenshots from Linux environments where applicable.
  • Include references to Bash scripting or automation for Linux users.
  • Clarify that all operations can be performed from Linux, macOS, or Windows, and provide guidance for each where differences exist.
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: 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 provides only PowerShell deployment examples for both ARM and Bicep templates, with instructions to run them in Azure Cloud Shell. There are no examples or instructions for deploying using Azure CLI, Bash, or other Linux-native tools. This approach prioritizes Windows-centric tooling and omits Linux parity, potentially disadvantaging users on Linux or macOS who prefer Bash or Azure CLI.
Recommendations
  • Add Azure CLI deployment examples for both ARM and Bicep templates, showing equivalent commands for template deployment.
  • Include Bash script examples for template deployment, especially for users who prefer Bash in Cloud Shell or on Linux/macOS.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide guidance for both.
  • Where possible, avoid language or instructions that imply PowerShell is the default or only supported method.
  • Consider a 'Platform parity' section that lists all supported deployment methods (PowerShell, Azure CLI, Bash, etc.) and links to relevant documentation.
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: 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 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 mentions of Azure CLI, Bash, or Linux-native tools for managing AKS backups. All command-line references are generic (kubectl) or PowerShell, with no Linux-specific guidance or parity. This may disadvantage users on Linux or those preferring cross-platform CLI solutions.
Recommendations
  • Add Azure CLI examples for all backup and restore operations, alongside or before PowerShell examples.
  • Explicitly mention cross-platform compatibility for command-line steps, including Bash and Linux environments.
  • Where PowerShell is referenced, provide equivalent Azure CLI commands and links.
  • Include screenshots or instructions for Linux environments (e.g., Ubuntu terminal) where appropriate.
  • Review all references to ensure Linux and macOS users are equally supported and not required to use Windows-specific tools.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-data-protection-use-rest-api-create-update-postgresql-policy.md ...rotection-use-rest-api-create-update-postgresql-policy.md
High Priority View Details →
Scanned: 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 Windows bias by referencing PowerShell objects as the default way to conceptualize and configure backup policies for PostgreSQL in Azure. It repeatedly mentions 'PowerShell object' as the canonical example, without providing equivalent Linux or cross-platform CLI (such as Azure CLI or Bash/cURL) examples. No Linux-specific tools, shell commands, or cross-platform scripting patterns are presented, and the only concrete examples are REST API payloads and PowerShell-centric descriptions.
Recommendations
  • Replace or supplement references to 'PowerShell object' with cross-platform alternatives, such as Azure CLI, Bash, or cURL commands.
  • Provide example workflows for Linux users, including shell scripts or Azure CLI commands to create and manage backup policies.
  • Clarify that the REST API can be used from any platform, and provide sample requests using tools available on Linux (e.g., cURL, httpie).
  • Avoid positioning PowerShell as the default or only way to interact with the API; instead, present platform-neutral approaches first.
  • Add a section explicitly addressing Linux and macOS usage, including environment setup and authentication steps for those platforms.
GitHub Create Pull Request
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-08 00:53
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 Data Protection Manager (DPM), which is a Windows-only backup tool. All examples, screenshots, and instructions assume the use of Windows Server, Windows-based SQL Server, and DPM. There are no references to Linux-based SQL Server, Linux backup tools, or cross-platform alternatives. The related content and automation references are PowerShell-centric, further reinforcing Windows bias.
Recommendations
  • Include guidance for backing up SQL Server running on Linux, using Azure Backup or other supported tools.
  • Provide examples and screenshots for Linux environments, such as using CLI tools or native Linux backup utilities.
  • Mention cross-platform alternatives to DPM, or clarify DPM's Windows-only scope early in the article.
  • Add references to automation via Bash scripts or Azure CLI, not just PowerShell.
  • Explicitly state platform limitations and link to Linux-specific documentation where applicable.
GitHub Create Pull Request
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-08 00:53
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 System Center DPM and Microsoft Exchange, both of which are Windows-only products. All instructions, examples, and screenshots reference Windows tools, paths (e.g., C:\Program Files), and GUI workflows. There are no Linux equivalents or alternative instructions for non-Windows platforms. PowerShell is referenced in related content, with no mention of Bash or Linux command-line tools.
Recommendations
  • Clarify early in the documentation that DPM and Exchange are Windows-only, and explicitly state platform limitations.
  • If possible, provide guidance or links for backing up Exchange on Linux (if supported in future versions) or for backing up other workloads on Linux using Azure Backup.
  • Include parity documentation for Azure Backup scenarios on Linux servers, using Linux-native tools and command-line examples.
  • Reference cross-platform automation options (e.g., REST API, Azure CLI) alongside PowerShell.
  • Add a section comparing Windows and Linux backup workflows, even if only to state that DPM is not available for Linux, and suggest alternatives.
GitHub Create Pull Request
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-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 is heavily oriented toward Windows environments, with all installation and operational instructions focused on Windows Server (including Azure VMs running Windows), exclusive use of Windows tools (e.g., PowerShell cmdlets, registry edits), and no mention of Linux support or examples. The documentation assumes the use of Windows-specific features and does not provide parity for Linux administrators or environments.
Recommendations
  • Explicitly state whether Linux is supported or not, and if not, provide guidance or alternatives for Linux workloads.
  • If Linux support is possible, add installation, configuration, and operational instructions for Linux environments, including examples using Linux tools and commands.
  • Include parity in troubleshooting, backup, and restore procedures for Linux systems if supported.
  • Mention cross-platform considerations early in the documentation, and avoid assuming Windows as the default unless it is a strict requirement.
  • If only Windows is supported, clarify this limitation prominently at the start of the documentation.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-restore-disks.md ...backup-azure-dataprotection-use-rest-api-restore-disks.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 mentioning Windows-centric tools (Azure PowerShell) before Linux equivalents (Azure CLI), and by referencing the Azure portal and PowerShell as primary restore methods. No Linux-specific examples, shell commands, or guidance are provided for Linux users. All examples are either REST API calls or reference PowerShell/portal documentation, with no parity for Linux command-line usage.
Recommendations
  • Mention Azure CLI before or alongside Azure PowerShell when listing restore options.
  • Provide explicit Linux shell (bash) examples for REST API calls, such as using curl or az CLI.
  • Include references to Linux documentation or workflows where applicable.
  • Ensure that all steps and prerequisites are platform-neutral or have clear Linux alternatives.
  • Add a section or note for Linux users on how to perform the same operations using bash/CLI.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-troubleshoot-slow-backup-performance-issue.md ...ackup-azure-troubleshoot-slow-backup-performance-issue.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 strong Windows bias. All troubleshooting steps, tools, and examples are specific to Windows environments. Only Windows tools (such as Performance Monitor) are mentioned, and all file paths, agent references, and troubleshooting advice assume a Windows system. There are no Linux equivalents, examples, or even a mention of Linux support or differences.
Recommendations
  • Add a section clarifying whether the Azure Backup agent and guidance applies to Linux systems, or explicitly state if it is Windows-only.
  • If Linux is supported, provide equivalent troubleshooting steps and examples for Linux environments (e.g., using iostat, vmstat, sar for performance monitoring).
  • Include Linux file paths and log locations, if applicable.
  • Mention Linux-specific considerations for antivirus/process interference and VM performance.
  • Where Windows tools are referenced (such as Performance Monitor), provide Linux alternatives and example commands.
  • Ensure parity in recommendations and troubleshooting steps for both Windows and Linux users.
GitHub Create Pull Request
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-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 troubleshooting System Center Data Protection Manager (DPM), a Microsoft product that is only available for Windows. All examples, commands, and troubleshooting steps reference Windows-specific tools (e.g., 'net stop dpmra'), Windows services, and concepts (e.g., NT AUTHORITY\SYSTEM, MARS agent, USN journal). There are no Linux equivalents, examples, or mentions of cross-platform scenarios. The documentation assumes the reader is using Windows and does not address Linux environments.
Recommendations
  • Explicitly state that DPM is a Windows-only product at the beginning of the documentation to clarify platform scope.
  • If any components (such as Azure Backup agent) support Linux, provide troubleshooting steps and examples for Linux environments.
  • Where possible, mention alternatives for Linux backup and recovery (e.g., Azure Backup for Linux VMs) and link to relevant documentation.
  • Avoid using Windows-specific terminology (e.g., NT AUTHORITY\SYSTEM, USN journal) without clarifying platform applicability.
  • Consider adding a section that discusses cross-platform backup strategies and how DPM fits into a heterogeneous environment.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-managed-disks-cli.md .../blob/main/articles/backup/backup-managed-disks-cli.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 moderate Windows bias. While the main backup workflow uses Azure CLI (which is cross-platform), several patterns and examples use Windows-centric conventions. Notably, variable assignment in CLI examples uses PowerShell syntax (e.g., $DiskId = ...), which does not work in Bash or Linux shells. References to PowerShell and Azure portal are present, but there are no explicit Linux/Bash equivalents or clarifications. The documentation does not provide Linux-specific notes or examples, and variable assignment is shown only in Windows/PowerShell style.
Recommendations
  • Replace PowerShell-style variable assignment (e.g., $DiskId = ...) with Bash-compatible syntax (e.g., DiskId=...) or provide both versions.
  • Add explicit notes or examples for Linux/Bash users, especially for steps involving variable assignment and file redirection.
  • Where Azure PowerShell is referenced (e.g., in Next Steps), ensure parity by also referencing Bash/CLI alternatives.
  • Clarify that all Azure CLI commands are cross-platform and provide any necessary shell-specific guidance.
  • Avoid using Windows-centric conventions (such as $variable) in CLI documentation unless both platforms are covered.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-center-overview.md ...cs/blob/main/articles/backup/backup-center-overview.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 Tools Missing Linux Example
Summary
The documentation page references PowerShell scripts and Microsoft Database Backup scripts as sample automation resources, but does not mention or provide parity for Linux-native tools or scripting languages (such as Bash or Python). There are no explicit Linux examples or references to Linux-specific backup patterns, and the automation samples are Windows-centric. This suggests a bias toward Windows tooling and automation, with Linux alternatives missing.
Recommendations
  • Include sample Bash scripts and Linux CLI commands alongside PowerShell examples in the Community Hub and documentation.
  • Reference Linux-native backup tools or scripting patterns (e.g., cron jobs, shell scripts) where automation is discussed.
  • Explicitly mention Linux support and provide examples for managing backups of Linux VMs and workloads.
  • Ensure documentation for automated deployments covers both Windows and Linux environments, with clear instructions and samples for each.
  • Add links to Linux-focused community resources and forums relevant to Azure Backup.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-the-mabs-server.md ...cs/blob/main/articles/backup/backup-the-mabs-server.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 for backing up the Microsoft Azure Backup Server (MABS) is heavily biased toward Windows environments. All examples, tools, and procedures reference Windows-specific utilities (e.g., PowerShell, mountvol.exe, diskshadow.exe, psexec.exe, Net Share), Windows file paths, and Windows-only features like Previous Versions. There are no Linux equivalents or cross-platform alternatives provided, and all instructions assume the administrator is working on Windows. Even cloud backup and SQL Server backup examples are framed in a Windows context.
Recommendations
  • Explicitly state platform requirements and limitations at the beginning of the documentation.
  • If MABS is Windows-only, clarify this and explain why Linux alternatives are not supported.
  • Where possible, provide guidance or references for similar backup strategies on Linux (e.g., using native SQL Server on Linux, Azure Backup Agent for Linux, or alternative backup tools).
  • Include notes or links to documentation for cross-platform SQL Server backup and restore procedures.
  • If any part of the process can be performed from a Linux system (e.g., accessing Azure Backup vaults, managing SQL backups), provide Linux command-line examples (e.g., using sqlcmd, az CLI, or SMB/CIFS mounting).
  • Avoid using Windows-specific tools (like mountvol.exe, diskshadow.exe, psexec.exe, Net Share) without mentioning that these are not available on Linux, and suggest alternatives if possible.
  • Add a section summarizing platform support and explicitly noting the lack of Linux support if applicable.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-instant-restore-capability.md ...n/articles/backup/backup-instant-restore-capability.md
High Priority View Details →
Scanned: 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 provides configuration instructions for Azure Instant Restore using the Azure portal and PowerShell, but does not mention or provide examples for Linux command-line tools (such as Azure CLI or Bash scripting). PowerShell is featured as the only scripting method, which is primarily associated with Windows environments, and there are no Linux-specific instructions or parity in example commands.
Recommendations
  • Add Azure CLI examples for configuring snapshot retention and other backup policy settings, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that PowerShell commands can be run on Linux and macOS, or provide links to relevant setup guides for non-Windows platforms.
  • Include Bash script examples or guidance for users who prefer shell scripting on Linux.
  • Ensure that any references to tools or configuration steps do not assume a Windows environment by default, and present cross-platform options side-by-side.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-whats-new-mabs.md ...lob/main/articles/backup/backup-mabs-whats-new-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 Powershell Heavy
Summary
The documentation for Microsoft Azure Backup Server (MABS) is heavily focused on Windows environments, with repeated references to Windows Server, Windows-based workloads, and Windows-specific tools (such as PowerShell and registry keys). There are no examples or guidance for Linux workloads, Linux-based backup scenarios, or Linux tools. Features and supportability tables consistently mention Windows first or exclusively, and configuration instructions rely on Windows patterns (registry keys, PowerShell cmdlets) without Linux alternatives.
Recommendations
  • Add explicit Linux workload support information, including which Linux distributions and versions are supported for backup and recovery.
  • Provide Linux-specific examples for backup, recovery, and configuration tasks, such as using shell scripts, cron jobs, or Linux-native tools.
  • Include parity in feature tables, indicating whether features apply to Linux VMs or workloads, and call out any differences.
  • Offer guidance for Linux administrators, such as installation steps, troubleshooting, and best practices for Linux environments.
  • If registry keys or PowerShell cmdlets are required for configuration, provide equivalent instructions for Linux (e.g., config files, CLI commands).
  • Mention Linux support in introductory and summary sections to clarify cross-platform capabilities.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-server-previous-versions.md ...cles/backup/offline-backup-server-previous-versions.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 is heavily oriented toward Windows environments, with all examples, tools, and workflows described for Windows Server, Windows clients, DPM, and MABS. There are no Linux equivalents or examples, and all utilities and registry operations are Windows-specific. The use of Windows command prompt, registry editing, and references to Windows-only tools and consoles further reinforce the Windows bias.
Recommendations
  • Add explicit statements about Linux support or limitations for DPM/MABS and Azure Backup workflows.
  • If Linux support exists, provide equivalent Linux command-line examples and workflows, including how to prepare disks, interact with Azure Import/Export, and manage certificates.
  • Mention and document any Linux-compatible tools or scripts for offline backup, or clarify if none exist.
  • Include screenshots and instructions for Linux environments where applicable, such as using shell commands, mounting disks, and interacting with Azure services.
  • If the workflow is Windows-only, state this clearly at the beginning and suggest alternative solutions for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-database-portal.md ...cles/backup/quick-backup-postgresql-database-portal.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 page demonstrates a Windows bias by primarily referencing PowerShell scripts for privilege assignment and automation, mentioning PowerShell before alternatives like PG admin or PSQL, and lacking explicit Linux or cross-platform CLI examples. There are no bash, shell, or Linux-native tool instructions, and PowerShell is presented as the default automation method.
Recommendations
  • Provide equivalent examples using Linux-native tools such as bash scripts, psql CLI, and PG admin for privilege assignment and automation.
  • Explicitly mention cross-platform options and clarify that steps can be performed on both Windows and Linux environments.
  • Include sample commands for Linux users (e.g., using psql to grant privileges) alongside PowerShell scripts.
  • Ensure that references to PowerShell are balanced with references to Linux tools, and avoid presenting Windows tooling as the default or only option.
  • Add screenshots or instructions for Linux environments where relevant, especially for command-line operations.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/monitoring-and-alerts-overview.md ...main/articles/backup/monitoring-and-alerts-overview.md
High Priority View Details →
Scanned: 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 by consistently listing Windows-centric tools (PowerShell) before cross-platform alternatives (CLI, REST API), referencing Windows-specific backup agents (Azure Backup Agent, DPM, Azure Backup Server) without Linux equivalents, and omitting explicit Linux usage examples or guidance. While Azure CLI and REST API are mentioned, there are no Linux-specific instructions, examples, or references to Linux-native backup agents or tools. The documentation implicitly assumes a Windows-first environment for monitoring and reporting Azure Backup, which may disadvantage Linux administrators.
Recommendations
  • Provide explicit Linux usage examples for monitoring and reporting tasks, such as using Azure CLI on Linux shells (bash, zsh) and scripting with curl for REST API calls.
  • List cross-platform tools (CLI, REST API) before or alongside Windows-specific tools (PowerShell) when describing interfaces and automation options.
  • Reference Linux-native backup agents or clarify the support for Linux workloads where applicable, including any differences in monitoring or alerting.
  • Include troubleshooting and reporting scenarios relevant to Linux-based environments, such as integration with Linux syslog or native notification systems.
  • Ensure documentation language and examples are inclusive of both Windows and Linux administrators, avoiding implicit prioritization of Windows tools.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-azure-files-vault-tier-terraform.md ...ackup/quick-backup-azure-files-vault-tier-terraform.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-first bias by mentioning Azure PowerShell alongside Azure CLI for authentication, despite Terraform only supporting Azure CLI authentication. There are no explicit Linux or cross-platform shell examples, and PowerShell is referenced multiple times (including in 'Next steps') before or alongside CLI, with no mention of Bash or Linux-specific workflows. This may cause confusion for Linux users and does not provide parity in guidance.
Recommendations
  • Remove references to Azure PowerShell in authentication steps, or clarify that only Azure CLI is supported for Terraform authentication.
  • Add explicit Linux/Bash shell command examples where relevant (e.g., directory creation, file editing), or clarify that all CLI commands are cross-platform.
  • When listing tools or next steps, alternate the order or explicitly mention both Windows (PowerShell) and Linux (Bash/CLI) options, or group them under 'Command-line options' instead of listing PowerShell first.
  • Include a note or section for Linux/macOS users, confirming that all steps are supported and providing any OS-specific tips if needed.
  • Ensure that all command-line examples use syntax that works on all platforms, or provide both Windows and Linux variants if differences exist.
GitHub Create Pull Request
← Previous Page 30 of 65 Next →