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 1451-1475 of 1604 flagged pages
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 exhibits mild Windows bias by listing Azure PowerShell as the first option for restoring Azure Blobs, ahead of Azure CLI and REST API. This ordering may suggest a preference for Windows-centric tooling. There are no explicit Linux examples or mentions of Linux-specific tools, and the page does not provide parity guidance for Linux users.
Recommendations
- List Azure CLI examples before or alongside Azure PowerShell to avoid implicit prioritization of Windows tools.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux and macOS users.
- Provide example commands for both Azure PowerShell and Azure CLI in the main tutorial, not just in related content.
- Include a note or section on using these tools from Linux environments, highlighting any differences or considerations.
- Ensure that REST API examples are presented as platform-neutral and accessible from any OS.
Create Pull Request
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/query-backups-using-azure-resource-graph.md
...les/backup/query-backups-using-azure-resource-graph.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as the first automation client when discussing how to use Azure Resource Graph queries in automation. There is no explicit Linux CLI example, and PowerShell is mentioned before Azure CLI and SDK options. The documentation does not provide parity in examples or instructions for Linux users, nor does it mention Linux-specific tools or patterns.
Recommendations
- List Azure CLI before PowerShell when mentioning automation clients, or present both equally.
- Provide explicit examples or links for running ARG queries using Azure CLI on Linux systems.
- Include notes or sections that address Linux users, such as installation or usage tips for Azure CLI on Linux.
- Avoid implying PowerShell is the default or preferred method; clarify that both PowerShell and CLI are supported cross-platform.
- Add sample scripts or command lines for both PowerShell and Azure CLI to demonstrate parity.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/scripts/disable-soft-delete-for-file-shares.md
.../backup/scripts/disable-soft-delete-for-file-shares.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by using Windows-style file paths (e.g., .\rqbody-disableSoftDelete.json) in all command examples and does not provide equivalent Linux/macOS examples (e.g., ./rqbody-disableSoftDelete.json). There is no mention of Linux-specific usage or considerations for the ARM client, nor are there any bash or shell examples. This may make it less accessible for Linux users.
Recommendations
- Add Linux/macOS command examples using forward slashes (e.g., ./rqbody-disableSoftDelete.json) alongside Windows examples.
- Clarify whether the ARM client works cross-platform and provide installation instructions for Linux/macOS if supported.
- Explicitly mention any platform-specific requirements or differences in usage.
- Consider including bash or shell script samples for Linux users.
- Add a note on how to run the ARM client on Linux (e.g., via Mono, .NET Core, or alternatives) if applicable.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-userestapi-createorupdatepolicy.md
...up/backup-azure-arm-userestapi-createorupdatepolicy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page exhibits subtle Windows bias, primarily through the use of 'Pacific Standard Time' as the default time zone in several examples and the prioritization of Azure VM (which is typically Windows-based) in example sections and request bodies. The time zone examples use 'Pacific Standard Time', which is a Windows time zone identifier, rather than the IANA time zone format commonly used on Linux. There are no explicit Linux or cross-platform examples, nor is there mention of Linux-specific patterns or tools. The documentation does not reference PowerShell or Windows-only command-line tools, but the time zone handling and example ordering suggest a Windows-centric approach.
Recommendations
- Include examples using IANA time zone identifiers (e.g., 'America/Los_Angeles') alongside Windows time zones to support Linux users.
- Clarify time zone support in the API: specify whether only Windows time zones are accepted, or if IANA/Olson time zones are also supported.
- Add explicit notes or examples for Linux users, such as how to format requests or handle time zones from Linux environments.
- Ensure parity in example ordering: present Azure VM (Windows and Linux) examples together, or clarify that the API is agnostic to VM OS.
- If CLI examples are added in future, provide both Windows (PowerShell/CMD) and Linux (bash/curl) command samples.
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 focuses on Azure Backup as a replacement for tape infrastructure but implicitly prioritizes Windows environments. It references System Center Data Protection Manager (DPM), a Windows-only tool, and links to a 'backup-windows-with-mars-agent' page for next steps. No Linux-specific backup tools, examples, or guidance are provided, and there is no mention of Linux agents or cross-platform considerations.
Recommendations
- Include examples and guidance for Linux systems, such as using Azure Backup with Linux VMs or workloads.
- Reference Linux-compatible backup agents or scripts, and provide links to relevant documentation (e.g., 'backup-linux-azure-vm.md').
- Mention cross-platform support explicitly and clarify any differences in backup and retention policy configuration for Linux environments.
- Balance references to Windows tools (like DPM and MARS agent) with Linux equivalents or alternatives.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-backup-troubleshoot.md
...backup/azure-kubernetes-service-backup-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively referencing the Azure portal (a web GUI most commonly used on Windows) for configuration steps and omitting Linux-specific or cross-platform CLI alternatives for several key operations. All command-line examples use Azure CLI and kubectl, which are cross-platform, but there are no PowerShell-specific examples. However, the troubleshooting steps and screenshots consistently reference the Azure portal for configuration changes, with no mention of Linux-native tools or workflows (such as editing YAML manifests directly, using kubectl patch, or leveraging automation via shell scripting). This may disadvantage Linux administrators who prefer or require command-line or automation-centric workflows.
Recommendations
- Provide Linux-native CLI alternatives for all Azure portal steps, such as using az CLI or kubectl commands to update extension configurations, scale node pools, and assign roles.
- Include examples of editing YAML manifests directly and applying them with kubectl, rather than relying solely on portal screenshots.
- Clarify that all CLI commands (az, kubectl) are cross-platform and provide any OS-specific caveats if necessary.
- Add a section on automating troubleshooting and configuration tasks using shell scripts, which are common in Linux environments.
- Ensure that instructions do not assume access to a graphical interface and are fully reproducible in headless/server environments.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-userestapi-restoreazurevms.md
.../backup/backup-azure-arm-userestapi-restoreazurevms.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Os Type Windows Only
Summary
The documentation page demonstrates a subtle Windows bias. In example responses for recovery points, the 'osType' property is always set to 'Windows', and there are no examples or mentions of Linux VMs or their restore scenarios. There are no PowerShell or Windows tool references, but the examples and metadata consistently use Windows as the operating system, potentially implying that Windows is the default or only supported scenario.
Recommendations
- Include example responses and request bodies for Linux VMs (e.g., with 'osType': 'Linux').
- Explicitly mention that the REST API supports both Windows and Linux VMs, and highlight any differences in restore operations or metadata for Linux.
- Add a section or note clarifying cross-platform support and parity.
- Provide sample restore scenarios for Linux VMs, including any Linux-specific properties or considerations.
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
Powershell Heavy
Windows First
Summary
The documentation page contains a Windows bias primarily through its reference to the 'default PowerShell object' for PostgreSQL Flexible servers when describing backup scheduling and retention. PowerShell is a Windows-centric tool, and its mention as the default implies a Windows-first approach. There are no Linux-specific examples, nor are cross-platform CLI tools (such as Azure CLI) referenced. The examples and instructions focus on REST API and JSON, which are platform-neutral, but the only tooling context provided is PowerShell, with no mention of Linux alternatives.
Recommendations
- Replace or supplement references to 'default PowerShell object' with cross-platform alternatives, such as Azure CLI or direct REST API usage.
- Provide example commands for Linux environments, such as using curl or Azure CLI to interact with the REST API.
- Clarify that the REST API and JSON examples are platform-agnostic and can be used from any OS.
- If mentioning PowerShell, also mention its availability on Linux and macOS, or provide equivalent bash/shell examples.
- Avoid implying that PowerShell is the default or only way to interact with Azure Backup policies.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-integrate-microsoft-defender-using-logic-apps.md
...up-azure-integrate-microsoft-defender-using-logic-apps.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on Azure Virtual Machines without specifying or providing examples for Linux-based VMs. All workflow and alerting instructions reference Microsoft Defender for Cloud, Azure Backup, and Office 365, which are traditionally Windows-centric or Microsoft ecosystem tools. There are no examples, notes, or guidance for Linux VMs, Linux-specific security tools, or cross-platform considerations. The documentation implicitly assumes a Windows-first environment, and omits Linux parity in both prerequisites and operational steps.
Recommendations
- Explicitly mention support for both Windows and Linux Azure VMs in the scope and prerequisites.
- Provide examples or notes for Linux VM scenarios, including how ransomware detection and backup protection work for Linux VMs.
- Reference Linux-compatible security alerting and email solutions (e.g., integration with Sendmail/Postfix, or non-Office 365 options) where appropriate.
- Clarify whether the logic app workflow and Defender for Cloud integration applies equally to Linux VMs, and highlight any differences or additional steps required.
- Include troubleshooting or configuration notes for Linux VM users, such as permissions, agent installation, or alerting specifics.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-enhanced-policy.md
...in/articles/backup/backup-azure-vms-enhanced-policy.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides detailed PowerShell examples and cmdlets for configuring Enhanced backup policies, with step-by-step instructions and explanations. The PowerShell section is significantly more extensive than the Azure CLI section, which is more concise and lacks the same level of detail. There are no Linux-specific shell examples (e.g., Bash), nor are Linux tools or patterns mentioned. PowerShell (a Windows-centric tool) is presented before CLI, and the CLI section does not reference Linux usage or considerations.
Recommendations
- Add Linux/Bash shell examples for Azure CLI commands, including explicit instructions for Linux users (e.g., handling VM IDs, environment variables, JSON formatting).
- Ensure parity in detail between PowerShell and CLI sections, providing step-by-step CLI workflows similar to those given for PowerShell.
- Explicitly mention cross-platform compatibility for CLI commands, clarifying that they work on Linux, macOS, and Windows.
- Consider adding a 'Platform considerations' note that highlights differences or requirements for Linux users (such as authentication, environment setup, or file paths).
- Avoid presenting PowerShell before CLI, or alternate the order, to avoid implicit prioritization of Windows tools.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/blob-backup-configure-quick.md
...ob/main/articles/backup/blob-backup-configure-quick.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell as a restore method before Azure CLI, and by referencing PowerShell-specific instructions. There is no explicit mention of Linux shell examples or parity in command-line instructions, and PowerShell is typically associated with Windows environments.
Recommendations
- List Azure CLI instructions before or alongside Azure PowerShell to avoid Windows-first ordering.
- Provide explicit Linux shell examples and clarify cross-platform compatibility for command-line tools.
- Include notes or links for Linux users, such as installation and usage of Azure CLI and REST API from Linux environments.
- Avoid assuming PowerShell as the default scripting environment; mention Bash or other shells where appropriate.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-center-support-matrix.md
...b/main/articles/backup/backup-center-support-matrix.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by listing Windows-centric workloads (such as SQL in Azure VM, SAP HANA in Azure VM, System Center Data Protection Manager, Azure Backup Agent (MARS), and Azure Backup Server (MABS)) before or more prominently than Linux equivalents. Windows backup tools are mentioned (MARS, MABS, DPM) without Linux alternatives or parity explanations. There are no explicit Linux/Powershell example biases, but the workload and tool selection leans toward Windows environments.
Recommendations
- Explicitly mention Linux support for Azure VM backup scenarios, including supported Linux distributions and any limitations.
- Add references to Linux-native backup tools or workflows where appropriate, or clarify if only Windows tools are supported.
- Where workloads are listed (e.g., SQL in Azure VM, SAP HANA in Azure VM), clarify Linux compatibility or provide examples for Linux-based deployments.
- If certain features/tools are Windows-only (e.g., MARS, MABS, DPM), clearly state their platform limitations and suggest Linux alternatives or workarounds.
- Consider balancing the order of workload listings to avoid always listing Windows-centric workloads first.
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 exhibits Windows bias by providing a specific example for deploying a Windows Server VM with backup enabled, while omitting equivalent examples for Linux VMs. The SQL Server backup example also implicitly targets Windows workloads, as SQL Gallery images are typically Windows-based. There are no Linux-specific templates or examples, nor are Linux backup scenarios mentioned, despite their relevance in Azure environments.
Recommendations
- Add examples and templates for deploying and backing up Linux VMs, such as Ubuntu or CentOS, with Recovery Services vault integration.
- Include documentation and templates for backing up Linux-based workloads (e.g., MySQL, PostgreSQL on Linux VMs) alongside Windows/SQL Server examples.
- Ensure parity in monitoring and alerting examples by referencing both Windows and Linux VM scenarios.
- Explicitly mention cross-platform support in descriptions, clarifying that templates can be used for both Windows and Linux resources where applicable.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/encryption-at-rest-with-cmk.md
...ob/main/articles/backup/encryption-at-rest-with-cmk.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure portal, PowerShell, and Azure CLI for all major operations, but PowerShell is consistently presented before CLI, and detailed PowerShell examples are given. This ordering and emphasis reflects a Windows-first and PowerShell-heavy bias, as PowerShell is primarily a Windows-centric tool (even though it is cross-platform now, its usage is still more common on Windows). There is no mention of Linux-specific tools, shell scripts, or patterns, nor any acknowledgement of Linux user workflows outside of Azure CLI. The documentation does not provide bash or shell script examples, nor does it discuss integration with Linux-native automation tools.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support Linux users.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux and macOS users.
- Add bash/shell script snippets for common operations, especially for steps that require scripting or automation.
- Include notes or tips for Linux users, such as differences in authentication or environment setup.
- Reference Linux-native automation tools (e.g., Ansible, shell scripts) where appropriate, or link to relevant guides.
- Clarify that PowerShell is available on Linux, but CLI may be more familiar to Linux administrators.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-afs-backup-cli.md
...ocs/blob/main/articles/backup/manage-afs-backup-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is largely cross-platform and focused on Azure CLI, which is available on both Windows and Linux. However, there are subtle signs of Windows bias: (1) The introductory section lists Azure portal, Azure PowerShell, and REST API as alternatives, mentioning PowerShell before REST API and without mentioning Bash or Linux shell scripting; (2) In the Vault-Standard tier section, the example output includes a Windows file path (C:\Users\testuser\Downloads\CLIForAFS\azure-cli>), which may confuse Linux users or imply a Windows-centric workflow. No explicit Linux shell examples, Linux file paths, or Bash scripting are present, and no Linux-specific tools or patterns are referenced.
Recommendations
- Add explicit mention of Bash scripting and Linux shell environments as alternatives alongside PowerShell in the introduction.
- Ensure example outputs and file paths are platform-neutral or provide both Windows and Linux variants (e.g., show example CLI output from a Linux terminal as well).
- Include notes or examples for Linux users, such as how to redirect output to files (e.g., using > on Linux), and clarify that Azure CLI commands work identically on Linux and macOS.
- Where file paths are shown, use generic or cross-platform paths, or provide both Windows and Linux examples.
- Consider referencing Linux tools (such as jq for JSON processing) where relevant.
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 page focuses exclusively on Microsoft-centric backup tools (MARS Agent, MABS, DPM-A), which are Windows-only solutions. There are no mentions of Linux backup agents, Linux command-line utilities, or cross-platform workflows. All described utilities and workflows implicitly assume a Windows environment, with no guidance for Linux users or administrators.
Recommendations
- Include information about Linux-compatible backup agents or workflows, if available.
- Provide examples or references for performing offline backup from Linux systems, such as using Azure CLI, REST APIs, or third-party tools.
- Clarify platform requirements and limitations for each backup method, explicitly stating Windows-only support where applicable.
- If Linux is not supported, suggest alternative approaches for Linux users to achieve similar outcomes.
- Add documentation links or sections for cross-platform or Linux-specific backup scenarios.
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. The only explicit OS distinction is in the 'Install the VM agent' section, where Windows instructions (MSI installer, file path, executable name) are presented first and in greater detail, including version verification steps. Linux instructions are shorter, less detailed, and refer users to external package repositories and GitHub, with less guidance on verification. The initial VM creation link points to a Windows VM creation guide, with no mention of a Linux equivalent.
Recommendations
- Provide equal detail for Linux agent installation, including verification steps (e.g., checking agent version, service status, log file locations).
- Include a link to a Linux VM creation guide alongside the Windows VM creation link in the introduction.
- When listing OS-specific instructions, alternate the order or present them in parallel to avoid Windows-first bias.
- Mention common Linux troubleshooting steps for the agent, similar to the Windows update/reinstall guidance.
- Ensure screenshots and examples are OS-neutral or include both Windows and Linux variants where relevant.
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 UI for configuration steps and screenshots, with no mention of command-line or automation options until the very end, where Azure CLI is listed as a next step but not demonstrated in the main flow. There are no examples using Linux-native tools, shell commands, or cross-platform automation (e.g., Bash, kubectl, or Azure CLI in the main instructions). This approach implicitly favors Windows users who are more likely to use the portal, and may disadvantage Linux users who prefer command-line workflows.
Recommendations
- Add parallel instructions using Azure CLI for each configuration step, with sample commands.
- Include examples using Bash or shell scripts for automation, where applicable.
- Reference kubectl commands for relevant cluster operations.
- Ensure screenshots and UI references are supplemented with text-based, cross-platform alternatives.
- Clarify that all steps can be performed on Linux, macOS, or Windows, and provide explicit guidance for non-Windows environments.
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 a file path example using Windows-style (C:\temp2\Policy.json) and does not mention or show Linux/macOS equivalents (e.g., /home/user/Policy.json). All CLI examples use generic Azure CLI commands, but the file path usage and lack of Linux-specific notes or examples indicate a Windows-first bias and missing Linux parity.
Recommendations
- Include Linux/macOS file path examples (e.g., /home/user/Policy.json) alongside Windows paths.
- Add a note clarifying that file paths should be adapted to the user's operating system.
- Explicitly mention that Azure CLI works cross-platform and provide examples for both Windows and Linux environments.
- Consider showing command examples for both Windows (cmd/PowerShell) and Linux (bash) where file paths or environment specifics differ.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-hana-database-instance-troubleshoot.md
...cles/backup/sap-hana-database-instance-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently refers to 'Azure VM' and troubleshooting steps for SAP HANA backups, but does not specify or provide examples for Linux-based Azure VMs, which are the typical platform for SAP HANA. There are no Linux-specific commands, tools, or references (e.g., shell commands, Linux role assignment patterns), nor is there mention of Linux administration practices. The guidance is generic and could be interpreted as Windows-centric due to the lack of explicit Linux parity.
Recommendations
- Explicitly state that SAP HANA is typically run on Linux VMs and clarify that instructions apply to Linux-based Azure VMs.
- Provide Linux-specific examples for enabling managed identity and assigning roles, such as using Azure CLI or shell commands.
- Include troubleshooting steps or references for common Linux administration tasks relevant to SAP HANA backup and restore (e.g., mounting disks, checking file system types).
- Mention Linux file system support more prominently and provide guidance for verifying and changing file systems on Linux.
- Add links to Linux-specific Azure documentation for VM management and role assignment.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-hana-database-about.md
...s/blob/main/articles/backup/sap-hana-database-about.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses on backing up SAP HANA databases on Azure VMs, but does not provide explicit examples or instructions for Linux environments, despite SAP HANA typically running on Linux. There are no references to Linux-specific tools, commands, or shell examples, and the documentation does not clarify OS requirements or differences. While Windows-specific tools like PowerShell are not mentioned, the lack of Linux parity and the general assumption of Azure VM usage without OS context suggests a subtle Windows-first bias.
Recommendations
- Explicitly state that SAP HANA is generally deployed on Linux and clarify OS requirements for the backup process.
- Provide Linux shell (bash) command examples for running the preregistration script and managing backups.
- Mention any OS-specific considerations, such as permissions, package dependencies, or service management differences between Windows and Linux.
- If Windows is supported, provide parity by including both Windows (PowerShell) and Linux (bash) examples for all relevant steps.
- Reference Linux-native tools and patterns where appropriate, such as systemd for service management, and clarify any differences in backup plugin installation or operation between OSes.
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. In the 'Install the VM agent' section, instructions for Windows appear first and are more detailed, including links to MSI installers and explicit file paths. The Linux instructions are less detailed and refer to distribution repositories, with a secondary mention of GitHub. The initial VM creation link points to a Windows-specific quickstart, and there is no mention of Linux VM creation or parity in portal operations. No PowerShell or CLI examples are present, and most steps are portal-based and OS-agnostic, but where OS-specific details are given, Windows is prioritized.
Recommendations
- Present Linux instructions before or alongside Windows instructions in the VM agent installation section.
- Provide a link to the Linux VM creation quickstart in the introduction, alongside the Windows VM creation link.
- Expand Linux agent installation details, including example commands for RPM/DEB installation and verification steps.
- Ensure that screenshots and examples do not implicitly assume Windows VMs; clarify when steps apply equally to Linux VMs.
- Add a note on any OS-specific backup considerations, such as application consistency or agent limitations, for both Windows and Linux.
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 exhibits mild Windows bias. The only explicit OS-specific section is 'Install the VM agent', where Windows instructions (MSI installer, file path, executable name) are listed first and in more detail, while Linux instructions are more generic and less step-by-step. The initial VM creation link points to a Windows VM guide, not a Linux one. There are no PowerShell or CLI examples, but Windows-specific tools and patterns are mentioned before Linux equivalents.
Recommendations
- Provide equal, step-by-step instructions for installing/updating the Linux agent, including example commands for RPM/DEB installation.
- Add a link to the Linux VM creation quickstart alongside the Windows VM creation link.
- Ensure that screenshots and examples are OS-neutral or provide both Windows and Linux variants where relevant.
- Mention Linux agent version verification steps, similar to the Windows agent verification.
- Review all sections for implicit prioritization of Windows tools and rephrase to treat Windows and Linux equally.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-userestapi-restoreazurevms.md
.../backup/backup-azure-arm-userestapi-restoreazurevms.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is generally platform-neutral in its REST API focus, but there are subtle signs of Windows bias. Specifically, in several example responses (notably in the Cross Region Restore section), the 'osType' and 'OsType' fields are set to 'Windows', and VM size examples reference Windows-centric naming. There are no explicit Linux or cross-platform examples, and no mention of Linux-specific considerations or sample payloads. No PowerShell or CLI examples are present, but the implicit assumption of Windows as the default OS in examples suggests a 'windows_first' approach.
Recommendations
- Include example responses and request bodies that show both 'osType': 'Linux' and 'osType': 'Windows' to demonstrate parity.
- Explicitly mention that the APIs work for both Windows and Linux VMs, and note any differences if they exist.
- Where VM configuration or disk restore is discussed, provide examples or notes for restoring Linux VMs (e.g., handling of Linux-specific boot or disk configurations).
- If referencing VM sizes or storage types, include examples that are common for Linux workloads as well.
- Add a section or note on any Linux-specific restore considerations (e.g., file system compatibility, agent requirements, etc.).
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
Powershell Heavy
Windows First
Summary
The documentation page exhibits a Windows bias primarily through repeated references to PowerShell objects as the default or primary way to conceptualize and configure backup policies. The term 'PowerShell object' is used multiple times to describe the policy structure, and no equivalent Linux or cross-platform command-line tooling (such as Azure CLI, Bash, or curl) is mentioned. There are no Linux-specific examples or references, and the documentation implicitly assumes familiarity with Windows/PowerShell paradigms.
Recommendations
- Replace or supplement references to 'PowerShell object' with neutral terms such as 'policy object' or 'JSON policy definition', unless specifically discussing PowerShell scripting.
- Add equivalent examples using Azure CLI and/or curl for creating and managing backup policies, demonstrating how to interact with the REST API from Linux or cross-platform environments.
- Explicitly mention that the REST API can be used from any platform, and provide sample commands for both Windows (PowerShell) and Linux/macOS (Bash, curl, Azure CLI).
- Avoid assuming PowerShell as the default scripting or automation environment; provide parity in documentation for Linux users.
- Include a section or callout for Linux/macOS users, highlighting any differences or tips for using the REST API from non-Windows systems.