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 1551-1575 of 1604 flagged pages
Backup
Create backup policies via REST API in Azure Backup
...up/backup-azure-arm-userestapi-createorupdatepolicy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page does not show explicit bias toward Windows in terms of tooling, commands, or examples (e.g., PowerShell, CMD, Windows-specific tools), nor does it omit Linux/macOS equivalents. However, it consistently uses 'Pacific Standard Time' as the default time zone in several examples, which is a Windows-centric time zone identifier and can be problematic for Linux/macOS users who typically use IANA/Olson time zone names (e.g., 'America/Los_Angeles'). The time zone examples and references appear before UTC-based examples, indicating a subtle 'windows_first' bias.
Recommendations
- Clarify which time zone identifiers are supported (Windows vs. IANA/Olson) and provide guidance for Linux/macOS users.
- Include examples using IANA/Olson time zone names if supported, or explicitly state that only Windows time zones are accepted.
- If possible, provide parity by showing both 'Pacific Standard Time' and 'America/Los_Angeles' in examples.
- Add a note about time zone compatibility for cross-platform users.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Metadata
Summary
The documentation is largely platform-neutral, focusing on REST API calls and JSON request/response bodies. However, there is a subtle Windows bias in metadata and examples: VM sizes and OS types in sample responses are consistently Windows-centric (e.g., "osType": "Windows"), and there are no explicit Linux/macOS examples or references. No PowerShell, CLI, or Windows-specific tooling is mentioned, but the examples and metadata may suggest Windows as the default or primary use case.
Recommendations
- Include sample responses and request bodies featuring Linux VMs (e.g., set "osType": "Linux" in example responses).
- Add a note clarifying that the REST API works equally for Windows and Linux VMs, and highlight any differences if they exist.
- Where VM configuration or metadata is shown, alternate between Windows and Linux examples, or show both.
- If there are platform-specific considerations (e.g., disk formats, encryption), document them explicitly for both Windows and Linux.
Backup
Create backup policies for Azure database for PostgreSQL - Flexible server using data protection REST API in Azure Backup
...base-postgresql-flex-use-rest-api-create-update-policy.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation contains minor Windows bias: it references the 'default PowerShell object' for PostgreSQL Flexible servers as the baseline for backup scheduling and retention, without mentioning Linux or cross-platform equivalents. No Linux/macOS-specific examples, tools, or CLI references are provided, and the only tool mentioned is PowerShell, which is traditionally Windows-centric (though now cross-platform). However, the main workflow is REST API-based and platform-neutral, and all code samples are in JSON/HTTP, which are OS-agnostic.
Recommendations
- Replace or supplement the 'default PowerShell object' reference with Azure CLI or Bash examples, or clarify that PowerShell is available cross-platform.
- Explicitly mention that REST API operations can be performed from any OS using tools like curl, Postman, or Azure CLI.
- Add example commands for Linux/macOS users (e.g., curl or Azure CLI) to demonstrate how to create backup policies.
- Avoid implying PowerShell as the only or default method; provide parity for Linux/macOS users.
Backup
Back up Azure Disks using Azure Data Protection REST API.
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-disks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page is largely platform-neutral, focusing on REST API usage with HTTP requests and JSON bodies, which are cross-platform. However, there is a subtle Windows bias in the 'Assign permissions' section, where the link for assigning permissions points to a PowerShell-based page (backup-managed-disks-ps.md), and PowerShell is mentioned before Azure CLI. No Linux-specific tools or examples are provided, and the only explicit tool reference is to PowerShell, which is more commonly used on Windows.
Recommendations
- Provide explicit Azure CLI examples for permission assignment alongside or before PowerShell examples.
- Ensure links for prerequisite steps (like assigning permissions) reference both PowerShell and Azure CLI documentation, or a platform-neutral page.
- Add a note clarifying that all REST API operations can be performed from any OS using tools like curl, Postman, or native scripting languages.
- Where possible, show example commands using curl for Linux/macOS users.
Backup
Overview of Recovery Services vaults
...ackup/backup-azure-recovery-services-vault-overview.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. It references Windows-centric backup tools (System Center DPM, Windows Server, Azure Backup Server) and provides a direct link to backing up Windows Server, while Linux equivalents are not mentioned or linked. Windows workloads and tools are listed before Linux, and no Linux-specific backup instructions or examples are provided.
Recommendations
- Include explicit references and links to Linux backup scenarios, such as backing up Linux VMs or workloads.
- Add examples or documentation links for Linux backup agents or procedures, if available.
- Balance the order of mentioning Windows and Linux workloads/tools to avoid Windows-first presentation.
- Ensure parity in 'Next steps' by providing Linux VM backup instructions alongside Windows Server backup.
Backup
Back Up an Azure Virtual Machine with Azure Extended Zones Portal
...ain/articles/backup/backup-azure-vms-extended-zones.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is primarily focused on using the Azure Portal, which is cross-platform, but in the 'Install the VM agent' section, Windows instructions are presented first and in more detail, including download links and verification steps. The Linux instructions are less detailed, lack explicit command examples, and do not provide step-by-step installation or verification guidance. There are no PowerShell or Windows-only tool references elsewhere, but the agent installation section shows a mild Windows bias.
Recommendations
- Provide explicit Linux installation commands (e.g., 'sudo apt-get install walinuxagent' or 'sudo yum install WALinuxAgent') for common distributions.
- Include verification steps for Linux agent installation (e.g., checking agent version with 'waagent --version').
- Present Windows and Linux instructions in parallel or in separate, equally detailed subsections.
- Add links to official Linux package documentation or troubleshooting guides.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation primarily describes how to back up Azure Managed Disks using the Azure portal, which is cross-platform. However, when mentioning automation or scripting, PowerShell is listed before Azure CLI, and there are no explicit Linux/macOS-specific examples or guidance. The references to scripts and automation link to PowerShell and CLI documentation, but PowerShell is mentioned first, and there are no sample bash scripts or Linux/macOS terminal screenshots. The documentation does not mention any Windows-specific tools, but the ordering and lack of Linux/macOS parity in examples indicate a mild Windows bias.
Recommendations
- When referencing automation, mention Azure CLI before or alongside PowerShell to reflect cross-platform parity.
- Include explicit Linux/macOS examples, such as bash scripts or CLI commands run from a Linux terminal.
- Add screenshots or terminal output from Linux/macOS environments where applicable.
- Clarify that all CLI steps work on Linux/macOS and Windows, and provide troubleshooting tips for non-Windows platforms if needed.
Backup
Tutorial - Configure vaulted backup for Azure Blobs using Azure Backup
...main/articles/backup/blob-backup-configure-tutorial.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation references Azure PowerShell before Azure CLI and REST API in the 'Related content' section, suggesting a Windows-first approach. While CLI and REST API options are mentioned, PowerShell is listed first, which may subtly prioritize Windows tooling. No explicit Linux/macOS examples or tools are highlighted, and there is no indication of platform-specific instructions or parity checks.
Recommendations
- List Azure CLI before PowerShell in cross-platform documentation, as CLI is natively supported on Linux/macOS.
- Explicitly mention that all steps and tools (Azure Portal, CLI, REST API) are cross-platform.
- Provide example commands for both PowerShell and CLI side-by-side, or clarify platform applicability.
- Add a note on platform compatibility for each tool, especially in sections referencing PowerShell.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it is largely platform-neutral in its architectural and conceptual guidance, it repeatedly references PowerShell and Windows-centric tooling (e.g., MARS agent, DPM/MABS) as automation and management channels, and provides example procedures and videos using PowerShell before mentioning CLI. There is little to no explicit mention of Linux-specific backup agents, Linux command-line examples, or parity for Linux workloads. The documentation assumes familiarity with Windows tools and patterns, and does not provide Linux/macOS-specific guidance or examples, which may create friction for non-Windows users.
Recommendations
- Add explicit Linux/macOS examples for backup automation and management using Azure CLI and REST API, especially in sections referencing PowerShell.
- Mention Linux backup agents (such as Azure Backup Server for Linux, if available) and clarify support for Linux workloads.
- Provide parity in walkthroughs and videos, showing both PowerShell and CLI procedures side-by-side.
- Clarify any differences or limitations for Linux/macOS users in backup, restore, and monitoring scenarios.
- Include references to Linux filesystem backup scenarios and best practices.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page shows mild Windows bias by referencing PowerShell and CLI for resource moves, but only explicitly names PowerShell (a Windows-centric tool) and provides no direct Linux/macOS shell examples or parity in command-line instructions. The portal-based instructions are platform-agnostic, but the only command-line example mentioned is PowerShell, with CLI as a secondary reference. No Linux-specific tools, shell commands, or screenshots are provided.
Recommendations
- Provide explicit Bash/Azure CLI examples for all command-line operations, especially for moving resources (e.g., az resource move).
- List Azure CLI instructions before or alongside PowerShell, and clarify CLI works on Linux/macOS/Windows.
- Add notes or sections for Linux/macOS users where scripts or tools may differ, including troubleshooting tips.
- Include screenshots or terminal output from Linux/macOS environments where relevant.
Backup
Monitoring and reporting solutions for Azure Backup
...main/articles/backup/monitoring-and-alerts-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by consistently listing Azure PowerShell as the first non-portal client for monitoring and reporting, and referencing PowerShell examples before CLI or REST API. While Linux-compatible tools (Azure CLI, REST API) are mentioned, there are no explicit Linux/macOS-specific examples or guidance, and PowerShell is given prominence. No Windows-only tools or patterns are present, and all described solutions are cross-platform in principle.
Recommendations
- Alternate the order of tool mentions (e.g., list Azure CLI before PowerShell in some sections).
- Provide explicit CLI examples alongside PowerShell examples, especially in links and referenced documentation.
- Add notes or examples for Linux/macOS users where command syntax or environment setup may differ.
- Clarify that all non-portal clients (PowerShell, CLI, REST API) are supported on Linux/macOS and provide parity guidance.
Backup
Configure Multi-user authorization using Resource Guard
.../blob/main/articles/backup/multi-user-authorization.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides command-line examples for both Azure PowerShell and Azure CLI, but consistently lists PowerShell examples before CLI examples. This ordering, along with the explicit use of PowerShell cmdlets, may subtly signal a Windows-first approach. However, Azure CLI is cross-platform and all CLI examples are present, so Linux/macOS users can follow the instructions without issue. No Windows-only tools or patterns are mentioned, and there are no missing Linux/macOS equivalents.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit prioritization of Windows tools.
- Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Where possible, clarify that PowerShell examples are for Windows users and CLI examples are for all platforms.
- Consider adding a short note at the beginning of command sections explaining platform compatibility.
Backup
Quickstart - Configure vaulted backup for Azure Files using Azure CLI
...cles/backup/quick-backup-azure-files-vault-tier-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page is focused on Azure CLI, which is cross-platform, but there are subtle Windows biases. The example CLI output includes a Windows file path (C:\Users\testuser\Downloads\CLIForAFS\azure-cli>), suggesting Windows as the default environment. References to Azure PowerShell and portal alternatives are provided, but PowerShell is mentioned before Linux shell alternatives. There is no explicit Linux example, and the CLI command output is shown in a Windows context.
Recommendations
- Replace or supplement CLI example output with a Linux/macOS shell prompt (e.g., $ az backup protection enable-for-azurefileshare ...).
- Explicitly mention that Azure CLI works equally well on Linux, macOS, and Windows.
- Provide example commands and outputs for Bash or zsh environments.
- When listing alternatives (PowerShell, portal, REST), avoid listing Windows-centric tools first or exclusively.
- Add a note clarifying that the CLI commands are platform-agnostic and show usage in both Windows and Linux/macOS terminals.
Backup
Quickstart - Configure vaulted backup for Azure Files using Azure Terraform
...ackup/quick-backup-azure-files-vault-tier-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page mentions Azure PowerShell alongside Azure CLI for authentication and management tasks, and lists PowerShell before CLI in several places. However, the actual Terraform workflow and commands are platform-neutral, and no Windows-only tools or examples are given. There are no explicit Linux/macOS examples, but the instructions do not prevent Linux/macOS users from completing the task.
Recommendations
- Explicitly mention that all Terraform commands work on Linux/macOS as well as Windows.
- Provide example commands for both Azure CLI and Azure PowerShell, but clarify that Azure CLI is cross-platform and preferred for Terraform authentication.
- When listing management options (portal, PowerShell, CLI, REST), alternate the order or mention CLI first to avoid Windows-first bias.
- Add a note or section for Linux/macOS users confirming compatibility and any OS-specific considerations.
Backup
Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Server using a Terraform template
...p/quick-backup-postgresql-flexible-server-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Azure PowerShell and the Azure portal as clients for backup management before mentioning CLI and other cross-platform options. It also includes a note about Azure PowerShell authentication, which is only relevant to Windows users. However, the actual quickstart and all code samples are platform-neutral (Terraform), and the required authentication method is Azure CLI, which is cross-platform.
Recommendations
- List cross-platform tools (Azure CLI, Terraform) before Windows-specific tools (PowerShell, Azure portal) when enumerating options.
- Clarify that Azure CLI is available on Windows, Linux, and macOS, and provide links to installation instructions for all platforms.
- Remove or rephrase the PowerShell authentication note to emphasize cross-platform support and avoid implying PowerShell is required.
- Add explicit statements or links for Linux/macOS users where relevant, e.g., installation and usage guides.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides parity for both Windows and Linux virtual machines when describing how to attach/detach and swap disks after restore. However, in the section describing post-restore actions, instructions and links for Windows are presented before those for Linux, indicating a 'windows_first' ordering bias. No PowerShell-heavy, Windows-only, or missing Linux example biases are present; both platforms are covered with equivalent portal-based instructions.
Recommendations
- Present instructions for Windows and Linux in parallel or alternate the order to avoid implicit prioritization.
- Explicitly state that all steps apply equally to both Windows and Linux VMs unless otherwise noted.
- Consider grouping platform-specific instructions under clear subheadings for improved parity and discoverability.
Backup
Tutorial - Restore a VM with Azure CLI
...ocs/blob/main/articles/backup/tutorial-restore-disk.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is focused on Azure CLI usage, which is cross-platform, and most examples use CLI commands that work on Windows, Linux, and macOS. However, there is a notable Windows bias in the introductory section, where PowerShell is mentioned as an alternative and linked before the CLI tutorial, and a link to a Windows-specific VM zone documentation is used in the cross-zonal restore section. No Linux-specific examples, troubleshooting, or considerations are provided, and Windows terminology (e.g., referencing PowerShell, linking to Windows VM docs) appears before Linux equivalents.
Recommendations
- Add explicit Linux/macOS references and examples where relevant, such as shell syntax differences (e.g., date command for SAS token expiry).
- Provide a parallel link to Linux VM documentation in the cross-zonal restore section, not just Windows.
- Balance introductory references by mentioning both PowerShell and Bash/CLI alternatives equally, or lead with CLI as the cross-platform default.
- Include troubleshooting tips or notes for Linux/macOS users if any CLI commands behave differently or require different prerequisites.
- Clarify that all CLI commands are cross-platform and highlight any OS-specific caveats.
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 when attaching or swapping disks. However, the instructions for Windows VMs are consistently presented before those for Linux VMs, indicating a 'windows_first' bias. No PowerShell-heavy examples or exclusive mention of Windows tools are present, and Linux instructions are included, though always after Windows.
Recommendations
- Present instructions for Windows and Linux VMs in parallel or alternate the order to avoid implicit prioritization.
- Explicitly state that the process applies equally to both Windows and Linux VMs at the beginning of relevant sections.
- Where possible, provide combined or side-by-side examples for both platforms to reinforce parity.
- Review linked resources to ensure Linux documentation is as comprehensive and up-to-date as Windows documentation.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Azure portal, Azure PowerShell, and Azure CLI as alternative methods for restoring Azure Files, listing PowerShell (a Windows-centric tool) before CLI (cross-platform). However, all technical examples and REST API usage are platform-neutral, with no explicit PowerShell or Windows-only commands, nor any OS-specific tooling. There are no Linux-specific examples or references, but also no Windows-specific examples beyond the ordering in the introductory and summary sections.
Recommendations
- List Azure CLI before Azure PowerShell when mentioning alternative tools, as CLI is cross-platform and more accessible to Linux users.
- Explicitly mention that all REST API examples are platform-agnostic and can be executed from any OS, including Linux, macOS, and Windows.
- Provide example commands using curl or httpie (common Linux tools) to demonstrate REST API calls from Linux environments.
- Add a short section or note on authentication and environment setup for Linux users (e.g., using Azure CLI or environment variables for access tokens).
- Ensure parity in references to management tools by including links to Linux-specific guides or CLI usage where relevant.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists supported VM SKUs for Azure Backup policies, presenting Windows-based SKUs first and in much greater detail than Linux equivalents. The Windows section is extensive, specifying many versions and configurations, while Linux distributions are listed later and with less granularity. No examples, tools, or patterns specific to either platform are given, but the ordering and detail favor Windows.
Recommendations
- Present Windows and Linux SKUs in separate, equally prominent sections, or interleave them alphabetically to avoid implicit prioritization.
- Provide more detailed breakdowns for Linux SKUs, including specific versions, configurations, and notes on support parity.
- Add explicit statements about Linux support and limitations, similar to those given for Windows (e.g., smalldisk, core, containers).
- Include guidance or examples for both Windows and Linux VM backup scenarios, if applicable.
- Regularly review and update Linux support information to match the granularity and clarity provided for Windows.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page does not provide explicit Windows or Linux command-line examples, but it consistently lists Windows-centric tools (Azure portal, Azure PowerShell) before cross-platform options (Azure CLI) when mentioning alternative management methods. There are no examples or references to Linux-specific tools, shells, or workflows, and PowerShell is mentioned before CLI in all tool lists. No Linux-specific bias is present, but the ordering and tool emphasis suggest a subtle Windows-first bias.
Recommendations
- When listing alternative management tools, alternate the order or list Azure CLI before PowerShell to avoid implicit prioritization of Windows tools.
- Explicitly state that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Provide example REST API invocations using both PowerShell (for Windows users) and Bash/cURL (for Linux/macOS users) to demonstrate parity.
- Add a brief section or note for Linux/macOS users on how to authenticate and invoke REST API calls using native tools (e.g., curl, jq).
- Ensure that references to PowerShell are balanced with references to Bash or other Linux-native shells where appropriate.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides instructions for restoring Azure Managed Disks primarily through the Azure portal, with references to both Windows and Linux VM disk operations. However, in the section describing how to attach or swap restored disks, the instructions for Windows virtual machines are presented before those for Linux virtual machines. This ordering may subtly reinforce a Windows-first perspective, even though Linux instructions are present and linked.
Recommendations
- Alternate the order of Windows and Linux instructions in sections where both are relevant, or present them in parallel (e.g., side-by-side or in a tabbed format) to avoid implying priority.
- Explicitly state that the restore process and subsequent disk operations apply equally to both Windows and Linux VMs.
- Ensure that any referenced CLI, PowerShell, or REST API guides include Linux-specific examples and usage notes where applicable.
- Consider adding a summary table or section that highlights parity between Windows and Linux workflows for disk restore and attachment.
Backup
Create backup policies for Azure database for PostgreSQL - Flexible server using data protection REST API in Azure Backup
...base-postgresql-flex-use-rest-api-create-update-policy.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation page contains a reference to the 'default PowerShell object' for PostgreSQL Flexible servers, implying PowerShell as the primary or default automation tool. No equivalent mention is made of Linux-native tools, CLI, or scripting approaches. All examples are REST API and JSON-based, which are cross-platform, but the PowerShell reference introduces a subtle Windows bias.
Recommendations
- Replace or supplement the 'default PowerShell object' reference with cross-platform alternatives such as Azure CLI or Bash scripting.
- Explicitly mention that REST API operations can be performed from any OS, including Linux and macOS, using tools like curl or httpie.
- Provide example commands for Linux users (e.g., curl or Azure CLI) to demonstrate how to create backup policies via REST API.
- Avoid implying PowerShell as the default or only automation method unless parity is shown for other platforms.
Backup
Back up blobs in a storage account using Azure Data Protection REST API.
...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' section, and no Linux-specific examples or shell commands are provided. The documentation assumes familiarity with Windows-centric tools and patterns, potentially making it less accessible for Linux users.
Recommendations
- Explicitly mention Azure CLI as an option for assigning permissions alongside PowerShell and REST API, and provide example CLI commands.
- Include Linux shell (bash) examples for REST API calls using curl or similar tools.
- Ensure parity in example workflows by providing both PowerShell and CLI/bash examples where applicable.
- Reference Azure CLI documentation links in the prerequisites and related content sections.
- Avoid listing Windows tools (PowerShell) before cross-platform tools (CLI) unless there is a technical reason.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page lists supported VM SKUs for Azure Backup policies, presenting Windows-based SKUs first and in much greater detail than Linux equivalents. The Windows section is extensive, listing many variations and versions, while Linux distributions are grouped and listed with fewer details. There are no examples, tools, or patterns mentioned, but the ordering and level of detail show a clear Windows-first bias.
Recommendations
- Present Linux distributions before or alongside Windows SKUs, or group them together for parity.
- Provide more detailed breakdowns for Linux SKUs (e.g., list all supported versions and variants for each distribution, as done for Windows).
- Add clarifying notes about Linux support, including any limitations or special considerations, similar to what is provided for Windows.
- Ensure future updates maintain equal detail and visibility for both Windows and Linux platforms.