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 1051-1075 of 1604 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix-mabs-dpm.md ...main/articles/backup/backup-support-matrix-mabs-dpm.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, with all examples, supported operating systems, and deployment scenarios centered on Windows Server and related Microsoft technologies. There is no mention of Linux support, examples, or parity, and all tools and workflows assume a Windows-based infrastructure.
Recommendations
  • Explicitly state if Linux is unsupported, or clarify any Linux limitations, to avoid ambiguity.
  • If partial Linux support exists (e.g., for agent-based backup or file-level backup), document the scenarios, requirements, and limitations.
  • Provide equivalent Linux examples or workflows where possible, such as agent installation, backup, and restore procedures for Linux VMs.
  • Include a section or matrix row for Linux-based workloads, even if only to state 'not supported', to make the documentation more inclusive and clear.
  • Mention any future plans or alternatives for Linux users, such as integration with other Azure Backup solutions that support Linux.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-server-previous-versions.md ...cles/backup/offline-backup-server-previous-versions.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. All examples, tools, and workflows are described exclusively for Windows Server, Windows clients, DPM, and MABS, with no mention of Linux support or equivalent Linux tools. All command-line instructions use Windows executables, and registry edits and certificate management are described using Windows-specific utilities and paths. PowerShell is referenced for user identification, and all screenshots and UI flows are from Windows-based products. There is no guidance for Linux-based backup servers or cross-platform scenarios.
Recommendations
  • Explicitly state if Linux is unsupported for DPM/MABS offline backup workflows; if supported, provide equivalent Linux instructions and tools.
  • If possible, develop and document cross-platform utilities (e.g., for disk preparation and certificate management) that work on Linux.
  • Include Linux command-line examples (bash, shell scripts) and file paths where applicable.
  • Mention Linux backup server options and clarify their compatibility with Azure Import/Export.
  • Provide parity in screenshots and UI walkthroughs for any supported Linux-based management consoles.
  • Avoid assuming the user is on Windows by default; structure prerequisites and workflows to address both Windows and Linux environments where possible.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/pre-backup-post-backup-scripts.md ...main/articles/backup/pre-backup-post-backup-scripts.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows environments. All paths, examples, and terminology (such as drive letters, backslashes in paths, and references to Windows-specific applications like Exchange and SharePoint) are Windows-centric. There are no examples or guidance for Linux systems, and no mention of Linux shell scripting or file system conventions.
Recommendations
  • Add explicit guidance for configuring pre- and post-backup scripts on Linux systems, including example paths (e.g., /opt/scripts/myscript.sh) and file permissions.
  • Provide Linux shell script examples alongside Windows examples, and clarify any differences in script execution (e.g., bash vs. PowerShell/cmd).
  • Mention Linux data source naming conventions and provide examples relevant to Linux workloads (e.g., mount points, application data paths).
  • Clarify whether MABS supports Linux agents and, if so, document any differences in ScriptingConfig.xml location or usage.
  • Avoid assuming drive letters or Windows-only applications in examples; use more generic or cross-platform examples where possible.
GitHub 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
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it is mostly platform-agnostic in its main content (focused on Kusto queries and Azure portal usage), it lists PowerShell as the first automation client for ARG, and links to a PowerShell-specific tutorial before mentioning Azure CLI or SDKs. There are no explicit Linux shell or bash examples, and no mention of Linux-specific tools or workflows, which may make Linux users feel less prioritized.
Recommendations
  • List Azure CLI before PowerShell when mentioning automation clients, or present both together to avoid implying a Windows-first workflow.
  • Include explicit bash/Azure CLI examples for running ARG queries, especially for automation scenarios.
  • Provide links to both PowerShell and Azure CLI tutorials/documentation equally, ensuring Linux users have clear guidance.
  • Mention that ARG queries can be run from any platform using the Azure CLI, not just from PowerShell or the portal.
  • Consider adding a short section or note on cross-platform usage, highlighting Linux compatibility and any platform-specific considerations.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-azure-files-vault-tier-arm.md ...cles/backup/quick-backup-azure-files-vault-tier-arm.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell deployment examples and instructions, with no equivalent Azure CLI or Bash examples for Linux/macOS users. The 'Next steps' section also lists PowerShell-based management tasks before mentioning Azure CLI or REST API alternatives, reinforcing a Windows-first approach.
