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 501-520 of 520 flagged pages
Backup Create backup policies for Azure database for PostgreSQL - Flexible server using data protection REST API in Azure Backup ...base-postgresql-flex-use-rest-api-create-update-policy.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy
Summary
The documentation page contains a reference to the 'default PowerShell object' for PostgreSQL - Flexible servers, suggesting PowerShell as the default or primary automation tool. There are no Linux/macOS-specific examples, nor is there mention of equivalent Linux tools or command-line patterns (such as curl, jq, or bash scripting). The REST API usage is platform-agnostic, but the only tool explicitly referenced is PowerShell, which is primarily associated with Windows environments.
Recommendations
  • Replace or supplement references to 'default PowerShell object' with platform-neutral terminology (e.g., 'default REST API object').
  • Add example commands for creating backup policies using common Linux/macOS tools such as curl and jq.
  • Clarify that the REST API can be used from any OS and provide sample workflows for Linux/macOS users.
  • Avoid implying PowerShell is the default or only supported method; mention cross-platform alternatives.
  • If scripting examples are provided, show both PowerShell and bash/curl equivalents.
GitHub Create Pull Request
Backup Back up Azure Disks using Azure Data Protection REST API. ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-disks.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation is largely platform-neutral, focusing on REST API calls and HTTP requests, which are usable from any OS. However, there is a minor Windows bias in the 'Next steps' section, where 'Azure PowerShell' is listed before 'Azure CLI' as a method for restoring managed disks. No PowerShell-specific examples or Windows-only tools are present in the main content, and all examples use HTTP requests and JSON payloads.
Recommendations
  • List Azure CLI before Azure PowerShell in 'Next steps' to reflect cross-platform parity.
  • Explicitly mention that all REST API examples can be executed from Linux, macOS, or Windows using tools like curl, wget, or Postman.
  • Provide a brief example of using curl or similar cross-platform command-line tools to make the REST API calls.
  • Ensure links to prerequisites and related articles include both CLI and PowerShell options where relevant.
GitHub Create Pull Request
Backup Monitor Azure Backup protected workloads ...les/backup/backup-azure-monitoring-built-in-monitor.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-centric backup tools (DPM, MABS, MARS) and linking to a 'manage-windows-server' page for Recovery Services vault management. There are no explicit Linux or macOS examples, nor are Linux backup tools or patterns mentioned, but the page is mostly conceptual and portal-focused, so the impact is limited.
Recommendations
  • Add references to Linux-supported backup agents and workloads (e.g., Azure Backup for Linux VMs, Azure Backup agent for Linux).
  • Include links to documentation for managing Linux backup items in Recovery Services vault and Backup vault.
  • Clarify whether the described monitoring features and portal views apply equally to Linux and macOS workloads.
  • Provide examples or notes for Linux-specific backup scenarios where applicable.
GitHub Create Pull Request
Backup Supported VM SKUs for Azure Policy .../articles/backup/backup-azure-policy-supported-skus.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation lists supported VM SKUs for Azure Backup Policy, presenting Windows-based SKUs first and in much greater detail than Linux equivalents. The Windows section is extensive, with many variants and configurations, while Linux distributions are listed in a much shorter, less granular manner. There are no examples, tools, or instructions specific to either platform, but the ordering and level of detail favor Windows.
Recommendations
  • Reorder the table or split it into separate sections for Windows and Linux to provide equal visibility.
  • Provide more granular details for Linux SKUs, including variants, supported configurations, and any platform-specific notes.
  • Add explicit guidance or examples for Linux users, such as how to verify SKU compatibility or troubleshoot unsupported images.
  • Include parity notes on feature differences between Windows and Linux VM backup policies.
