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 1476-1500 of 1604 flagged pages
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vm-migrate-enhanced-policy.md
...cles/backup/backup-azure-vm-migrate-enhanced-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation primarily describes migration of Azure VM backups using the Azure Portal and briefly mentions CLI and PowerShell, but does not provide explicit Linux-specific examples or parity for Linux administrators. The only command-line reference is a link to the Azure CLI command, but no PowerShell or Bash/Linux shell examples are shown inline, nor is there any mention of Linux-specific considerations or tools. The structure and language implicitly assume a Windows-centric audience by referencing PowerShell and the Azure Portal UI, with no explicit Linux parity.
Recommendations
- Include explicit Linux/Bash shell examples for CLI operations, such as showing the az backup item set-policy command with sample parameters.
- Provide parity between PowerShell and Bash/CLI examples, ideally in tabbed format, so both Windows and Linux administrators can follow along.
- Mention any Linux-specific considerations or prerequisites for VM backup migration, if applicable.
- Clarify that the Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, and provide installation links for non-Windows platforms.
- If PowerShell examples are included elsewhere, ensure Bash/Linux equivalents are also present.
Create Pull Request
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-overview.md
...s/blob/main/articles/backup/offline-backup-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references Microsoft Azure Backup Server (MABS), System Center Data Protection Manager (DPM), and the MARS Agentβall Windows-based backup solutions. There are no mentions of Linux-based backup agents, tools, or workflows, nor are there any examples or considerations for Linux environments. This creates a bias toward Windows and omits guidance for Linux users.
Recommendations
- Explicitly state whether Linux-based backup agents or tools are supported or not for offline backup workflows.
- If Linux support exists, provide equivalent instructions, examples, and workflows for Linux environments (e.g., using Azure CLI, azcopy, or other cross-platform tools).
- Include a comparison table row for OS/platform support, clarifying which options are available for Windows and Linux.
- If only Windows tools are supported, note this limitation clearly and provide guidance or alternatives for Linux users.
- Reference cross-platform utilities (such as AzCopy or Azure CLI) where possible, and provide sample commands for both Windows and Linux.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-blob-vaulted-backup-cli.md
.../main/articles/backup/quick-blob-vaulted-backup-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows subtle Windows bias by linking to PowerShell-based instructions before or alongside CLI and REST API options, and by referencing a PowerShell-specific guide for creating a Backup vault. There is no explicit Linux exclusion, but the presence and order of PowerShell links suggest a Windows-first approach.
Recommendations
- Provide direct links to both PowerShell and Azure CLI/Linux shell instructions for creating a Backup vault, ensuring CLI examples are not secondary.
- When listing restore options, avoid listing PowerShell before CLI or alternate between them to avoid perceived priority.
- Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) to reinforce parity.
- If possible, include bash or shell script examples alongside CLI commands to demonstrate Linux compatibility.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-portal.md
...cs/blob/main/articles/backup/quick-backup-vm-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by referencing Windows VM creation in the introductory section and providing a detailed, step-by-step Windows agent installation process before mentioning Linux. Linux instructions are less detailed and lack direct package commands or examples. Throughout the guide, there is a lack of parity in practical Linux examples, and the initial VM creation link points only to Windows VMs.
Recommendations
- Provide parallel links and references for both Windows and Linux VM creation in the introduction (e.g., link to both /azure/virtual-machines/windows/quick-create-portal and /azure/virtual-machines/linux/quick-create-portal).
- Ensure that all instructions and examples (such as agent installation) are equally detailed for Linux, including explicit package manager commands (e.g., 'sudo apt install walinuxagent' or 'sudo yum install WALinuxAgent').
- Where screenshots or UI steps are shown, clarify that the process is identical for both Windows and Linux VMs, or note any differences.
- Include troubleshooting or verification steps for Linux agent installation, similar to the Windows example (e.g., checking the agent version with 'waagent --version').
- Review the documentation for any other implicit prioritization of Windows and ensure Linux users are equally supported throughout.
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
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Summary
The documentation contains a subtle Windows bias, notably by referencing the 'default PowerShell object' for PostgreSQL - Flexible servers as the baseline for backup scheduling and retention. There are no explicit Linux or cross-platform CLI examples, and PowerShell is mentioned as the default tool, which may not be familiar or available to Linux users. However, the main focus of the documentation is on REST API usage, which is platform-agnostic. No shell-specific (cmd, PowerShell, bash) command-line examples are provided, but the only tool mentioned by name is PowerShell.
Recommendations
- Remove or rephrase references to 'default PowerShell object' to avoid implying PowerShell is the primary or only supported tool.
- If referencing default objects or tools, clarify their cross-platform availability or provide equivalent examples for Linux (e.g., Azure CLI, Bash, or SDK usage).
- Add a section or note highlighting that the REST API can be used from any platform, and provide example invocations using curl (Linux/macOS) and PowerShell (Windows), ensuring parity.
- Where possible, provide sample scripts or commands for both Windows (PowerShell) and Linux (bash/curl) to demonstrate REST API usage in a cross-platform manner.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-aks.md
...ure-docs/blob/main/articles/backup/quick-backup-aks.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal (web UI) for configuration steps and does not provide any command-line examples. While the Azure CLI is mentioned as a next step for restore operations, there are no CLI, PowerShell, or shell-based instructions for the backup configuration process itself. This approach implicitly favors Windows users, as the Azure Portal is often the default for Windows-centric workflows, and omits parity for Linux users who may prefer or require CLI-based automation.
Recommendations
- Add step-by-step instructions for configuring AKS backup using the Azure CLI, including all relevant commands.
- If PowerShell examples are provided elsewhere, ensure equivalent Bash/shell examples are included.
- Explicitly mention that the Azure CLI is cross-platform and provide links or code blocks for both Windows and Linux environments.
- Include a table or section comparing portal, CLI, and (if applicable) PowerShell methods for configuring AKS backup.
- Ensure screenshots and examples are not exclusively from Windows environments; include CLI output from Linux terminals where appropriate.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-rm-template-samples.md
...lob/main/articles/backup/backup-rm-template-samples.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page lists several Azure Resource Manager and Bicep templates for backup scenarios, but it demonstrates a Windows bias by explicitly providing a template for deploying a Windows Server VM with backup enabled, while not offering an equivalent example for Linux VMs. There are no Linux-specific backup scenarios or templates mentioned, and the only OS-specific example is for Windows.
Recommendations
- Add examples and templates for deploying and backing up Linux VMs, ensuring parity with the Windows Server VM example.
- Explicitly mention support for both Windows and Linux VMs in relevant templates, or clarify any OS-specific limitations.
- Where OS-specific templates are provided (e.g., for Windows Server), provide a corresponding Linux example immediately after or alongside.
- Review descriptions to ensure they are OS-neutral unless a feature is genuinely Windows-only, and clearly state such limitations.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-restore-disk.md
...ocs/blob/main/articles/backup/tutorial-restore-disk.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Reference
Summary
The documentation is largely cross-platform and focused on Azure CLI, which is available on both Windows and Linux. However, there is a subtle Windows bias in the form of referencing PowerShell documentation before Linux alternatives, and linking to Windows-specific VM documentation in some places. No Linux-specific examples or tools are missing, but the only alternative to CLI mentioned is PowerShell, and the link to zone-pinned VMs references a Windows VM creation page.
Recommendations
- When referencing alternative automation tools, mention both PowerShell and Bash (or shell scripting) guides if available, or clarify that CLI commands are cross-platform.
- When linking to VM documentation (e.g., for zone-pinned VMs), provide links to both Windows and Linux VM creation guides.
- Explicitly state that all CLI examples work on both Windows and Linux, and consider including a note or section for Linux users if there are any OS-specific considerations.
- If referencing PowerShell for automation, also mention Bash scripting or provide a link to a Linux automation guide if available.
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 discusses backing up SAP ASE (Sybase) databases on Azure VMs but implicitly assumes a Windows-centric environment in several places. For example, when referencing VM creation, it links specifically to the Windows VM creation guide and does not mention or link to Linux VM equivalents. There are no explicit examples or instructions tailored for Linux-based ASE deployments, despite Linux being a common platform for SAP ASE. There is also no mention of Linux-specific tools, commands, or considerations, and no PowerShell or Windows-specific commands are shown, but the omission of Linux content is notable.
Recommendations
- Provide parallel instructions and links for both Windows and Linux VM creation and management, especially when referencing Azure VM documentation.
- Explicitly mention supported operating systems for SAP ASE on Azure VMs, and clarify any differences in backup procedures or prerequisites between Windows and Linux.
- Include Linux-specific examples, such as using Bash or Linux shell commands for running the preregistration script, and note any OS-specific requirements (e.g., permissions, package dependencies).
- When referencing Azure documentation, provide both Windows and Linux links where relevant (e.g., quick-create guides for VMs).
- If the solution is OS-agnostic, state this clearly to reassure Linux users that the instructions apply equally to their environment.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/whats-new.md
...Docs/azure-docs/blob/main/articles/backup/whats-new.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page for Azure Backup service release notes exhibits a mild Windows bias. Several features and updates reference or focus on Windows-centric tools (such as MARS agent and Microsoft Azure Backup Server), and Windows Server support is highlighted in the context of on-premises backup. However, the majority of the content is platform-neutral or references cross-platform workloads (Linux, PostgreSQL, MySQL, SAP HANA, AKS, etc.), and there are no explicit PowerShell-heavy or Windows-only example sections. Linux-specific tools or parity are not missing, but Windows tools are mentioned more frequently and sometimes before their Linux or cross-platform equivalents.
Recommendations
- When referencing backup agents or servers (e.g., MARS, MABS), clarify their platform support and provide equivalent Linux options or links where available.
- Where Windows tools are mentioned (such as MARS or MABS), include a brief note or link about Linux backup approaches (e.g., Azure Backup for Linux VMs, native Linux backup tooling integration).
- Ensure that any feature or tool that is Windows-specific is clearly labeled as such, and that Linux or cross-platform alternatives are referenced in the same context.
- Add explicit examples or references for Linux workloads and management tools (e.g., Azure CLI, REST API) alongside any mention of PowerShell or Windows GUIs.
- Consider a summary table or section listing supported platforms for each backup feature/tool, making Linux parity and support more visible.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/move-to-azure-monitor-alerts.md
...b/main/articles/backup/move-to-azure-monitor-alerts.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page shows a subtle Windows bias by referencing the Azure portal, PowerShell, and CLI clients as ways users are immediately aware of backup job results, but does not mention Linux-specific tools or workflows. There are no explicit Linux or cross-platform command-line examples, and the only agent mentioned by name is the Microsoft Azure Recovery Services (MARS) agent, which is Windows-only. Notification configuration is stated as only available via the Azure portal, with no mention of Linux-friendly automation or CLI alternatives.
Recommendations
- Include explicit examples or references for Linux users, such as using Azure CLI or REST API (even if not currently supported, clarify roadmap or alternatives).
- Mention Linux-compatible backup agents or clarify if only Windows workloads are supported for classic alerts.
- Balance references to PowerShell with Azure CLI or Bash equivalents where possible.
- If certain features are Windows-only (e.g., MARS agent), clearly state this and provide Linux alternatives or workarounds.
- Add documentation or links for Linux administrators to monitor and manage alerts using tools available on Linux.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-overview.md
...s/blob/main/articles/backup/offline-backup-overview.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation exclusively references Microsoft-centric backup tools (MABS, DPM-A, MARS Agent), which are primarily Windows-based, and does not mention or provide examples for Linux environments or tools. There are no Linux-specific instructions, examples, or references to Linux-compatible backup agents or workflows, indicating a bias toward Windows platforms.
Recommendations
- Explicitly state whether Linux-based backup agents or workflows are supported or not for offline backup scenarios.
- If Linux is supported, provide examples and instructions for performing offline backups from Linux systems, including any required tools or agents.
- Mention any Linux-compatible utilities or command-line tools that can be used for preparing and transferring backup data.
- Include a comparison or support matrix indicating platform compatibility (Windows/Linux) for each offline backup method.
- If Linux is not supported, clearly document this limitation to set customer expectations.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-azure-files-vault-tier-cli.md
...cles/backup/quick-backup-azure-files-vault-tier-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is generally cross-platform and focused on Azure CLI, which is available on all major OSes. However, there are subtle Windows biases: (1) The example CLI output includes a Windows file path (C:\Users\testuser\Downloads\...), which may confuse Linux/macOS users; (2) The instructions for installing Azure CLI mention Windows and macOS specifically and suggest using Docker, but do not mention Linux package managers or provide Linux-specific install guidance; (3) The Next Steps section lists Azure portal and PowerShell before CLI and REST API, which may imply a Windows-first approach.
Recommendations
- Replace or supplement the CLI example output with a Linux/macOS terminal prompt (e.g., ~/Downloads/CLIForAFS/azure-cli$) or use a generic prompt (e.g., $) to avoid Windows path bias.
- In the prerequisites, explicitly mention Linux as a supported platform for Azure CLI and provide a link to Linux installation instructions or mention common package managers (apt, yum, etc.).
- When listing alternative tools (portal, PowerShell, CLI, REST API), rotate or randomize the order, or list CLI first to match the page's focus.
- Ensure that all example commands and outputs are OS-agnostic unless a platform-specific behavior is being demonstrated.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-cloud-as-tape.md
...n/articles/backup/backup-azure-backup-cloud-as-tape.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page implicitly prioritizes Windows environments by referencing System Center Data Protection Manager (DPM), which is a Windows-only tool, and by linking to a 'Try Azure Backup' guide that specifically mentions Windows with the MARS agent. There are no examples, screenshots, or instructions for Linux systems or cross-platform backup scenarios, and no mention of Linux-compatible tools or agents.
Recommendations
- Include explicit references to Linux backup scenarios, such as using Azure Backup with Linux VMs or workloads.
- Provide examples, screenshots, or step-by-step guides for configuring backup and retention policies on Linux systems.
- Mention Linux-compatible backup agents or integration options (e.g., Azure Backup for Linux VMs, Azure CLI usage).
- Balance references to Windows-specific tools (like DPM and MARS agent) with Linux equivalents or alternatives.
- Add links to Linux-focused documentation in the 'Next steps' section, such as 'Back up Linux VMs with Azure Backup'.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-database-postgresql-overview.md
...es/backup/backup-azure-database-postgresql-overview.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by exclusively recommending the use of pgAdmin (a GUI tool popular on Windows) for database management tasks, without mentioning or providing examples for Linux-native or CLI-based tools such as psql. There are no command-line examples or references to Linux workflows, and all screenshots and tool recommendations focus on GUI-based approaches, which are more common in Windows environments.
Recommendations
- Include examples using the psql command-line tool for granting privileges and connecting to the database, as this is the default and most common tool on Linux systems.
- Provide alternative instructions for Linux users, such as how to perform the same tasks using terminal commands.
- Mention other cross-platform or Linux-native tools (e.g., DBeaver, Azure CLI, or direct psql usage) alongside pgAdmin.
- Add screenshots or code snippets that demonstrate Linux terminal usage for key operations.
- Ensure that REST API and CLI instructions are as prominent as portal/GUI instructions, and consider including a 'Linux' or 'Command-line' tab in relevant sections.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-portal.md
...cs/blob/main/articles/backup/quick-backup-vm-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias, primarily by referencing Windows VM creation first and providing more detailed, step-by-step instructions for installing the VM agent on Windows (including download links, file paths, and UI actions), while the Linux instructions are more generic and less detailed. The initial link for VM creation points specifically to Windows VMs, and Windows-specific tools and file paths are mentioned explicitly.
Recommendations
- Provide parallel Linux examples and links wherever Windows examples or links are given (e.g., link to both Windows and Linux VM creation quickstarts).
- Ensure installation instructions for the VM agent on Linux are as detailed as those for Windows, including example commands for RPM/DEB installation and verification steps.
- Avoid mentioning Windows tools, file paths, or UI actions without providing Linux equivalents.
- When referencing VM creation or management, use neutral language or present Linux and Windows options together, rather than Windows-first.
- Include screenshots or command snippets for Linux where relevant, to match the level of detail given for Windows.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits a mild Windows bias by referencing PowerShell objects as the default or canonical representation of backup policy structure for PostgreSQL backups. There are no explicit Linux or cross-platform CLI examples, and the only tooling or scripting context mentioned is PowerShell. However, the primary focus of the page is on REST API usage and JSON payloads, which are inherently cross-platform. Still, the repeated mention of PowerShell as the default object model may alienate Linux users or those using other shells.
Recommendations
- Replace or supplement references to 'PowerShell object' with neutral terms such as 'policy object' or 'JSON policy object', since the REST API and JSON are cross-platform.
- If scripting examples are included, provide both PowerShell and Bash/cURL examples for invoking the REST API, so Linux users have parity.
- Clarify that the REST API and JSON payloads can be used from any platform or scripting environment, not just PowerShell.
- Avoid implying that PowerShell is the default or only way to interact with the API; instead, emphasize the cross-platform nature of REST and JSON.
- Consider adding a short section or note for Linux/macOS users, demonstrating how to use cURL or similar tools to perform the same operations.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-disks.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-disks.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page is largely neutral and platform-agnostic in its main REST API examples, but it demonstrates subtle Windows bias in two ways: (1) references to PowerShell are given before Azure CLI in the 'Next steps' section, and (2) the only explicit link for assigning permissions in prerequisites points to a PowerShell-based guide. There are no Linux-specific examples or explicit parity in tool references.
Recommendations
- When referencing command-line tools, always mention Azure CLI alongside PowerShell, and provide links to both PowerShell and CLI guides for tasks like assigning permissions.
- In the 'Next steps' section, list Azure CLI before or alongside PowerShell, or alternate their order across documentation pages.
- Explicitly state that all REST API operations can be performed from any OS, and provide example CLI commands (e.g., using curl or az CLI) for common operations.
- Add a section or note clarifying that the REST API can be used from Linux, macOS, and Windows equally, and provide sample shell (bash) commands where appropriate.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Summary
The documentation page lists supported VM SKUs for Azure Policy, presenting a long, detailed enumeration of Windows-based images and SKUs before Linux distributions. The Windows section is much more extensive and appears first, while Linux distributions are listed only after all Windows options, with less detail and fewer variants. There are no Linux-specific examples or parity in the level of detail provided.
Recommendations
- Reorder the table or split it into separate sections for Windows and Linux, or alternate between Windows and Linux entries to avoid the impression of prioritizing Windows.
- Provide equal detail for Linux distributions, including variants, special configurations, and notes where applicable.
- Add explicit mention of support for Linux in the introductory text, not just as a list at the end.
- If there are any limitations or special considerations for Linux (as there is for CentOS), provide similar notes for Windows where relevant.
- Consider including example policy assignments or usage scenarios for both Windows and Linux VMs to ensure parity.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-sql-manage-cli.md
...ob/main/articles/backup/backup-azure-sql-manage-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently assumes the SQL Server is running on a Windows VM and does not mention or provide guidance for Linux-based SQL Server VMs. All examples, resource names, and container naming conventions (such as 'mssqlserver', 'testSQLVM') implicitly reference Windows environments. There are no examples or notes for managing SQL Server on Linux VMs, nor any mention of Linux-specific considerations or differences.
Recommendations
- Explicitly state whether the instructions apply to both Windows and Linux SQL Server VMs, or clarify if only Windows is supported.
- If Linux SQL Server VMs are supported, provide parallel examples and notes for Linux environments (e.g., naming conventions, prerequisites, differences in agent installation or backup support).
- Add a section or note about any limitations or differences when using Azure Backup for SQL Server on Linux VMs.
- Use more neutral naming in examples (e.g., avoid 'mssqlserver' if not Windows-specific) or provide both Windows and Linux variants.
- Reference relevant documentation for SQL Server on Linux in Azure VMs if available.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/create-manage-backup-vault.md
...lob/main/articles/backup/create-manage-backup-vault.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation exclusively describes how to create and delete Backup vaults using the Azure Portal UI, which is platform-agnostic but typically more familiar to Windows users. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux-specific tools or workflows. Additionally, where command-line automation is referenced, only REST API documentation is linked, with no Azure CLI or Bash scripting guidance. This may unintentionally favor Windows users or those accustomed to GUI workflows, while omitting parity for Linux users who often prefer CLI-based management.
Recommendations
- Add step-by-step instructions for creating and deleting Backup vaults using the Azure CLI, with example commands.
- Include Bash script examples for Linux users to automate vault management.
- If PowerShell examples are provided elsewhere, ensure equivalent Azure CLI/Bash examples are present and not secondary.
- Reference both Windows and Linux environments explicitly when discussing automation or scripting options.
- Link to documentation for managing Backup vaults via Azure CLI and Bash in the 'Next steps' or relevant sections.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vm-migrate-enhanced-policy.md
...cles/backup/backup-azure-vm-migrate-enhanced-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation primarily describes migration using the Azure Portal UI and briefly references Azure CLI, but does not provide any explicit command-line examples for Linux users. While PowerShell is mentioned in a note about supported tools, there are no step-by-step CLI or PowerShell examples, and no Linux-specific guidance or screenshots. The only command-line reference is a link to the Azure CLI documentation, with no in-place example. This may disadvantage Linux users who prefer or require CLI-based workflows.
Recommendations
- Add explicit Azure CLI command examples for all migration operations, including sample commands and expected output.
- Ensure that CLI examples are platform-agnostic or, where differences exist, provide both Windows (PowerShell) and Linux (Bash) command examples.
- Include screenshots or terminal output for CLI-based workflows, not just portal UI.
- Clarify in each section that all operations can be performed via CLI on both Windows and Linux, and provide links to relevant documentation for both platforms.
- If PowerShell-specific features or commands are mentioned, provide equivalent Bash or shell commands for Linux users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-extended-zones.md
...ain/articles/backup/backup-azure-vms-extended-zones.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains platform neutrality by focusing on the Azure Portal UI, but in the 'Install the VM agent' section, Windows instructions are presented first and in more detail, including direct download links and file paths, while Linux instructions are less detailed and refer users to external package repositories. This ordering and detail level reflect a subtle Windows-first and Windows-tools bias.
Recommendations
- Present Linux and Windows agent installation instructions with equal detail and prominence, possibly in parallel columns or tabs.
- Provide direct Linux command examples for installing the Azure Linux agent (e.g., using apt, yum, or zypper), similar to the explicit Windows MSI instructions.
- Where possible, alternate the order of Windows and Linux instructions or use a neutral ordering (e.g., alphabetical) to avoid implicit prioritization.
- Include troubleshooting and verification steps for Linux agent installation, matching the level of detail provided for Windows.
- Ensure that any references to file paths, tools, or verification steps are provided for both platforms.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-encryption.md
...re-docs/blob/main/articles/backup/backup-encryption.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a subtle Windows bias by mentioning BitLocker (the Windows disk encryption tool) before DM-Crypt (the Linux equivalent) when describing Azure Disk Encryption for VMs. BitLocker is named explicitly and first, while DM-Crypt is mentioned second, which may suggest a prioritization of Windows technologies. No Linux-specific tools or command-line examples are provided, and the only detailed encryption workflow (ADE) references BitLocker first.
Recommendations
- Present Linux and Windows encryption tools in parallel or alternate the order (e.g., 'ADE uses BitLocker for Windows VMs and DM-Crypt for Linux VMs') to avoid implicit prioritization.
- Include explicit Linux examples or references where possible, such as links to documentation on using DM-Crypt with Azure VMs.
- Add a section or examples that address Linux-specific backup and encryption scenarios to ensure parity.
- Where possible, avoid listing Windows tools or patterns before Linux equivalents unless there is a technical reason.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-rm-template-samples.md
...lob/main/articles/backup/backup-rm-template-samples.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides a comprehensive list of Azure Resource Manager and Bicep templates for Azure Backup scenarios. However, it demonstrates a subtle Windows bias: the only specific OS example given is for deploying a Windows Server VM with backup enabled, and there are no equivalent examples or explicit mentions of Linux VMs or Linux-specific backup scenarios. This may give the impression that Windows is the primary or only supported platform for certain backup operations.
Recommendations
- Add examples and templates for deploying and backing up Linux VMs, similar to the 'Deploy Windows Server VM with backup enabled' entry.
- Explicitly mention Linux support where applicable, especially in sections that currently only reference Windows.
- Where possible, provide parity in sample templates and descriptions for both Windows and Linux environments.
- Review template descriptions to ensure they do not imply exclusivity to Windows unless that is a technical limitation.