Recommendations
  • Add Azure CLI deployment instructions and examples alongside the PowerShell example, ensuring parity for Linux/macOS users.
  • Include Bash shell command examples for template deployment, or explicitly mention cross-platform options.
  • In the 'Next steps' section, alternate the order of PowerShell and CLI/REST API links, or group them together to avoid implying a preferred platform.
  • Explicitly state that all deployment methods (PowerShell, CLI, portal, REST API) are supported and provide links or code snippets for each.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-azure-files-vault-tier-bicep.md ...es/backup/quick-backup-azure-files-vault-tier-bicep.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell deployment instructions and examples, with no equivalent Azure CLI or Bash examples for Linux/macOS users. The prerequisites specifically mention installing the Azure PowerShell module, and the deployment workflow is described exclusively in terms of PowerShell commands. Azure CLI and Bash are only mentioned in passing in the 'Next steps' section, not in the main deployment flow.
Recommendations
  • Add Azure CLI and Bash examples for deploying the Bicep/ARM template, alongside the PowerShell example.
  • In the prerequisites, mention both Azure PowerShell and Azure CLI as options for users, with installation links for each.
  • Present deployment instructions for both Windows (PowerShell) and Linux/macOS (Bash/CLI), or use a tabbed interface to allow users to select their preferred environment.
  • Ensure that all steps, including tracking and restoring backups, have parity between PowerShell and CLI/Bash instructions.
  • Avoid assuming the use of PowerShell or Windows-specific workflows as the default; instead, provide cross-platform guidance.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/private-endpoints.md ...re-docs/blob/main/articles/backup/private-endpoints.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by providing only PowerShell and Windows-centric tooling (e.g., .ps1 scripts, Azure PowerShell, ARMClient with Windows file paths), with no equivalent CLI/bash/Linux examples. Instructions for scripting, automation, and role assignment are exclusively shown using PowerShell, and the use of Windows file path conventions (e.g., C:\<filepath>) further reinforces the bias. There is no mention of Azure CLI, Bash, or Linux-native workflows, and the examples and screenshots assume a Windows environment.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell examples, including role assignments, private endpoint creation, and DNS management.
  • Include bash script examples alongside .ps1 scripts, and use cross-platform file path conventions (e.g., /home/user/file.json) where appropriate.
  • Show how to upload and run scripts in the Azure Cloud Shell using both Bash and PowerShell environments.
  • Add explicit Linux/Unix workflow guidance for tasks such as managing DNS, running nslookup, and editing host files.
  • Ensure that screenshots and instructions reference both Windows and Linux environments where relevant.
  • Mention that all steps can be performed from Linux/macOS as well as Windows, and provide links to platform-agnostic tooling documentation.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-hana-database-instances-restore.md ...articles/backup/sap-hana-database-instances-restore.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by focusing on Azure Portal workflows and referencing PowerShell/CLI scripts for permissions, but does not provide explicit Linux command-line examples or mention Linux-native tools. The instructions and screenshots are oriented around GUI steps, which are more familiar to Windows users, and there is no mention of Linux-specific mounting, file system, or SAP HANA restore commands, despite SAP HANA on Azure VMs typically running on Linux.
Recommendations
  • Add explicit Linux command-line examples for mounting and restoring disks/snapshots, such as using 'lsblk', 'mount', or SAP HANA's native tools (e.g., hdbsql, hdbbackupdiag).
  • Provide sample Bash scripts or CLI commands for common restore tasks, not just PowerShell or generic 'CLI script' references.
  • Include Linux-specific guidance for disk attachment and permissions, such as using 'az' CLI commands and Linux file system operations.
  • Clarify when steps are OS-agnostic versus when they require Windows or Linux-specific actions.
  • Add screenshots or terminal output examples from Linux environments to balance the visual bias toward Windows GUIs.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/archive-tier-support.md ...docs/blob/main/articles/backup/archive-tier-support.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a subtle Windows bias. While it lists Azure portal, PowerShell, and CLI as supported clients, PowerShell (a Windows-centric tool) is mentioned before CLI (which is more cross-platform and commonly used on Linux). There are no explicit Linux-specific examples, nor is there mention of Linux tools or workflows. The documentation focuses on Azure Virtual Machines, SQL Server, and SAP HANA in Azure VMs, but does not clarify support or workflows for Linux VMs or Linux-native backup scenarios. Screenshots and instructions appear to assume a Windows-centric environment.