GitHub Create Pull Request
Backup Back Up an Azure Virtual Machine with Azure Extended Zones Portal ...ain/articles/backup/backup-azure-vms-extended-zones.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Minor Windows Tools
Summary
The documentation is primarily Azure Portal-based and is mostly OS-neutral, but in the 'Install the VM agent' section, Windows instructions are given first and in more detail (including download links, file paths, and verification steps), while Linux instructions are more generic and refer to distribution repositories. No CLI or script examples are provided for either OS, and the rest of the guide is portal-centric, avoiding OS-specific tooling.
Recommendations
  • Present Linux and Windows agent installation instructions in parallel, with equal detail and verification steps.
  • Include explicit Linux verification commands (e.g., checking agent version via CLI).
  • Provide direct links to official Linux agent packages for major distributions.
  • If possible, offer CLI/PowerShell examples for backup operations, and ensure both Windows and Linux variants are shown.
  • Avoid listing Windows instructions before Linux unless there is a technical reason.
GitHub Create Pull Request
Backup Azure Backup release notes - Archive .../main/articles/backup/backup-release-notes-archived.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page for Azure Backup release notes shows a mild Windows bias. Several features and updates reference Windows-specific tools and agents, such as the MARS agent and Microsoft Azure Backup Server (MABS), which are Windows-only solutions. These Windows tools are mentioned prominently and repeatedly, while Linux/macOS equivalents are not discussed or are less visible. However, the page also covers cross-platform workloads (AKS, PostgreSQL, SAP HANA on RHEL, etc.), and some features explicitly mention CLI support, which is cross-platform. There are no explicit PowerShell-only instructions or examples, but Windows-centric solutions are often described first or in more detail.
Recommendations
  • For Windows-only tools like MARS and MABS, clearly state their platform limitations and suggest Linux/macOS alternatives or clarify if none exist.
  • Where backup features are available via CLI, REST API, or portal, highlight cross-platform usage and provide links to Linux/macOS-specific instructions if available.
  • Ensure parity in example coverage: if a feature is described for Windows (e.g., MARS agent), mention whether similar functionality exists for Linux/macOS and how to achieve it.
  • Consider adding a summary table indicating platform support for each major backup feature/tool.
  • Avoid listing Windows tools/features before cross-platform or Linux features unless there is a technical reason.
GitHub Create Pull Request
Backup Encrypt backup data in a Backup vault by using customer-managed keys ...backup/encryption-at-rest-with-cmk-for-backup-vault.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation consistently presents Windows-centric tools (PowerShell) before cross-platform alternatives (Azure CLI) in all code example sections. PowerShell examples are detailed and shown first, which may create friction for Linux/macOS users who are more likely to use Bash and Azure CLI. There are no Linux/macOS-specific instructions or screenshots, but the CLI examples do provide parity in functionality.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to better support Linux/macOS users.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide any OS-specific notes if needed.
  • Include screenshots or terminal snippets from Linux/macOS environments where applicable.
  • Add a short section clarifying platform support and recommending Azure CLI for non-Windows users.
GitHub Create Pull Request
Backup Configure Multi-user authorization using Resource Guard .../blob/main/articles/backup/multi-user-authorization.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides command-line examples for both PowerShell and Azure CLI, but consistently lists PowerShell (a Windows-centric tool) before CLI in all code tabs and sections. There are no Linux-specific instructions, nor are Linux/macOS tools or shell patterns mentioned. The CLI examples are present and functional, but PowerShell is given visual and instructional priority throughout, which may subtly reinforce a Windows-first workflow for users.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or list CLI first in some sections to avoid implicit prioritization.
  • Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for non-Windows users.
  • Add a short note or section for Linux/macOS users, confirming parity and pointing to CLI usage.
  • Where screenshots or UI instructions are given, clarify any differences for Linux/macOS users (e.g., browser, authentication flows, etc.), if applicable.
  • Consider including bash scripting examples or references for automation on Linux/macOS.
