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 1501-1525 of 1604 flagged pages
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-ase-database-about.md
...cs/blob/main/articles/backup/sap-ase-database-about.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page refers to Azure VMs in a generic way but, in the section on restoring VMs, the example link for creating a new empty VM points specifically to the Windows VM creation documentation. There are no explicit Linux or cross-platform examples or references, and no mention of Linux-specific tools or procedures, despite SAP ASE being commonly run on Linux. This may lead Linux users to feel less supported or unsure if the instructions fully apply to their environments.
Recommendations
- Provide parallel links and examples for both Windows and Linux VM creation and management (e.g., link to both Windows and Linux quick-create guides).
- Explicitly mention that the backup and restore procedures apply to both Windows and Linux VMs, and highlight any OS-specific considerations.
- Include Linux-specific examples or notes where relevant, such as running the preregistration script on Linux, or restoring to a Linux VM.
- Ensure that terminology and linked resources do not default to Windows unless the feature is Windows-only.
Create Pull Request
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/blob-backup-configure-tutorial.md
...main/articles/backup/blob-backup-configure-tutorial.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. In the 'Related content' section, Azure PowerShell is listed before Azure CLI, which is more cross-platform and commonly used on Linux. There is also a relative emphasis on PowerShell-based workflows, with no explicit Linux-specific guidance or examples, and no mention of Bash or Linux shell environments.
Recommendations
- List Azure CLI examples before or alongside PowerShell examples to promote cross-platform parity.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows.
- Add Bash or Linux shell script examples where command-line usage is discussed.
- Ensure that any referenced guides or links include both PowerShell and CLI/Linux instructions.
- Consider a dedicated section or callout for Linux users, highlighting any differences or additional steps.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-ase-database-backup.md
...s/blob/main/articles/backup/sap-ase-database-backup.md
Medium Priority
View Details →
Detected Bias Types
Linux First
Missing Windows Example
Summary
The documentation is strongly Linux-focused, referencing only Linux VMs for SAP ASE backup configuration. All instructions, prerequisites, and discovery steps assume a Linux environment (e.g., 'unprotected Linux VMs', 'sudo python3'), with no mention of Windows VMs, Windows command-line tools, or PowerShell. There are no Windows-specific examples or guidance, and the documentation does not address how to perform these tasks on Windows-based SAP ASE deployments.
Recommendations
- Add explicit guidance for configuring SAP ASE backup on Windows VMs, if supported.
- Include Windows-specific prerequisites, such as verifying Python installation and running scripts with Windows command prompt or PowerShell.
- Provide parallel examples for both Linux and Windows environments, including screenshots and command-line instructions.
- Clarify in the introduction or prerequisites section whether Windows VMs are supported or not. If only Linux is supported, state this explicitly to avoid confusion.
- If Windows is not supported, consider adding a note explaining this limitation and, if possible, provide a roadmap or alternatives for Windows users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/modify-vm-policy-cli.md
...docs/blob/main/articles/backup/modify-vm-policy-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides only a Windows-style file path (C:\temp2\Policy.json) in the Azure CLI example and does not mention or show a Linux/macOS equivalent. There are no explicit Linux or cross-platform examples or notes, which may confuse or exclude users on non-Windows systems.
Recommendations
- Provide both Windows and Linux/macOS file path examples in CLI commands (e.g., C:\temp2\Policy.json and /tmp/Policy.json).
- Add a note clarifying that file paths should be adapted to the user's operating system.
- Where possible, use environment-agnostic examples or variables (e.g., <path-to-policy.json>) and explain with OS-specific examples below.
- Explicitly mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/view-reports.md
...s/azure-docs/blob/main/articles/backup/view-reports.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page for viewing Azure Backup reports demonstrates a mild Windows bias. It references Windows-centric backup solutions and tools (such as DPM, SQL in Azure VM, and SAP HANA in Azure VM) more prominently and in greater detail than Linux equivalents. There are no explicit Linux or cross-platform command-line examples, and the backup scenarios described (e.g., DPM server, SQL in Azure VM) are primarily Windows-focused. Linux workloads and tools are not mentioned, and Linux-specific backup scenarios are absent.
Recommendations
- Include examples and references for Linux-based backup workloads (e.g., Azure Backup for Linux VMs, Azure Database for PostgreSQL, MySQL, etc.) alongside Windows examples.
- Provide parity in documentation by describing how to view and interpret reports for Linux-based backup items, not just Windows-centric workloads.
- Explicitly mention and illustrate any differences or similarities in reporting for Linux and Windows workloads.
- Add screenshots or walkthroughs that feature Linux backup items or mixed-environment scenarios.
- Where tools or patterns are Windows-specific (e.g., DPM), offer Linux alternatives or clarify applicability.
Backup
Back Up Azure VMs in a Recovery Services Vault
...b/main/articles/backup/backup-azure-arm-vms-prepare.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally presents information in a cross-platform manner, with both Windows and Linux VM scenarios addressed. However, in the 'Install the VM agent' section, instructions for Windows appear before those for Linux, which is a minor instance of 'windows_first' bias. Both platforms are otherwise covered with appropriate guidance.
Recommendations
- Alternate the order of Windows and Linux instructions in sections where both are equally relevant, or present them in parallel (side-by-side or tabbed) to avoid the perception of prioritizing one OS.
- Continue to ensure that all examples, screenshots, and instructions are provided for both Windows and Linux where applicable.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The glossary is generally cross-platform and workload-neutral, but there are some instances of Windows bias. Windows-specific technologies (e.g., VSS, DPM, MABS, MARS agent) are referenced without equal mention of Linux alternatives or parity, and Windows terminology (VSS) is explained before mentioning Linux equivalents. The 'Application consistent backup' entry references VSS first, then Linux scripts, and the VSS entry links only to Windows documentation. Some backup features and agents are described in a Windows-centric way, though this may reflect Azure Backup's current support matrix.
Recommendations
- Where Windows-specific technologies (e.g., VSS) are mentioned, clarify Linux equivalents or workflows (e.g., pre/post scripts, fsfreeze, etc.) and link to relevant Linux documentation.
- For entries like 'Application consistent backup', present Linux and Windows approaches with equal prominence.
- If backup agents or extensions are Windows-only, explicitly state this and, where possible, mention Linux support status or alternatives.
- Add references or links to Linux backup documentation or Azure Backup support for Linux workloads where applicable.
- Review glossary entries for implicit Windows-first ordering and rephrase to be platform-neutral where possible.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The glossary is generally cross-platform and workload-neutral, but there are minor signs of Windows bias. Windows tools (VSS, DPM, MABS, MARS agent) are referenced, and the VSS (Windows Volume Shadow Copy Service) entry links only to Windows documentation. In the 'Application consistent backup' entry, VSS is mentioned before Linux scripts. The 'Snapshot' entry links to a Windows-specific disk snapshot page first. However, most terms are generic or Azure-specific, and Linux workloads (such as Azure File shares, PostgreSQL) are included. No critical Linux/macOS functionality is omitted.
Recommendations
- For terms like VSS, clarify that Linux uses pre/post scripts and link to relevant Linux backup documentation.
- In entries where both Windows and Linux approaches exist (e.g., application consistent backup), present them with equal prominence.
- Where possible, provide links to Linux/macOS backup documentation or mention Linux equivalents alongside Windows tools.
- For 'Snapshot', include links to both Windows and Linux disk snapshot documentation if available.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The glossary is generally cross-platform and workload-neutral, but there are some minor signs of Windows bias: Windows-specific tools (VSS, DPM, MABS, MARS Agent) are referenced without Linux equivalents, and the VSS (Windows Volume Shadow Copy Service) is mentioned before Linux alternatives in the 'Application consistent backup' entry. However, Linux is acknowledged in some places (e.g., mentioning pre/post scripts for Linux in backups), and most definitions are platform-agnostic.
Recommendations
- Where Windows-specific backup technologies (e.g., VSS) are mentioned, explicitly note Linux alternatives or clarify when Linux uses different mechanisms.
- For entries like 'Application consistent backup', provide a brief example or link for Linux backup consistency methods (e.g., fsfreeze, custom scripts).
- Add references to Linux backup tools or patterns where relevant (e.g., mention Azure Backup support for Linux VMs and how consistency is achieved).
- Ensure glossary entries for backup agents/tools (MARS, DPM, MABS) clarify their platform support and mention Linux equivalents or alternatives if available.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The glossary is generally cross-platform and workload-neutral, but there are some mild signs of Windows bias. Windows-specific tools and technologies (e.g., VSS, DPM, MABS, MARS Agent) are referenced without always providing Linux/macOS equivalents or context. In the 'Application consistent backup' entry, VSS is mentioned first, with Linux alternatives only briefly referenced as 'pre or post scripts.' The 'Snapshot' entry links only to Windows disk snapshot documentation. Windows backup concepts (bare metal, system state) are described, but Linux equivalents are not discussed. However, most of these terms are workload-specific and reflect Azure Backup's actual supported workloads, which are often Windows-centric.
Recommendations
- Where Windows tools (e.g., VSS) are mentioned, provide equal detail or links for Linux/macOS alternatives (e.g., fsfreeze, custom scripts, etc.).
- In entries like 'Application consistent backup,' clarify how Linux workloads achieve consistency and link to relevant documentation.
- For concepts like 'bare metal backup' and 'system state backup,' note whether these are Windows-only and, if so, clarify Linux/macOS limitations or alternatives.
- In 'Snapshot,' add links to Linux disk snapshot documentation or clarify that the link is Windows-specific.
- Where workload-specific Windows tools are referenced (DPM, MABS, MARS Agent), clarify their platform scope and mention Linux backup options if available.
Backup
Create backup policies via REST API in Azure Backup
...up/backup-azure-arm-userestapi-createorupdatepolicy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Timezones
Summary
The documentation does not provide OS-specific command-line examples (such as PowerShell, Bash, or CLI) and is focused on REST API request bodies, which are platform-neutral. However, there is a subtle Windows bias in the use of 'Pacific Standard Time' as a timeZone value in several examples, which is a Windows time zone identifier. Linux/macOS systems typically use IANA time zone names (e.g., 'America/Los_Angeles'). Additionally, 'Pacific Standard Time' appears before 'UTC' in some examples, which may cause confusion for Linux/macOS users.
Recommendations
- Clarify that timeZone values must use Windows time zone identifiers, and provide a mapping or link to documentation for Linux/macOS users.
- Add a note or table listing common time zone identifiers and their equivalents in Windows and IANA formats.
- Explicitly state that the REST API is platform-neutral and can be used from any OS with standard HTTP tools (curl, wget, etc.), and provide example commands for Linux/macOS (e.g., curl).
- Ensure that examples alternate or balance between UTC and Windows time zones, or default to UTC for maximum cross-platform clarity.
Backup
Create Backup Policies for PostgreSQL Databases by Using the Data Protection REST API
...rotection-use-rest-api-create-update-postgresql-policy.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing PowerShell objects as the default way to conceptualize backup policies for PostgreSQL, without mentioning Linux/macOS equivalents (such as Azure CLI or Bash scripting). The only tooling or pattern explicitly referenced is PowerShell, and it is described as the default, which may create friction for Linux/macOS users. However, all actual API usage and examples are platform-neutral (HTTP requests and JSON bodies), so Linux users can still complete the task without significant barriers.
Recommendations
- Replace or supplement references to 'PowerShell object' with platform-neutral terminology such as 'policy object', or explicitly mention that the concepts apply regardless of OS.
- Add a note or section highlighting how Linux/macOS users can use Azure CLI, curl, or other REST tools to interact with the API, with example commands.
- Avoid describing PowerShell as the default; instead, present it as one of several options.
- Provide links to cross-platform tooling (Azure CLI, REST API docs) alongside PowerShell references.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation mentions BitLocker for Windows VMs before DM-Crypt for Linux VMs when describing in-guest encryption, and references SQL Server and TDE (a Microsoft/Windows-centric technology) without mentioning Linux database equivalents. Windows tools and patterns are presented first, indicating a subtle Windows bias.
Recommendations
- Present DM-Crypt (Linux) and BitLocker (Windows) together or alternate their order to avoid Windows-first bias.
- Include examples or references for backing up Linux workloads and databases, such as MySQL or PostgreSQL, and their encryption options.
- Clarify that Azure Backup supports both Windows and Linux VMs equally, and provide links to Linux-specific documentation where appropriate.
- If mentioning TDE for SQL Server, consider also mentioning encryption options for popular Linux database platforms.
Backup
Quickstart - Configure vaulted backup for Azure Blobs using Azure Backup
...ob/main/articles/backup/blob-backup-configure-quick.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page references Azure PowerShell before Azure CLI in the 'Next step' section, which may indicate a Windows-first bias. While both PowerShell and CLI options are provided, PowerShell is listed before CLI, and there are no explicit Linux/macOS-specific instructions or examples. The page does not mention Windows-only tools, but the ordering and emphasis may create friction for Linux/macOS users.
Recommendations
- List Azure CLI before Azure PowerShell in sections where both are referenced, as CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly state that both CLI and PowerShell are supported on all platforms, and provide links to installation guides for Linux/macOS users.
- Add examples or notes highlighting usage on Linux/macOS, especially for command-line tasks.
- Ensure that any referenced scripts or commands are tested and documented for bash/zsh environments.
Backup
Quickstart - Configure vaulted backup for Azure Files using Azure Terraform
...ackup/quick-backup-azure-files-vault-tier-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by mentioning Azure PowerShell alongside Azure CLI for authentication and management tasks, even though Terraform only supports Azure CLI for authentication. Azure PowerShell is referenced multiple times and often listed before Azure CLI in 'Next steps', but no Linux/macOS-specific shell examples or guidance are provided. There are no explicit Windows-only tools or commands, but the prominence of PowerShell and lack of Linux/macOS parity in examples may create minor friction for non-Windows users.
Recommendations
- Clarify that Terraform authentication is only supported via Azure CLI, and remove or de-emphasize Azure PowerShell references in the authentication section.
- Provide Linux/macOS-specific shell examples (e.g., bash) for Azure CLI usage, especially for authentication and file operations.
- Ensure that all management and restore steps list Azure CLI before Azure PowerShell, or present both equally.
- Add notes or links for installing Azure CLI on Linux/macOS.
- Review 'Next steps' to ensure parity between PowerShell and CLI instructions, and avoid implying PowerShell is preferred.
Backup
What is Azure Kubernetes Service (AKS) Backup?
...les/backup/azure-kubernetes-service-backup-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page does not provide explicit command-line examples for either Windows or Linux, but in the 'Related content' section, the PowerShell (Windows-centric) backup guide is listed before the Azure CLI (cross-platform) restore guide. This ordering subtly prioritizes Windows tooling. No direct Linux/macOS examples or tools are referenced, and there is no mention of Linux-specific patterns or parity.
Recommendations
- List Azure CLI (cross-platform) guides before PowerShell guides in 'Related content' to avoid implicit Windows prioritization.
- Add explicit examples or references for Linux/macOS users where relevant, such as using Azure CLI for both backup and restore operations.
- Include a statement clarifying that all operations can be performed from Linux/macOS environments using Azure CLI.
- Ensure parity in walkthroughs and examples for both Windows (PowerShell) and Linux/macOS (CLI, Bash).
Backup
Azure Kubernetes Service (AKS) backup using Azure Backup prerequisites
...kup/azure-kubernetes-service-cluster-backup-concept.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by listing Azure PowerShell as a primary method for backup and restore operations, and referencing Azure portal (which is most commonly used on Windows) before CLI options. There is a lack of explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is mentioned as a distinct method for backup/restore, while Linux-native tools or workflows are not highlighted. Azure CLI is referenced, but not as prominently or as early as PowerShell/portal. No explicit Linux/macOS instructions or screenshots are provided.
Recommendations
- Provide explicit Bash/Azure CLI examples for all backup and restore operations, including installation and role assignments.
- List Azure CLI and Bash examples before PowerShell in 'Next steps' and throughout the documentation.
- Clarify that all operations can be performed from Linux/macOS using Azure CLI, and provide parity in instructions.
- Include screenshots or terminal snippets from Linux/macOS environments where relevant.
- Add a section or note on cross-platform compatibility, explicitly stating that all steps are supported on Linux/macOS.
Backup
Back up Azure Database for PostgreSQL - Flexible Server using Azure CLI
...p/back-up-azure-database-postgresql-flex-backup-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is largely cross-platform, focusing on Azure CLI commands that work on Windows, Linux, and macOS. However, there is a minor Windows-first bias in the backup-instance create command example, which uses a Windows-style path ('.\OSSBkpInstance.JSON') instead of a Linux/macOS-style ('./OSSBkpInstance.JSON'). No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present.
Recommendations
- Use cross-platform file path notation in examples, such as './OSSBkpInstance.JSON', or provide both Windows and Linux/macOS variants.
- Add a note clarifying that Azure CLI commands work on all major platforms and that file paths should be adapted to the user's OS.
- Explicitly mention that examples are OS-agnostic unless otherwise stated.
Backup
Tutorial - Back up Azure Managed Disks using Azure Backup
...main/articles/backup/back-up-managed-disks-tutorial.md
Low Priority
View Details →
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 cross-platform. However, when scripting or automation is mentioned, PowerShell is referenced before Azure CLI, and there are no explicit Linux/macOS-specific examples or guidance. The only script references are to PowerShell and CLI, with PowerShell listed first, and there is no mention of Bash, shell scripting, or Linux-specific considerations. This ordering and lack of Linux/macOS context may create friction for non-Windows users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that all portal steps are OS-agnostic and can be performed from any supported browser on any OS.
- Add Bash/shell script examples for common tasks where automation is discussed.
- Include notes or links to Linux/macOS prerequisites or troubleshooting, if any exist.
- Ensure parity in script documentation by providing equal detail for CLI and PowerShell.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is largely platform-neutral, focusing on REST API usage and providing HTTP and JSON examples. However, there is a subtle Windows bias in the sample data for recovery points, where the 'osType' field is set to 'Windows' in all examples. No Linux or macOS-specific examples, references, or considerations are provided, and there is no mention of restoring Linux VMs or handling Linux-specific scenarios.
Recommendations
- Include example recovery points and restore operations for Linux VMs (e.g., with 'osType': 'Linux').
- Add a note clarifying that the REST API is platform-agnostic and works equally for Windows and Linux VMs.
- Provide guidance or links for Linux-specific restore scenarios, such as handling SSH keys, file system differences, or post-restore steps for Linux VMs.
- Ensure that sample data and walkthroughs alternate or include both Windows and Linux VM cases.
Backup
Back Up Azure VMs in a Recovery Services Vault
...b/main/articles/backup/backup-azure-arm-vms-prepare.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains parity between Windows and Linux, especially in the 'Install the VM agent' section, where both platforms are covered. However, the Windows instructions are presented first in the table, which is a minor example of 'windows_first' bias. No PowerShell-heavy examples, Windows-only tools, or missing Linux examples are present. The overall guidance is platform-neutral, focusing on Azure portal workflows applicable to both OS types.
Recommendations
- Alternate the order of Windows and Linux instructions in tables or sections to avoid implicit prioritization.
- Explicitly state that all portal-based steps apply equally to Windows and Linux VMs.
- Where possible, provide command-line examples for both Windows (PowerShell/CLI) and Linux (Bash/CLI) for advanced users.
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by referencing the 'default PowerShell object' for PostgreSQL - Flexible servers as the baseline for backup scheduling and retention. No Linux/macOS-specific tools, CLI, or shell examples are provided, and PowerShell is mentioned as the default configuration context. However, the main workflow is based on REST API calls and JSON payloads, which are cross-platform and can be used from any OS. There are no explicit Windows-only instructions or examples, but the PowerShell reference may cause confusion or friction for Linux/macOS users.
Recommendations
- Remove or clarify the reference to 'default PowerShell object' and explain how the default policy is defined in REST API or Azure Portal, not PowerShell.
- Add examples or notes for using the REST API from Linux/macOS environments, such as with curl, wget, or Azure CLI.
- Explicitly state that the REST API workflow is OS-agnostic and can be performed from any platform.
- If PowerShell is mentioned, provide equivalent instructions for Bash or other common Linux/macOS shells.
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 →
Detected Bias Types
Windows First
Summary
The documentation page is largely platform-neutral, focusing on REST API usage with HTTP requests and JSON payloads, which are cross-platform. However, there is a subtle Windows bias in the 'Assign permissions' section, where the link for assigning permissions points to a PowerShell-based guide ('backup-managed-disks-ps.md'), and PowerShell is mentioned before Azure CLI. In the 'Next steps' section, the restore options are listed in the order: Azure portal, Azure PowerShell, Azure CLI, REST API, again putting Windows/PowerShell before Linux-friendly CLI. No explicit PowerShell-only examples or Windows-only tools are present, and all API usage is platform-agnostic.
Recommendations
- Ensure that links and references to permission assignment include both Azure CLI and PowerShell options, or link to a page that covers both.
- When listing tools or guides (e.g., in 'Next steps'), alternate the order or list Azure CLI before PowerShell to avoid implicit prioritization.
- Explicitly mention that all REST API operations can be performed from any OS using standard tools (curl, Postman, etc.), and provide example commands for both Windows and Linux/macOS environments where relevant.
- Add a brief section or note on how to use curl or similar cross-platform tools for making the API calls, to reinforce platform neutrality.
Low Priority
View Details →
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, while Linux distributions are listed later and with less granularity. There are no usage examples or tooling references, so bias is limited to ordering and detail.
Recommendations
- Present Linux and Windows SKUs in separate, equally prominent tables or sections.
- Provide more detailed breakdowns for Linux SKUs, including specific image variants and notes on support nuances.
- Add introductory context clarifying parity and any platform-specific limitations.
- If possible, include examples or guidance for both Windows and Linux VM backup configuration.
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 →
Detected Bias Types
Windows First
Minor Windows Tools
Summary
The documentation is largely platform-neutral, focusing on Azure portal-based workflows accessible from any OS. However, in the 'Install the VM agent' section, Windows instructions are presented first and in more detail (including download links, file paths, and version checks), while Linux instructions are shorter and less explicit. The rest of the page avoids CLI or OS-specific tooling, and does not use PowerShell or Windows-only patterns.
Recommendations
- Present Linux and Windows agent installation instructions with equal detail and prominence, possibly in side-by-side tabs.
- Include explicit Linux commands for installing/updating the agent (e.g., sample apt/yum commands).
- Add verification steps for Linux agent installation, similar to the Windows version check.
- Consider listing Linux instructions first or in parallel to avoid implicit prioritization.