Recommendations
  • Explicitly include Linux VM backup scenarios and clarify parity with Windows VM support.
  • Provide CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Add Linux shell (bash) command examples where relevant, especially for common operations.
  • Clarify that the Azure CLI is cross-platform and provide guidance for Linux users.
  • Include screenshots or instructions that are relevant to Linux environments (e.g., terminal usage, Linux file paths).
  • If certain features are Windows-only, clearly state this and provide alternative guidance for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/automation-backup.md ...re-docs/blob/main/articles/backup/automation-backup.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by repeatedly highlighting PowerShell as a primary automation method and in example scenarios, often mentioning it before cross-platform tools like CLI or SDKs. There are no explicit Linux-specific examples, nor is Bash or Linux shell scripting referenced. The automation scenarios and sample workflows focus on PowerShell and Azure Automation Runbooks, which are traditionally more Windows-centric, with no parity examples for Linux users.
Recommendations
  • Include explicit Linux/Bash shell examples alongside PowerShell in automation scenarios.
  • When listing automation methods, alternate or randomize the order of PowerShell and CLI, or list CLI first to avoid implicit prioritization.
  • Provide sample scripts or workflows using Azure CLI and Bash for each scenario described (e.g., configuring backups, exporting data, automating responses).
  • Highlight cross-platform SDKs (Python, Go) with code snippets or links to Linux-focused guides.
  • Mention and link to Linux automation tools (e.g., cron jobs, systemd timers) where appropriate, especially in sections discussing scheduling and monitoring.
  • Ensure that all referenced videos and tutorials have Linux/CLI equivalents or supplementary materials.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-database-portal.md ...cles/backup/quick-backup-postgresql-database-portal.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell scripts as the primary or only example for granting privileges to database users. There are no explicit Linux or cross-platform command-line examples (such as Bash, psql, or Azure CLI), and PowerShell is mentioned before other tools. While there is a brief mention of using PG admin or PSQL as alternatives, no concrete examples or guidance are provided for these tools, leaving Linux and cross-platform users underserved.
Recommendations
  • Provide equivalent Linux/Bash/psql command examples alongside PowerShell scripts for tasks such as granting database privileges.
  • Explicitly mention and demonstrate how to use Azure CLI for relevant operations, as it is cross-platform.
  • When referencing scripts or tools, list cross-platform or Linux-native options first or in parallel with Windows/PowerShell.
  • Include screenshots or walkthroughs for PG admin and psql where PowerShell is referenced.
  • Add a section or callout for Linux/macOS users, summarizing the steps and tools they should use.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/about-azure-vm-restore.md ...cs/blob/main/articles/backup/about-azure-vm-restore.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits bias towards Windows environments. Restore instructions for encrypted VMs reference PowerShell and link exclusively to Windows-specific encryption documentation. There are no Linux-specific examples or references for restoring encrypted VMs or for item-level restore, and the documentation links for encryption are all Windows-focused. This may leave Linux users without clear guidance for equivalent operations.
Recommendations
  • Add Linux-specific examples and instructions for restoring encrypted VMs, including references to relevant Linux disk encryption documentation.
  • Include CLI or Bash-based restore workflows alongside or instead of PowerShell-centric instructions.
  • Ensure that links and guidance for disk encryption and restore cover both Windows and Linux VM scenarios equally.
  • Explicitly mention any differences or additional steps required for Linux VMs in each restore scenario, especially for item-level restore and encrypted VM restore.
  • Where PowerShell is mentioned, provide Azure CLI or Bash alternatives for parity.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/about-restore-microsoft-azure-recovery-services.md ...kup/about-restore-microsoft-azure-recovery-services.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily Windows-centric, focusing exclusively on Windows environments and tools. All examples and instructions reference Windows-specific utilities (e.g., robocopy, Windows Server Backup, PowerShell), with no mention of Linux equivalents or support. There are no Linux examples or cross-platform guidance provided, and the documentation implicitly assumes the reader is using Windows.
Recommendations
  • Explicitly state platform support at the beginning of the document. If MARS agent is Windows-only, clarify this to avoid confusion.
  • If Linux support is planned or available, provide equivalent Linux instructions, examples, and tool recommendations (e.g., using rsync instead of robocopy, bash scripts instead of PowerShell).
  • Where features are Windows-specific, clearly label them as such and provide alternative guidance or links for Linux users.
  • Include a comparison table or section outlining feature parity (or lack thereof) between Windows and Linux environments.
  • If MARS agent is not available for Linux, suggest alternative Azure backup solutions for Linux systems and link to relevant documentation.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/active-directory-backup-restore.md ...ain/articles/backup/active-directory-backup-restore.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, specifically Windows Server-based Active Directory. All examples, tools, and procedures are Windows-centric, with PowerShell scripts and references to Windows-specific utilities (e.g., ntdsutil.exe, DSRM). There are no Linux or cross-platform examples, nor is there mention of Samba or other non-Windows AD implementations. The documentation assumes the reader is operating in a Windows-only environment.