GitHub Create Pull Request
Backup Query your backups using Azure Resource Graph (ARG) ...les/backup/query-backups-using-azure-resource-graph.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions PowerShell as the first automation client for Azure Resource Graph, with CLI and SDK listed afterwards. The linked 'first query' guides for PowerShell and Azure CLI are referenced, but PowerShell is mentioned before CLI, which may subtly prioritize Windows tooling. No Linux-specific tools or shell examples (e.g., Bash) are given, and no explicit Linux/macOS instructions or screenshots are present. However, the core instructions are platform-neutral and do not prevent Linux/macOS users from completing the tasks.
Recommendations
  • List Azure CLI before PowerShell when mentioning automation clients, as CLI is cross-platform and more common for Linux/macOS users.
  • Explicitly mention that Azure CLI and SDKs are fully supported on Linux and macOS.
  • Provide sample Bash or shell scripts for running Kusto queries via Azure CLI.
  • Include screenshots or notes demonstrating usage on Linux/macOS terminals.
  • Add a short section clarifying platform parity and pointing to Linux/macOS setup guides for Azure CLI.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure Terraform ...ackup/quick-backup-azure-files-vault-tier-terraform.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references Azure PowerShell and Azure CLI as authentication options, but clarifies that only Azure CLI is supported for Terraform. However, Azure PowerShell is mentioned first in several places, and restoration/management steps list PowerShell before CLI. No Linux-specific tools or shell examples are provided, and the troubleshooting section does not mention OS-specific guidance. The overall flow is platform-neutral due to Terraform and Azure CLI, but there is a subtle preference for Windows/PowerShell in ordering and tool mentions.
Recommendations
  • List Azure CLI before Azure PowerShell wherever both are mentioned, as CLI is cross-platform and the only supported option for Terraform authentication.
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS, and provide installation links for all platforms.
  • Include example commands for Linux/macOS shells (e.g., bash) where appropriate, especially for authentication and environment setup.
  • In 'Next steps', list Azure CLI before PowerShell, and clarify that both tools are available on all major platforms.
  • Add troubleshooting notes for common Linux/macOS issues if relevant.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure CLI ...cles/backup/quick-backup-azure-files-vault-tier-cli.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page primarily focuses on Azure CLI usage, which is cross-platform, but several subtle Windows biases are present. The example CLI output includes a Windows-style file path (C:\Users\testuser\Downloads\CLIForAFS\azure-cli>), suggesting a Windows environment. References to Azure PowerShell and the Azure portal are mentioned before REST API or CLI alternatives in some sections. There is no explicit Linux/macOS example or mention of their shell environments beyond a brief note about Bash in Cloud Shell.
Recommendations
  • Replace Windows-style CLI output paths with generic or platform-neutral examples.
  • Add explicit Linux/macOS shell examples (e.g., Bash, zsh) and outputs.
  • Ensure that references to PowerShell and Windows tools are balanced with Linux/macOS equivalents, or mention CLI as the primary cross-platform method.
  • Where possible, show example commands being run in both Windows and Linux/macOS environments.
  • Clarify that Azure CLI works equally well on Linux/macOS and provide troubleshooting tips for those platforms.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Blobs using Azure CLI .../main/articles/backup/quick-blob-vaulted-backup-cli.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page references Azure PowerShell and links to PowerShell-based instructions before or alongside CLI instructions, and includes custom metadata indicating PowerShell tracking. There is a link to creating a Backup vault using PowerShell, but no equivalent Linux/bash example is directly mentioned or linked. The page does focus on Azure CLI, which is cross-platform, but the presence and order of PowerShell references suggest a mild Windows bias.
Recommendations
  • Provide explicit bash/Linux/macOS examples or links for creating a Backup vault and other key steps.
  • Ensure that CLI instructions are presented before or alongside any PowerShell/Windows-specific instructions.
  • Add notes clarifying cross-platform compatibility for all CLI commands.
  • Review included files to ensure they do not contain Windows-specific instructions or terminology.
  • Where PowerShell is referenced, also provide bash equivalents or clarify that CLI commands work on all platforms.
