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 1576-1600 of 1604 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page does not provide explicit Windows or PowerShell command examples, nor does it mention Windows-specific tools or patterns in the main REST API workflow. However, in the introductory and 'Next steps' sections, Windows-centric tools (Azure portal, Azure PowerShell) are listed before cross-platform options like Azure CLI, suggesting a subtle 'windows_first' ordering bias. No Linux-specific examples, tools, or guidance are provided, and parity between platforms is not explicitly addressed.
Recommendations
- List Azure CLI before Azure PowerShell and Azure portal in tool references to emphasize cross-platform support.
- Explicitly mention that REST API and Azure CLI are fully supported on Linux and macOS, and provide links to platform-specific setup guides.
- Add example workflows or command snippets for Linux environments (e.g., using curl, jq, or Azure CLI on Linux) to demonstrate parity.
- Include a brief section on platform compatibility, clarifying that all REST API operations are OS-agnostic and can be performed from Linux, macOS, or Windows.
- Where possible, avoid ordering tools in a way that implies Windows is the default or preferred platform.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides instructions for restoring Azure Managed Disks and includes steps for attaching/restoring disks to both Windows and Linux virtual machines. However, the instructions for Windows VMs are presented before those for Linux VMs, indicating a 'windows_first' bias. There are no PowerShell-heavy examples, exclusive mention of Windows tools, or missing Linux examples; both platforms are covered with portal-based instructions and links.
Recommendations
- Present instructions for Windows and Linux virtual machines in parallel or alternate the order to avoid implicit prioritization.
- Explicitly state that the steps apply equally to both Windows and Linux VMs where applicable.
- Ensure that any screenshots or examples are balanced between Windows and Linux environments.
- If command-line examples (PowerShell, CLI) are provided in linked documents, verify that Linux equivalents are present and equally detailed.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-azure-file-share-rest-api.md
...n/articles/backup/restore-azure-file-share-rest-api.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page does not provide explicit Windows or Linux command-line examples, focusing solely on REST API calls and JSON payloads. However, in the introductory and 'Next steps' sections, Windows-centric tools (Azure portal, Azure PowerShell) are mentioned before Azure CLI, which is more commonly used on Linux/macOS. There are no Linux-specific examples, nor is there mention of Linux tools or shell environments. The REST API usage itself is cross-platform, but the ordering of alternative tools reflects a subtle Windows-first bias.
Recommendations
- When listing alternative management tools (portal, PowerShell, CLI), alternate or randomize the order, or explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Include example REST API invocations using curl or httpie, which are standard on Linux/macOS, alongside any PowerShell or Windows tool examples.
- Add a note clarifying that the REST API can be used from any OS, and provide sample shell commands for both Windows (PowerShell) and Linux/macOS (bash/curl).
- Where possible, link to Linux-specific guides or CLI usage patterns to ensure parity and inclusivity.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-policy-supported-skus.md
.../articles/backup/backup-azure-policy-supported-skus.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page lists supported VM SKUs for Azure Backup policies, presenting a long and detailed enumeration of Windows-based SKUs first, including many variants and specialized images. Linux distributions are listed only after all Windows SKUs, with less granularity and fewer details. There are no examples, tools, or patterns specific to either platform, but the ordering and detail level suggest a bias toward Windows.
Recommendations
- Reorder the table to group Windows and Linux SKUs separately, or alternate between Windows and Linux entries to avoid implicit prioritization.
- Provide equal granularity for Linux SKUs, including more details about supported variants, image options, and any special cases (e.g., smalldisk, containers, BYOS) if applicable.
- Add clarifying notes about Linux support, including any limitations or additional configuration requirements, to match the detail given for Windows SKUs.
- Explicitly state that the order of listing does not indicate priority or recommendation, or present the lists alphabetically by publisher.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-monitor-sql-database-backup.md
.../articles/backup/manage-monitor-sql-database-backup.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation focuses exclusively on managing and monitoring SQL Server databases on Azure VMs via the Azure portal, with no mention of or examples for Linux-based SQL Server VMs. There are no references to Linux tools, command-line instructions, or platform-specific considerations for Linux, despite SQL Server being supported on Linux. All screenshots and UI references implicitly assume a Windows-centric environment.
Recommendations
- Explicitly state whether the instructions apply to both Windows and Linux SQL Server VMs, or clarify any differences.
- Add sections or notes describing any Linux-specific considerations for SQL Server on Azure VMs, such as extension installation, backup agent support, or troubleshooting steps.
- Provide examples or links for managing and monitoring SQL Server on Linux VMs using the Azure CLI, REST API, or native Linux tools (e.g., bash scripts, systemd integration).
- If certain features are not supported on Linux, clearly document these limitations.
- Include screenshots or walkthroughs for Linux-based SQL Server VMs where the experience differs.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-blobs.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-blobs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Azure portal, PowerShell, and REST API as options for assigning permissions, but does not mention Azure CLI or Linux-native tools in the main workflow. PowerShell is referenced before CLI in the related content, and no Linux-specific examples or shell commands are provided. The examples and instructions are platform-neutral, but the ordering and omission of Linux/CLI options suggest a subtle Windows-first bias.
Recommendations
- Explicitly mention Azure CLI as an option for all operations where PowerShell is listed, especially in the 'Assign permissions' section.
- Provide example commands using Azure CLI (az) alongside PowerShell and REST API examples.
- Include notes or examples for Linux/macOS users, such as using curl for REST API calls and az CLI for resource management.
- Ensure that references to PowerShell and CLI are presented together or in a neutral order, rather than listing PowerShell first.
- Add a 'Cross-platform usage' section summarizing how to perform all documented operations from Linux, macOS, and Windows environments.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-policy-supported-skus.md
.../articles/backup/backup-azure-policy-supported-skus.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page lists supported VM SKUs for Azure Backup Policy, presenting Windows-based SKUs first and in much greater detail than Linux-based SKUs. The Windows section is extensive, with many variants and specializations, while Linux distributions are grouped and listed with fewer details. No Linux-specific backup notes, examples, or parity considerations are provided.
Recommendations
- Reorder the table or provide separate sections for Windows and Linux SKUs to give equal visibility.
- Expand the Linux section to include more details about supported variants, backup limitations, and any special considerations (e.g., LVM, SR-IOV, SAP, BYOS).
- Add notes or examples specific to Linux backup scenarios, such as handling custom images, kernel versions, or file system types.
- Clarify any differences in backup feature support between Windows and Linux VMs.
- Include guidance or links for Linux users on how to verify compatibility and configure backup for their distributions.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-monitor-sql-database-backup.md
.../articles/backup/manage-monitor-sql-database-backup.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation focuses exclusively on managing and monitoring SQL Server databases on Azure VMs using the Azure portal, with references to Azure CLI and REST API. However, it does not provide any platform-specific examples or instructions, and it does not mention or address Linux-based SQL Server VMs or their management nuances. There are no Windows-specific tools or PowerShell commands, but the absence of Linux-specific guidance or examples constitutes a subtle bias, especially since SQL Server is supported on Linux.
Recommendations
- Explicitly mention support for SQL Server on Linux VMs where applicable, and clarify if any features or steps differ for Linux.
- Provide examples or notes for managing SQL Server on Linux-based Azure VMs, especially for tasks that may differ (e.g., extension installation, backup agent behavior, or file system considerations).
- Include links to documentation or troubleshooting guides specific to SQL Server on Linux in Azure VMs.
- If certain features are only available or behave differently on Windows vs. Linux, clearly state these differences to ensure Linux users are informed.
- Where CLI or REST API is mentioned, provide example commands that are platform-agnostic or show both Windows and Linux shell syntax.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-managed-disks.md
...ocs/blob/main/articles/backup/restore-managed-disks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides instructions for restoring Azure Managed Disks and includes guidance for both Windows and Linux virtual machines. However, the instructions for Windows VMs are consistently presented before those for Linux VMs, indicating a 'windows_first' bias. There are no PowerShell-heavy examples, exclusive Windows tools, or missing Linux examples; parity is maintained in the steps and linked resources.
Recommendations
- Alternate the order in which Windows and Linux instructions are presented, or present them side-by-side to avoid implicit prioritization.
- Explicitly state that the steps apply equally to both Windows and Linux VMs where possible, and only differentiate when necessary.
- Review linked resources to ensure Linux documentation is as comprehensive and accessible as Windows documentation.
- Consider adding a table or section that summarizes differences and similarities between Windows and Linux disk restore operations for clarity.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-azure-file-share-rest-api.md
...n/articles/backup/restore-azure-file-share-rest-api.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page does not provide explicit Windows or Linux command-line examples, focusing solely on REST API calls and JSON payloads. However, in the introductory and closing sections, Windows-centric tools (Azure portal, Azure PowerShell) are consistently mentioned before Azure CLI, which is the primary cross-platform tool for Linux users. There are no Linux-specific examples, nor is there mention of Linux-native tools or patterns.
Recommendations
- List Azure CLI before Azure PowerShell and Azure portal when enumerating alternative management options, to reflect cross-platform parity.
- Explicitly mention that REST API examples are platform-agnostic and can be used from any OS, including Linux, macOS, and Windows.
- Provide example REST API invocations using common Linux tools (e.g., curl, jq) alongside the HTTP request samples, demonstrating usage from a Linux shell.
- Add a section or note highlighting how Linux users can automate these REST API calls using bash scripts or other Linux-native automation tools.
- Ensure parity in documentation references, e.g., link to both PowerShell and CLI guides when mentioning alternative approaches.
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
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation exhibits a mild 'windows_first' bias by linking to the Windows VM creation guide before the Linux equivalent and referencing Windows VM creation in the introductory section. However, throughout the rest of the document, instructions and examples are platform-neutral, focusing on the Azure portal UI. The only OS-specific section, about installing the VM agent, provides both Windows and Linux instructions with equal detail.
Recommendations
- When referencing VM creation, provide links to both Windows and Linux quickstart guides, or use a neutral link that allows the user to choose their OS.
- Ensure that introductory examples and links do not prioritize Windows over Linux unless there is a technical reason.
- Continue to provide parity in OS-specific instructions, as done in the VM agent installation section.
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
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a 'windows_first' bias, as it references Windows-specific VM creation instructions before Linux equivalents and provides a more detailed, step-by-step installation process for the Windows VM agent compared to Linux. However, both Windows and Linux agent installation methods are mentioned, and the rest of the guide is largely platform-agnostic, focusing on the Azure portal UI.
Recommendations
- Provide parallel links to both Windows and Linux VM creation guides in the introduction, or use a neutral link that covers both.
- Ensure that installation instructions for the VM agent are equally detailed for both Windows and Linux, including explicit commands or steps for common Linux distributions.
- Where possible, present Windows and Linux instructions side-by-side or in tabs, rather than listing Windows first.
- Review all screenshots and examples to ensure they are not Windows-centric and represent both platforms where relevant.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-vms-prepare.md
...b/main/articles/backup/backup-azure-arm-vms-prepare.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally presents a balanced approach for both Windows and Linux Azure VMs, especially in the 'Install the VM agent' section, where both platforms are given clear instructions. However, there is a subtle 'windows_first' bias: in the VM agent installation table, Windows instructions are listed before Linux, and the Windows process is described in more detail (with explicit verification steps and version numbers), while the Linux process is more general and refers to distribution repositories. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present elsewhere in the document.
Recommendations
- Present Linux and Windows instructions in parallel or alternate the order in which they are described to avoid implicit prioritization.
- Provide equally detailed verification steps for Linux agent installation (e.g., how to check the agent version and service status on Linux).
- Where possible, offer command-line examples for both Windows (PowerShell/Command Prompt) and Linux (bash/CLI) for common tasks, even if the Azure Portal is the main method.
- Explicitly state that all steps apply equally to both Windows and Linux VMs unless otherwise noted.
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
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not show overt Windows bias in terms of prioritizing Windows tools, PowerShell, or Windows-specific workflows. However, it lacks explicit Linux parity: there are no command-line examples (such as Bash, psql, or Azure CLI) for Linux users, and the only client tool mentioned for database access is pgAdmin (a cross-platform GUI), with no mention of CLI alternatives. There are no PowerShell or Windows-only tools mentioned, but the absence of Linux command-line guidance may disadvantage Linux-first users.
Recommendations
- Add examples for connecting to Azure Database for PostgreSQL using the psql command-line tool, including connection string formats and authentication steps.
- Provide Azure CLI commands for managing permissions, backup, and restore operations, in addition to (or instead of) portal screenshots.
- Mention and provide examples for Linux-native workflows, such as using Bash scripts for automation.
- Clarify that pgAdmin is cross-platform, and suggest alternative tools (e.g., psql) for users who prefer command-line interfaces.
- Ensure that all steps (such as firewall configuration and credential management) are documented with both GUI and CLI options.
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
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation exhibits a subtle 'windows_first' bias: the only explicit link for VM creation is to the Windows VM quickstart, and in the VM agent installation section, Windows instructions are listed before Linux. However, both Windows and Linux agent installation steps are present, and the rest of the documentation is platform-neutral, focusing on the Azure portal UI.
Recommendations
- Provide parallel links for both Windows and Linux VM creation in the introduction, e.g., 'create a VM with the Azure portal (Windows | Linux)'.
- Alternate the order of Windows and Linux instructions in the VM agent installation section, or present them side-by-side.
- Ensure all screenshots and UI references are clearly applicable to both Windows and Linux VMs, or clarify any differences.
- Where possible, mention Linux-specific considerations (e.g., agent verification steps) with the same level of detail as Windows.
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
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions PowerShell as the first automation client for running ARG queries, followed by CLI and SDK, which may suggest a Windows-first bias. However, it does also mention Azure CLI and SDK, which are cross-platform, and does not provide any OS-specific command-line examples. No PowerShell-specific scripts or Windows-only tools are shown, and the Kusto queries are platform-agnostic.
Recommendations
- List Azure CLI before PowerShell when mentioning automation clients, as CLI is cross-platform and more accessible to Linux users.
- Explicitly state that both PowerShell and Azure CLI are supported on Windows, Linux, and macOS.
- Provide example commands for both PowerShell and Azure CLI (or Bash) to demonstrate parity.
- Include links to Linux/macOS installation guides for Azure CLI and PowerShell to reinforce cross-platform support.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-userestapi-createorupdatepolicy.md
...up/backup-azure-arm-userestapi-createorupdatepolicy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation does not explicitly show Windows bias in terms of tools, PowerShell, or Windows-specific commands. However, there is a subtle 'windows_first' bias: the default time zone in several examples is 'Pacific Standard Time', which is a Windows time zone identifier and not a standard IANA time zone (used in Linux/Unix environments). Additionally, the documentation does not clarify time zone compatibility or provide guidance for Linux users who may expect IANA time zones. No explicit Linux examples or parity notes are present.
Recommendations
- Clarify in the documentation whether the 'timeZone' property accepts IANA time zone identifiers (e.g., 'America/Los_Angeles') or only Windows time zone IDs (e.g., 'Pacific Standard Time').
- Add a note or table mapping common Windows time zones to IANA equivalents for cross-platform clarity.
- Provide examples using both Windows and IANA time zone formats, if supported.
- Explicitly state any platform limitations or requirements for time zone values.
- Consider including a Linux-focused example or guidance for users managing backup policies from Linux environments.
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
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains OS neutrality by focusing on the Azure Portal UI for backup operations, which is cross-platform. However, in the 'Install the VM agent' section, instructions for Windows appear first, with more explicit step-by-step guidance and direct download links, while Linux instructions are less detailed and refer users to external package repositories. This ordering and level of detail indicate a subtle 'windows_first' bias.
Recommendations
- Present Linux and Windows instructions in parallel or alternate their order in different sections to avoid always listing Windows first.
- Provide equally detailed, step-by-step instructions for installing the Azure Linux agent, including example commands for popular distributions (e.g., apt, yum, zypper).
- Include direct links to official documentation for both Windows and Linux agent installation and update procedures.
- Explicitly state that all portal-based operations are OS-agnostic to reinforce cross-platform applicability.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-managed-disks-policy.md
...ob/main/articles/backup/backup-managed-disks-policy.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes how to configure Azure Policy for Managed Disks backup using the Azure Portal UI, without providing any command-line examples. There are no references to Windows-specific tools, but there is also a lack of parity for Linux users: no CLI (Azure CLI, Bash) or PowerShell examples are given, and no mention of automation or scripting approaches that are platform-neutral. This omission may disadvantage Linux-first users or those who prefer non-GUI workflows.
Recommendations
- Add examples using Azure CLI commands to assign and manage backup policies for Managed Disks, ensuring Linux and cross-platform users have clear guidance.
- If relevant, provide PowerShell examples as well, but ensure Azure CLI or REST API examples are given equal or higher prominence.
- Include a section on automating policy assignment using scripts (Bash, Python, etc.) for users who manage resources programmatically.
- Explicitly mention that all steps can be performed via CLI or REST API, and link to relevant documentation for those workflows.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/blob-backup-support-matrix.md
...lob/main/articles/backup/blob-backup-support-matrix.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples, commands, or tooling references (such as Windows, PowerShell, Linux, or CLI). However, it also does not include any Linux-specific guidance or parity examples, and the 'Next steps' and 'Related content' sections only reference REST API documentation, with no mention of command-line tools or scripts for either Windows or Linux. This absence of platform-specific examples may disadvantage Linux users who often rely on CLI or scripting guidance.
Recommendations
- Add example workflows for both Windows (PowerShell, Azure CLI in Windows) and Linux (Bash, Azure CLI in Linux) for common backup and restore operations.
- Include references to cross-platform tools such as Azure CLI and show example commands for both operating systems.
- If any platform-specific limitations exist, explicitly document them for both Windows and Linux.
- Provide links to documentation or quickstarts for both PowerShell and Bash/CLI usage to ensure parity.
- Consider adding a section on automating blob backup and restore using scripts, with examples for both Windows and Linux environments.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-cross-region-restore.md
.../main/articles/backup/tutorial-cross-region-restore.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal (web UI) for all configuration and restore steps, with no command-line examples provided for either Windows (PowerShell/CLI) or Linux (Bash/CLI). However, there is an implicit bias due to the absence of any Linux-specific guidance or CLI examples, which are common for cross-platform parity. There is no mention of PowerShell, Windows tools, or Windows-first ordering, but the lack of Linux/CLI examples may disadvantage Linux users who prefer or require automation or non-GUI workflows.
Recommendations
- Add Azure CLI (az) command examples for each step, ensuring they work on both Windows and Linux shells.
- Explicitly mention that all steps can be performed via CLI or provide links to CLI documentation.
- Include Bash shell scripts or command snippets for Linux users where appropriate.
- If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are provided alongside.
- Clarify any platform-specific differences in backup/restore workflows, if they exist.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-manage-backups.md
...kup/azure-kubernetes-service-cluster-manage-backups.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only Azure CLI and Azure Portal instructions, with no explicit Windows or PowerShell bias. However, it lacks any Linux-specific examples or terminal/shell guidance, which may disadvantage Linux users who commonly manage AKS clusters. The 'Next steps' section links to a PowerShell guide but does not mention Bash or Linux shell equivalents.
Recommendations
- Add explicit Linux/Bash shell examples where relevant, especially for Azure CLI commands (e.g., show both Windows CMD/PowerShell and Bash syntax for environment variables, command substitution, etc.).
- Clarify that Azure CLI commands are cross-platform and provide notes or tips for Linux/macOS users (e.g., differences in command substitution: $(...) vs %...%).
- Include links to Linux/Bash-specific AKS backup documentation in the 'Next steps' section, or clarify that the Azure CLI instructions are suitable for Linux/macOS.
- If any scripts or automation are referenced, provide both PowerShell and Bash versions.
- Explicitly state platform compatibility at the start of the article to reassure non-Windows users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/back-up-azure-database-postgresql-flex-backup-cli.md
...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, using Azure CLI commands and Bash variable syntax, which are compatible with both Windows and Linux. However, there is one instance where a Windows-specific file path ('.\OSSBkpInstance.JSON') is used in a command example, which may confuse Linux users who expect './OSSBkpInstance.JSON'. No PowerShell-specific commands or Windows-only tools are present, but the single use of a Windows path separator suggests a subtle 'windows_first' bias.
Recommendations
- Replace Windows-style file paths (e.g., '.\OSSBkpInstance.JSON') with POSIX-style paths (e.g., './OSSBkpInstance.JSON'), or provide both variants to accommodate both Windows and Linux users.
- Explicitly state that the Azure CLI commands work on both Windows and Linux, and clarify any platform-specific differences in file paths or environment variable syntax.
- Where file paths or shell syntax are shown, consider using cross-platform conventions or add notes for both environments.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-userestapi-createorupdatepolicy.md
...up/backup-azure-arm-userestapi-createorupdatepolicy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page does not show overt Windows bias in terms of examples or tools (e.g., no PowerShell, CMD, or Windows-specific tooling is present). However, there is a subtle bias in the use of 'Pacific Standard Time' as the default time zone in several example request bodies, and in the ordering of examples (e.g., Azure VM, SQL in Azure VM, SAP HANA in Azure VM) which are most commonly associated with Windows workloads. There are no explicit Linux or cross-platform command-line examples, but since the page is focused on REST API usage, this is less critical. No Linux-specific examples or references are missing, but the use of a Windows-centric time zone as a default may suggest a slight Windows-first orientation.
Recommendations
- Use 'UTC' as the default time zone in all examples to avoid regional or OS-specific bias.
- Explicitly mention that the REST API is platform-agnostic and can be used from any OS or environment.
- If possible, provide example REST API invocations using common cross-platform tools (e.g., curl, HTTPie) to reinforce platform neutrality.
- Consider including a note or example for Linux administrators, especially if there are any platform-specific considerations for time zones or date formats.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-vms-prepare.md
...b/main/articles/backup/backup-azure-arm-vms-prepare.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains platform neutrality, but in the 'Install the VM agent' section, instructions for Windows are presented before Linux. Both platforms are covered with similar detail, and no exclusive use of Windows tools, PowerShell, or missing Linux examples are observed elsewhere in the document.
Recommendations
- Present Linux and Windows instructions in parallel columns or in the order most relevant to the audience, or alternate which platform appears first in different sections.
- Ensure that any command-line or scripting examples (if added in the future) include both Windows (PowerShell/Command Prompt) and Linux (Bash/CLI) equivalents.
- Continue to avoid exclusive references to Windows tools or patterns unless there is no Linux equivalent, and always provide Linux alternatives where possible.