Recommendations
  • Add a section or note clarifying that the procedures are specific to Windows Server Active Directory, and mention whether or not they apply to Samba-based (Linux) domain controllers.
  • If Azure Backup or related tools support Samba AD or Linux-based domain controllers, provide equivalent backup and restore instructions/examples for those platforms.
  • Where PowerShell scripts are given, provide equivalent commands for Linux environments (e.g., using samba-tool for Samba AD).
  • Discuss any limitations or differences in backup/restore procedures for non-Windows domain controllers, if applicable.
  • Explicitly mention the lack of Linux support if it is intentional, to set expectations for cross-platform administrators.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-backup-glossary.md ...ocs/blob/main/articles/backup/azure-backup-glossary.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The Azure Backup glossary page demonstrates a Windows bias in several ways. Windows-specific technologies and tools (such as VSS, DPM, MABS, and MARS agent) are referenced without Linux equivalents or alternatives. In the 'Application consistent backup' entry, Windows VSS is mentioned first and in detail, while Linux is only referenced generically as 'pre or post scripts.' Several backup scenarios (bare metal, system state) are described in a way that is only applicable to Windows environments. Additionally, links and references to Windows tools (e.g., PowerShell, VSS documentation) are present, while Linux-native tools or workflows are not mentioned or are only briefly alluded to.
Recommendations
  • For each Windows-specific tool or technology (e.g., VSS, DPM, MABS, MARS agent), add equivalent Linux-focused explanations or explicitly state if there is no Linux equivalent.
  • In entries like 'Application consistent backup,' provide concrete Linux examples (e.g., using fsfreeze, LVM snapshots, or specific pre/post script patterns) and link to relevant Linux documentation.
  • Where PowerShell is referenced, ensure Azure CLI (which is cross-platform) is also mentioned with equal prominence.
  • For backup types like 'bare metal backup' and 'system state backup,' clarify their applicability to Windows and describe analogous Linux backup strategies (e.g., full disk imaging with dd, tar, or third-party tools).
  • Add references to Linux backup best practices and tools where relevant, and ensure that Linux administrators can find parity in documentation and guidance.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-restore.md ...les/backup/azure-kubernetes-service-cluster-restore.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell as an alternative method for restoring AKS clusters, but does not mention or provide examples for equivalent Linux-native or cross-platform CLI tools (such as Azure CLI or kubectl). The only explicit command-line method referenced is PowerShell, and there are no Linux-specific instructions or examples. This suggests a bias toward Windows/PowerShell environments and leaves out users who work primarily on Linux or macOS.
Recommendations
  • Include Azure CLI examples for restoring AKS clusters, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Mention and provide instructions for using kubectl (where applicable) for restore operations, especially for item-level or namespace restores.
  • When referencing PowerShell, always provide a parallel example using Azure CLI or bash scripts.
  • Explicitly state that the restore process can be performed from any OS, and clarify any OS-specific requirements or limitations.
  • Review linked articles (such as the PowerShell restore guide) to ensure Linux parity and cross-platform guidance.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-flexible-server-arm.md .../backup/quick-backup-postgresql-flexible-server-arm.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias by providing only PowerShell deployment instructions, referencing the Azure PowerShell module as a prerequisite, and omitting equivalent Azure CLI or Bash examples that would be more familiar to Linux users. The 'Next steps' section also directs users to a PowerShell-based restore guide, further reinforcing the Windows-centric approach. There is no mention of Linux tools, shells, or cross-platform alternatives.
Recommendations
  • Add Azure CLI and/or Bash examples for deploying the ARM template, as these are cross-platform and widely used on Linux and macOS.
  • List both Azure PowerShell and Azure CLI as prerequisites, with installation instructions for each.
  • In the deployment section, provide parallel instructions/scripts for PowerShell and Azure CLI, making it clear that either can be used.
  • Update the 'Next steps' section to include links to both PowerShell and Azure CLI restore guides.
  • Explicitly mention that the process is cross-platform and can be performed from Windows, Linux, or macOS environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-flexible-server-cli.md .../backup/quick-backup-postgresql-flexible-server-cli.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page, while focused on Azure CLI (which is cross-platform), demonstrates Windows bias in several ways. It references PowerShell objects and patterns before explaining CLI equivalents, uses Windows-style file paths (e.g., '.\OSSPolicy.json'), and does not provide Linux/macOS-specific examples or notes on differences (such as file path conventions or shell syntax). The guidance assumes a Windows environment for file manipulation and scripting, potentially confusing Linux users.