GitHub Create Pull Request
Backup Tutorial - Restore a VM with Azure CLI ...ocs/blob/main/articles/backup/tutorial-restore-disk.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is focused on Azure CLI usage for VM restore, which is cross-platform. However, there is a notable Windows bias in the introductory section: PowerShell is mentioned as an alternative and linked before CLI instructions, and the cross-zonal restore section links to a Windows-specific VM creation article. There are no Linux/macOS-specific examples, nor is there explicit parity shown for those platforms. All CLI examples are generic and do not use platform-specific shell features, but the documentation does not highlight Linux or macOS usage or considerations.
Recommendations
  • Add explicit references to Linux/macOS usage, such as shell compatibility notes or links to Linux VM documentation where appropriate.
  • When mentioning PowerShell, also mention Bash or other Linux-native shells as alternatives for scripting.
  • Ensure that cross-links (e.g., for zone-pinned VMs) point to both Windows and Linux VM documentation, or clarify applicability.
  • Consider providing example commands in both Bash and PowerShell syntax, or clarify that Azure CLI commands are identical across platforms.
  • Add a brief section or note confirming that all steps are fully supported and tested on Linux/macOS environments.
GitHub Create Pull Request
Backup Restore Azure Managed Disks ...ocs/blob/main/articles/backup/restore-managed-disks.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides instructions for restoring Azure Managed Disks and covers both Windows and Linux virtual machines when describing how to attach/detach disks after restore. However, the instructions for Windows VMs are consistently presented before those for Linux VMs, indicating a 'windows_first' bias. There are no PowerShell-heavy examples, exclusive mention of Windows tools, or missing Linux examples in the main restore workflow.
Recommendations
  • Alternate the order of Windows and Linux instructions, or present them in parallel (e.g., in a table or side-by-side format) to avoid implicit prioritization.
  • Explicitly state that the process applies equally to both Windows and Linux VMs at the beginning of the relevant section.
  • Ensure that any screenshots or linked instructions for Linux are as detailed and accessible as those for Windows.
  • Review linked resources to confirm Linux parity in depth and clarity.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-database-postgresql-flex-use-rest-api-create-update-policy.md ...base-postgresql-flex-use-rest-api-create-update-policy.md
Low Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by referencing the 'default PowerShell object' for PostgreSQL Flexible servers when describing backup scheduling and retention. No Linux-specific tools, shell commands, or cross-platform CLI examples are provided. All examples are REST API and JSON-based, which are platform-neutral, but the only tooling reference is to PowerShell, which is primarily a Windows technology (even though PowerShell Core is cross-platform, it is still most commonly associated with Windows environments).
Recommendations
  • Replace or supplement the mention of 'default PowerShell object' with references to Azure CLI, Bash scripts, or other Linux-native tools for managing backup policies.
  • Provide example commands for creating backup policies using Azure CLI or curl, which are commonly used on Linux systems.
  • Clarify that the REST API and JSON examples are platform-agnostic and can be used from any operating system.
  • If mentioning PowerShell, also mention cross-platform alternatives and provide equivalent examples for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-policy-supported-skus.md .../articles/backup/backup-azure-policy-supported-skus.md
Low Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation lists supported VM SKUs for Azure Backup Policy, and presents all Windows-based SKUs first in a long, detailed section, followed by a much shorter section for Linux distributions. There are many more Windows SKUs listed, with detailed breakdowns, while Linux SKUs are grouped and less granular. No examples, tools, or patterns are mentioned, but the ordering and detail level show a clear Windows-first bias.
Recommendations
  • Reorder the table or provide separate tables for Windows and Linux SKUs to give equal prominence.
  • Expand the Linux section to include more details, such as specific image SKUs, variants, and supported features.
  • Add clarifying notes about Linux support parity, including any limitations or differences compared to Windows.
  • If possible, provide links or references to Linux-specific backup documentation or troubleshooting guides.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/disk-backup-troubleshoot.md .../blob/main/articles/backup/disk-backup-troubleshoot.md