Recommendations
  • Provide both Windows (PowerShell/CMD) and Linux/macOS (Bash) command examples, especially for file paths and redirection.
  • Replace or supplement Windows-style file paths (e.g., '.\OSSPolicy.json') with POSIX-style paths (e.g., './OSSPolicy.json') in CLI examples.
  • Add notes or callouts explaining differences in file handling and command syntax between Windows and Linux/macOS shells.
  • Avoid referencing PowerShell objects or behaviors unless specifically relevant, and clarify when instructions are Windows-specific.
  • Explicitly state that Azure CLI is cross-platform and provide parity in examples and troubleshooting for all supported OSes.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-backup-concept.md ...kup/azure-kubernetes-service-cluster-backup-concept.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While the main content is platform-neutral and focuses on Azure concepts, the 'Next steps' section lists Azure PowerShell (a Windows-centric tool) before or alongside Azure CLI (which is cross-platform) for backup and restore operations. There are no explicit Linux shell or bash examples, and PowerShell is mentioned as a primary automation tool, which may implicitly prioritize Windows users. No Linux-specific tools, commands, or examples are provided.
Recommendations
  • Ensure that Azure CLI (which is cross-platform) is listed before or alongside Azure PowerShell in all 'Next steps' and example sections.
  • Provide explicit bash or shell command examples for common operations, especially for installation and management tasks.
  • Where PowerShell is mentioned, clarify that Azure CLI is available and supported on Linux/macOS/Windows, and provide links to CLI documentation.
  • Add a section or callout noting that all operations can be performed from Linux/macOS environments using Azure CLI.
  • If possible, include screenshots or walkthroughs from non-Windows environments (e.g., Azure Cloud Shell, Linux terminal) to reinforce cross-platform support.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-backup.md ...cles/backup/azure-kubernetes-service-cluster-backup.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell as the only command-line automation example, both in the introduction and in the 'Next steps' section, without mentioning or providing any Azure CLI (cross-platform) or Bash/Linux-native alternatives. All command-line automation is directed to PowerShell, and there are no Linux-specific or cross-platform shell examples. The documentation assumes use of the Azure Portal or PowerShell, omitting Linux-first workflows.
Recommendations
  • Add Azure CLI examples alongside or before PowerShell examples for all automation steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • In 'Next steps', include links to Azure CLI-based backup and restore guides, or provide equivalent Bash scripts.
  • When referencing command-line options, mention both PowerShell and CLI, or provide a table with both sets of commands.
  • Explicitly state that all features are available via Azure CLI and provide links or inline examples.
  • If screenshots are shown, ensure they are not Windows-specific (e.g., avoid showing only Windows file paths or PowerShell terminals).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-backup-support-matrix.md ...azure-kubernetes-service-cluster-backup-support-matrix.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias, primarily by listing Azure PowerShell as a first-class method for backup and restore operations alongside Azure CLI and the Azure portal. Azure PowerShell is a Windows-centric tool, and its inclusion (and placement before ARM/Bicep/Terraform) suggests a preference for Windows tooling. However, the documentation does not provide command-line examples, and the main technical requirements and supported scenarios focus on Linux-based node pools, which is positive for Linux parity. Still, the 'Next steps' section lists Azure PowerShell before ARM/Bicep/Terraform, and the page references Azure CLI and PowerShell as the main automation tools, which may reinforce a Windows-first perception.
Recommendations
  • Ensure that all example commands and automation instructions are provided for both Azure CLI and Azure PowerShell, with CLI (cross-platform) examples listed first.
  • Explicitly state that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Where possible, provide Bash shell examples for scripting and automation, not just PowerShell.
  • In the 'Next steps' section, list Azure CLI before Azure PowerShell, and consider grouping cross-platform tools (CLI, ARM, Bicep, Terraform) before Windows-centric tools.
  • Clarify that PowerShell is available cross-platform, but that Azure CLI is the primary tool for Linux users.
  • If referencing PowerShell, provide equivalent Bash/CLI examples or links for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/back-up-azure-stack-hyperconverged-infrastructure-virtual-machines.md ...e-stack-hyperconverged-infrastructure-virtual-machines.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All command-line examples use PowerShell or Windows-specific tools (e.g., PowerShell cmdlets, .exe installers). The workflow assumes a Windows environment (e.g., references to Hyper-V, Windows Server, and NTLM authentication). Linux support is only briefly mentioned, with no concrete examples or detailed guidance for Linux VMs. There are no Linux shell commands, nor are Linux-specific backup or recovery scenarios illustrated.