Low Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples, commands, or troubleshooting steps. However, it also does not include any Windows- or PowerShell-specific instructions, nor does it reference Windows tools or patterns. The absence of both Windows and Linux examples means Linux users are not disadvantaged compared to Windows users, but there is a lack of parity in that neither is addressed. The documentation could be improved by including cross-platform command-line examples (e.g., Azure CLI, PowerShell) for common troubleshooting actions.
Recommendations
  • Add Azure CLI examples for common troubleshooting steps, as Azure CLI is cross-platform and widely used on Linux.
  • If relevant, include PowerShell examples, but ensure they are presented alongside Azure CLI or Bash equivalents.
  • Explicitly mention that the troubleshooting steps apply to all supported platforms (Windows, Linux, macOS) unless otherwise noted.
  • Where permissions or resource group creation is discussed, provide sample commands for both Azure CLI and PowerShell.
  • Link to platform-agnostic Azure documentation for resource management tasks.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-managed-disks.md ...ocs/blob/main/articles/backup/restore-managed-disks.md
Low Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides instructions for restoring disks to both Windows and Linux VMs, but lists Windows VM instructions before Linux VM instructions. There is no evidence of exclusive use of Windows tools, PowerShell-heavy examples, or missing Linux examples; both platforms are referenced with parity in attach/detach/swap disk instructions via portal links.
Recommendations
  • Present instructions for Windows and Linux VMs in parallel or alternate the order to avoid implicit prioritization.
  • Explicitly state that the steps apply equally to both Windows and Linux VMs where applicable.
  • Ensure that any CLI or script-based examples (referenced in other docs) include both Windows (PowerShell) and Linux (Bash) variants.
  • Review linked resources to confirm Linux parity in step-by-step instructions.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-cross-region-restore.md ...lob/main/articles/backup/quick-cross-region-restore.md
Low Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only Azure Portal (web UI) instructions and does not include any command-line examples. There is no mention of Windows-specific tools or PowerShell, but also no coverage of Linux CLI tools (such as Bash, Azure CLI, or PostgreSQL command-line utilities). This omission may disadvantage Linux users who prefer or require command-line workflows.
Recommendations
  • Add Azure CLI examples for enabling Cross Region Restore and restoring PostgreSQL databases, as the Azure CLI is cross-platform and widely used on Linux.
  • Include Bash or psql command-line snippets for restoring PostgreSQL databases, where appropriate.
  • Explicitly mention that the steps are platform-agnostic if only the portal is supported, or clarify any platform limitations.
  • Provide parity by ensuring that any PowerShell or Windows-specific instructions (if added in the future) are matched with equivalent Linux/Bash/CLI instructions.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/threat-detection-overview.md ...blob/main/articles/backup/threat-detection-overview.md
Low Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation describes threat detection for Azure VM backups with Microsoft Defender for Cloud but does not provide any OS-specific examples or instructions. However, it implicitly assumes a Windows-centric environment by omitting any mention of Linux-specific considerations, tools, or examples, despite Azure VMs commonly running both Windows and Linux. There are no PowerShell or Windows tool references, but the lack of Linux parity in examples or troubleshooting is a subtle form of bias.
Recommendations
  • Explicitly state that threat detection supports both Windows and Linux Azure VMs, if applicable.
  • Include examples or notes about how threat detection works for Linux VMs, such as any differences in malware detection, configuration, or reporting.
  • If there are Linux-specific limitations or requirements (e.g., supported distributions, agent installation), document them clearly.
  • Provide troubleshooting steps or status interpretation examples for both Windows and Linux VM scenarios.
  • Ensure that related content and tutorials include Linux VM walkthroughs where relevant.
GitHub Create Pull Request
← Previous Page 21 of 21 Next →