Recommendations
  • Provide parallel Linux command-line examples (e.g., bash commands for agent installation, configuration, and firewall management).
  • Include explicit instructions and screenshots for backing up and recovering Linux VMs, covering both host-level and guest-level scenarios.
  • Clarify any differences in backup and recovery workflows for Linux VMs, including limitations and best practices.
  • Mention Linux tools/utilities (e.g., systemctl, firewall-cmd/ufw) where relevant, alongside Windows tools.
  • Ensure that Linux prerequisites and supported scenarios are as detailed as those for Windows, and are not relegated to a single line or table row.
  • Consider reordering sections or examples so that Linux is not always mentioned last or as an afterthought.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/back-up-file-data.md ...re-docs/blob/main/articles/backup/back-up-file-data.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented towards Windows environments. All instructions, terminology, and referenced features (such as Volume Shadow Copy Service, deduplication, and file/folder selection) are specific to Windows. There are no examples, notes, or guidance for Linux systems, nor is there any mention of Linux-specific backup considerations or tools. The documentation assumes the use of the MABS console, which is a Windows application, and references Windows-only features (e.g., VSS, Data Deduplication, file properties dialog).
Recommendations
  • Add explicit notes clarifying whether MABS supports Linux clients, and if so, provide equivalent instructions or limitations for Linux systems.
  • Include Linux-specific examples or workflows, such as how to install the protection agent on Linux, how to select files/folders for backup, and how to perform recovery operations.
  • Mention Linux backup/recovery limitations (e.g., lack of VSS, differences in file system support, etc.) where relevant.
  • If Linux is not supported, state this clearly at the beginning of the documentation to set expectations.
  • Where Windows-specific features are referenced (e.g., Data Deduplication, VSS, file properties), provide Linux alternatives or note their absence.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/back-up-hyper-v-virtual-machines-mabs.md ...ticles/backup/back-up-hyper-v-virtual-machines-mabs.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows environments, specifically Hyper-V on Windows Server, and Microsoft Azure Backup Server (MABS), which itself is a Windows-based product. Windows terminology, tools, and workflows are exclusively described, with Linux only briefly mentioned as a supported guest OS for file-consistent snapshots. There are no Linux command-line examples, no mention of Linux-based backup agents or recovery workflows, and all recovery and backup procedures are described using Windows GUI tools or Windows-specific features (e.g., VSS, SCSI controller requirements, registry edits).
Recommendations
  • Provide explicit Linux guest backup and recovery examples, including command-line steps for Linux VMs.
  • Clarify the limitations and capabilities for Linux VMs (e.g., application-consistent vs. file-consistent backups, supported distributions, agent installation).
  • Include parity in recovery workflows for Linux VMs, such as how to restore files from a Linux guest, and whether item-level recovery is possible.
  • Mention or link to equivalent Linux backup tools or patterns where appropriate, or clarify if none exist.
  • If MABS does not support certain Linux scenarios, state this clearly and suggest alternative approaches or products for Linux environments.
  • Balance the documentation structure so that Linux prerequisites and workflows are not relegated to a single line or section, but are integrated throughout.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-flexible-server-bicep.md ...ackup/quick-backup-postgresql-flexible-server-bicep.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing deployment instructions and code samples using Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The instructions reference Windows-specific behaviors (e.g., right-click to paste in the shell window), and there are no Linux/macOS-specific guidance or cross-platform notes. The 'Next steps' section also links only to PowerShell-based restore instructions.
Recommendations
  • Provide equivalent Azure CLI (az) examples for deploying the Bicep template, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash shell instructions and note any differences in command usage or environment setup for Linux/macOS users.
  • Avoid Windows-specific instructions such as 'right-click to paste' or clarify how to paste in terminals on different operating systems.
  • In the prerequisites, mention both Azure PowerShell and Azure CLI as supported tools for deploying Bicep files, and link to installation guides for both.
  • In the 'Next steps' section, add links to restore instructions using Azure CLI or portal, not just PowerShell.
  • Consider a 'Platform differences' note or table summarizing how to perform each step on Windows, Linux, and macOS.
GitHub Create Pull Request
← Previous Page 43 of 65 Next →