Backup

755
Total Pages
562
Linux-Friendly Pages
193
Pages with Bias
25.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

520 issues found
Showing 201-225 of 520 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-afs-backup.md ...re-docs/blob/main/articles/backup/manage-afs-backup.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation primarily focuses on managing Azure Files backups using the Azure Portal, with only a brief mention of Azure PowerShell, Azure CLI, and REST API as alternative management methods. The PowerShell link is listed before CLI, and there are no direct examples or instructions for Linux users or Linux-specific tools. All screenshots and step-by-step instructions are portal-based, which is platform-agnostic, but the lack of parity in command-line examples (especially for Linux/CLI) and the ordering of PowerShell before CLI suggest a subtle Windows bias.
Recommendations
  • Provide explicit Azure CLI examples alongside or immediately after PowerShell examples, especially for common tasks such as creating, modifying, or deleting backup policies.
  • Ensure that Azure CLI and REST API links are given equal prominence to PowerShell, and consider listing CLI before PowerShell to avoid Windows-first ordering.
  • Include at least one end-to-end Linux/CLI workflow for managing Azure Files backups, with sample commands and expected outputs.
  • Add a section or callout for Linux users, highlighting any platform-specific considerations or best practices.
  • Review and update cross-references to ensure that Linux and CLI documentation is as comprehensive and discoverable as Windows/PowerShell content.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-bicep-file.md ...lob/main/articles/backup/quick-backup-vm-bicep-file.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All deployment and cleanup examples use Azure PowerShell scripts exclusively, with no mention of Azure CLI or Bash equivalents. The Bicep template provisions only Windows VMs, and the instructions reference Windows-specific tools and patterns (e.g., PowerShell, Remove-AzResourceGroup). There are no Linux VM options or Linux command-line examples provided.
Recommendations
  • Add Azure CLI and/or Bash examples for deploying and cleaning up resources, alongside PowerShell.
  • Include a Linux VM option in the Bicep template (e.g., allow selection of a Linux image and admin SSH key).
  • Ensure that references to tools and commands are cross-platform, or provide parallel instructions for Linux/macOS users.
  • Update the documentation to mention both Windows and Linux scenarios where applicable, and avoid assuming a Windows-only environment.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows VM creation first, providing more detailed and step-by-step instructions for Windows VM agent installation (including a direct download link and file verification steps), and mentioning Windows-specific tools and paths. Linux instructions are less detailed, lack explicit command-line examples, and are presented after the Windows instructions. There are no Linux-specific screenshots or examples, and the initial VM creation link points to a Windows-specific guide.
Recommendations
  • Provide parallel Linux examples and links (e.g., link to both Windows and Linux VM creation guides).
  • Include explicit Linux command-line examples for agent installation (e.g., apt, yum, or zypper commands).
  • Add Linux-specific screenshots or UI references where applicable.
  • Present Windows and Linux instructions with equal detail and in parallel sections, rather than Windows first.
  • Avoid referencing Windows-specific tools or file paths without Linux equivalents.
  • Ensure all optional and troubleshooting steps are covered for both platforms.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-backup-vault.md ...-docs/blob/main/articles/backup/manage-backup-vault.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing PowerShell before CLI when discussing scripting and automation, and by not providing any Linux-specific examples or guidance. All command-line references are generic or PowerShell-centric, with no mention of Linux shell usage, nor any screenshots or instructions tailored for Linux users. The page assumes the Azure portal as the main interface, which is cross-platform, but scripting examples and tool mentions favor Windows environments.
Recommendations
  • Provide explicit examples for both Azure CLI (bash/shell) and PowerShell when mentioning scripting or automation, and ensure CLI examples are given equal prominence.
  • Include notes or sections on how Linux users can perform equivalent operations, especially for tasks like moving resources, managing vaults, and troubleshooting.
  • Add screenshots or command snippets that show usage from Linux terminals (e.g., bash) where relevant.
  • When referencing tools and scripts, clarify compatibility and provide sample scripts for both Windows (PowerShell) and Linux (bash/CLI).
  • Review all command references to ensure they are not Windows-centric and update documentation to reflect cross-platform parity.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation focuses exclusively on managing and monitoring SQL Server databases on Azure VMs, implicitly assuming Windows as the underlying OS. There are no examples, instructions, or notes for SQL Server on Linux VMs, nor any mention of Linux-specific tools or scenarios. All references to SQL Server management, backup, and recovery are Windows-centric, and the use of the Azure portal is described with screenshots and steps that are only applicable to Windows-based SQL Server deployments.
Recommendations
  • Explicitly state whether the instructions apply to both Windows and Linux-based SQL Server VMs, or clarify if only Windows is supported.
  • Add sections or notes describing how to manage and monitor SQL Server on Linux VMs, including any differences in backup agent installation, extension registration, or portal experience.
  • Provide Linux-specific examples, such as using Bash, Linux file paths, or relevant Linux tools for troubleshooting and management.
  • If certain features are not supported on Linux, clearly document these limitations.
  • Include links to documentation for SQL Server on Linux in Azure VMs, if available.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/monitoring-and-alerts-overview.md ...main/articles/backup/monitoring-and-alerts-overview.md
High Priority View Details →
Scanned: 2025-12-29 18:00
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 consistently mentioning PowerShell as a primary non-portal client and listing it before the Azure CLI. There are no explicit Linux-specific examples or references to Linux shells or tools. While Azure CLI is mentioned, it is always after PowerShell, and no sample commands or workflows are provided for Linux users. The documentation does not address Linux-specific monitoring or reporting scenarios, nor does it provide parity in examples or guidance for Linux administrators.
Recommendations
  • Provide explicit Linux/Unix shell examples (e.g., Bash) alongside or before PowerShell examples.
  • Ensure Azure CLI examples are given equal prominence and detail as PowerShell, including sample commands for common tasks.
  • Mention cross-platform compatibility and highlight any differences or considerations for Linux users.
  • Include references to Linux-native tools or workflows where appropriate (e.g., integration with syslog, cron jobs, or Linux-based automation).
  • Review the ordering of tool mentions to avoid always listing Windows tools first.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-azure-data-box-dpm-mabs.md ...icles/backup/offline-backup-azure-data-box-dpm-mabs.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All instructions, examples, and supported platforms are exclusively for Windows Server (2016/2019) and Windows-based tools (DPM, MABS). The setup and troubleshooting sections rely on Windows-specific tools (e.g., PSExec, regedit, Windows command prompt, PowerShell modules), and there are no Linux equivalents or mentions of cross-platform alternatives. No Linux distributions or commands are referenced, and the workflow assumes a Windows administrative environment throughout.
Recommendations
  • Clearly state early in the documentation that only Windows platforms are supported, if that is a product limitation. If not, add explicit support information for Linux and other platforms.
  • If DPM/MABS or the MARS agent can be used on Linux, provide equivalent Linux instructions, including commands for mounting NFS shares, managing certificates, and interacting with Azure (e.g., using Azure CLI instead of PowerShell).
  • Where PowerShell is used, provide Azure CLI equivalents for cross-platform compatibility.
  • Replace or supplement Windows-only tools (e.g., PSExec, regedit) with cross-platform alternatives or document how to perform equivalent tasks on Linux.
  • If Linux is not supported, add a note in the 'Supported platforms' section to clarify this and, if possible, link to alternative solutions for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-azure-data-box.md .../main/articles/backup/offline-backup-azure-data-box.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows environments. All supported platforms listed are Windows SKUs, with no mention of Linux or macOS support. All examples, prerequisites, and troubleshooting steps use Windows-specific tools (PowerShell, MARS Agent, Windows command prompt, PsExec, Windows Registry, Control Panel). There are no Linux equivalents or instructions, and the documentation does not clarify whether Linux is unsupported or simply omitted.
Recommendations
  • Explicitly state platform support at the beginning of the document. If Linux is not supported, clarify this to avoid confusion.
  • If Linux support exists or is planned, provide equivalent instructions for Linux environments, including commands for Bash, Linux-compatible tools, and Linux-specific troubleshooting.
  • Where possible, use cross-platform Azure CLI examples in addition to or instead of PowerShell.
  • Mention Linux tools and patterns (e.g., mounting NFS shares, managing certificates, uninstalling packages) alongside Windows tools.
  • Add a section addressing common questions about non-Windows support and alternatives.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/move-to-azure-monitor-alerts.md ...b/main/articles/backup/move-to-azure-monitor-alerts.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation references PowerShell and the Azure portal as primary management interfaces, with no mention of Linux-specific tools or CLI usage. It assumes familiarity with PowerShell and Windows-centric workflows, and does not provide Linux or cross-platform command-line examples. Notification configuration is stated as only available via the Azure portal, and there is no discussion of Linux automation or scripting options.
Recommendations
  • Add Azure CLI examples for common alert management and backup operations, as the CLI is cross-platform and widely used on Linux.
  • Explicitly mention Linux support and provide guidance for Linux administrators, including how to monitor or manage alerts using Bash scripts or automation tools.
  • Clarify if PowerShell Core (cross-platform) is supported, and provide examples using it if so.
  • Where possible, avoid language that assumes a Windows environment (e.g., 'portal/PowerShell/the CLI clients') and ensure parity in examples and instructions for both Windows and Linux users.
  • If certain features are only available via the Azure portal, note any workarounds or alternative monitoring/notification integrations that Linux users might employ.
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-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows file paths, tools, and conventions (e.g., 'Drive:', 'cscript', and backslash paths). There are no examples or instructions for Linux systems, and all scripting and configuration guidance assumes a Windows environment.
Recommendations
  • Add explicit guidance and examples for configuring pre-backup and post-backup scripts on Linux-based protected computers, if supported.
  • Include Linux path formats (e.g., /opt/dpm/Scripting) and script execution methods (e.g., bash, sh) alongside Windows examples.
  • Mention Linux-compatible scripting languages and tools (e.g., Bash, Python) and how to invoke them.
  • Clarify whether MABS supports Linux agents for scripting, and if not, state this limitation clearly.
  • Ensure that all XML configuration examples show both Windows and Linux path and script invocation formats where applicable.
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-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as the first automation client for Azure Resource Graph, referencing a PowerShell-specific quickstart before the Azure CLI or SDK equivalents. There are no explicit Linux shell (bash) or cross-platform CLI examples, and the only automation tools mentioned are PowerShell, Azure CLI, and Python SDK, with PowerShell given prominence. No Linux-specific guidance or parity is provided.
Recommendations
  • List Azure CLI examples and documentation links before or alongside PowerShell to avoid Windows-first ordering.
  • Provide explicit bash/Azure CLI sample commands for running ARG queries, especially for Linux users.
  • Mention cross-platform tools (e.g., Azure CLI, Python SDK) before or equally with PowerShell.
  • Clarify that all automation clients (PowerShell, CLI, SDK) are cross-platform, and provide links to Linux installation guides.
  • Consider adding a section or note for Linux/macOS users, highlighting any differences or tips for their environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/private-endpoint-configure-vault-backup-server.md ...ckup/private-endpoint-configure-vault-backup-server.md
High Priority View Details →
Scanned: 2025-12-29 18:00
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, specifically Microsoft Azure Backup Server (MABS) and the MARS agent, which are Windows-only tools. All examples, screenshots, and instructions assume use of the Azure Portal GUI or Windows-based DNS management. There are no references to Linux equivalents, CLI commands, or cross-platform backup agents. The only DNS host file example links to a Windows-based DNS guide, and there are no PowerShell or CLI scripts, but the overall workflow is Windows-centric.
Recommendations
  • Add explicit notes clarifying that MABS and MARS agent are Windows-only, and suggest Linux-compatible alternatives (e.g., Azure CLI, AzCopy, or third-party backup solutions) where possible.
  • Provide parallel instructions or references for configuring private endpoints and DNS using Azure CLI, which is cross-platform.
  • Include Linux-based DNS configuration examples (e.g., editing /etc/hosts, using BIND for DNS forwarding) alongside or after Windows examples.
  • If possible, add guidance for backing up Linux servers to Azure using supported tools, and how private endpoints would be configured in those scenarios.
  • Link to documentation for Linux backup solutions and their integration with Azure Backup, if supported.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-azure-files-vault-tier-cli.md ...cles/backup/quick-backup-azure-files-vault-tier-cli.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page, while focused on Azure CLI (which is cross-platform), shows evidence of Windows bias. It includes a command output with a Windows file path (C:\Users\testuser\Downloads\...), references PowerShell and the Azure portal before mentioning Linux or macOS alternatives, and does not provide explicit Linux shell output or examples. The prerequisites section mentions Docker for macOS/Windows but does not clarify native Linux installation. There are no explicit Linux shell examples or screenshots, and the only command output shown is from a Windows environment.
Recommendations
  • Provide example command outputs from both Linux and Windows environments, or use a neutral shell prompt (e.g., $ or #) instead of a Windows path.
  • Explicitly mention native Linux installation steps for Azure CLI, not just Docker for macOS/Windows.
  • Include Linux-specific notes or troubleshooting tips where relevant.
  • When referencing alternative tools (PowerShell, Azure portal), list them in an order that does not prioritize Windows tools (e.g., 'Azure CLI, Azure PowerShell, or Azure portal').
  • Add screenshots or terminal snippets from Linux environments to demonstrate parity.
  • Clarify that all CLI commands work identically on Linux, macOS, and Windows, and provide links to Linux-specific documentation where appropriate.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-azure-files-vault-tier-terraform.md ...ackup/quick-backup-azure-files-vault-tier-terraform.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows-first bias by mentioning Azure PowerShell alongside Azure CLI for authentication, despite Terraform only supporting Azure CLI. PowerShell is referenced multiple times (including in 'Next steps') before or alongside Azure CLI, and there are no explicit Linux/macOS-specific instructions or examples. The documentation assumes familiarity with Windows tools and patterns, such as PowerShell, without providing parity for Linux users.
Recommendations
  • Clearly state that Azure CLI is cross-platform and preferred for Terraform authentication, and de-emphasize PowerShell in this context.
  • Provide explicit Linux/macOS command-line examples (e.g., bash/zsh) where relevant, especially for directory and file operations.
  • In 'Next steps', list Azure CLI and REST API options before PowerShell to avoid Windows-first ordering.
  • Add a note or section for Linux/macOS users, clarifying that all Terraform and Azure CLI commands work natively on those platforms.
  • Remove or clarify any PowerShell references that are not directly relevant to Terraform workflows.
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-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a bias towards Windows environments by primarily referencing PowerShell scripts for privilege assignment and automation, with only brief and secondary mentions of Linux-native tools (e.g., psql, pgAdmin). PowerShell is presented as the default or primary method, and alternatives are not equally detailed. There is also a lack of explicit Linux shell or cross-platform CLI examples, and no Bash or Linux command-line instructions are provided.
Recommendations
  • Provide equivalent examples using Linux-native tools such as psql and Bash scripts for privilege assignment and automation, alongside PowerShell.
  • Ensure that instructions for both PowerShell and Linux/Unix environments are presented with equal prominence and detail.
  • Where PowerShell scripts are referenced, include downloadable or copy-paste-ready Bash/psql equivalents.
  • Explicitly mention cross-platform compatibility and clarify which steps or scripts are platform-agnostic.
  • Add screenshots or walkthroughs using Azure CLI and psql on Linux, not just Azure Portal or PowerShell.
  • Review and update all sections to ensure Linux users are not required to adapt Windows-centric instructions themselves.
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-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All deployment and restore examples use PowerShell, with no Azure CLI, Bash, or Linux-native instructions provided. The prerequisites and next steps reference PowerShell tools and modules exclusively, and there is no mention of Linux or cross-platform alternatives. This may hinder accessibility for Linux or macOS users.
Recommendations
  • Add Azure CLI examples for deploying the ARM template, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Provide Bash shell script examples alongside PowerShell scripts.
  • In prerequisites, mention both Azure PowerShell and Azure CLI, with installation links for each.
  • In 'Next steps', include links to restoring using Azure CLI or portal, not just PowerShell.
  • Explicitly state that the instructions are cross-platform, or clarify platform-specific steps where necessary.
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-12-29 18:00
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 and referencing the Azure PowerShell module as a prerequisite. There are no examples or instructions for deploying the Bicep template using cross-platform tools such as Azure CLI, nor are there any Linux/macOS-specific notes or parity. The guidance for restoring backups also links only to a PowerShell-based article.
Recommendations
  • Add Azure CLI deployment instructions for the Bicep template, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • List both PowerShell and CLI as options in the prerequisites, and provide installation links for both.
  • Update the deployment section to include both PowerShell and CLI examples, or at least mention that the CLI can be used with a reference link.
  • Ensure that any 'Next steps' or further reading links include CLI-based or portal-based alternatives, not just PowerShell.
  • Wherever possible, avoid language that assumes a Windows shell (e.g., 'right-click the shell window'), or provide equivalent instructions for other platforms.
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-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page, while focused on Azure CLI (which is cross-platform), exhibits Windows bias in several ways. It references PowerShell and Windows object manipulation patterns first and in detail, and uses Windows-style file paths (e.g., '.\OSSPolicy.json') in CLI examples. The explanation of modifying policy templates emphasizes PowerShell object usage before discussing the CLI/file-based approach, and does not provide explicit Linux/Unix shell equivalents or path examples. There are no Linux-specific examples or notes about running the CLI commands on Linux or macOS.
Recommendations
  • Provide Linux/Unix shell command examples alongside or instead of Windows-style examples, especially for file paths (e.g., use './OSSPolicy.json' instead of '.\OSSPolicy.json').
  • When discussing object manipulation, avoid assuming PowerShell as the default and clarify that Linux/macOS users should use file-based approaches.
  • Explicitly mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, and provide notes or tips for users on different platforms.
  • If referencing PowerShell, also reference Bash or other common Linux shells where appropriate, or provide links to equivalent guidance.
  • Consider reordering explanations to avoid presenting Windows/PowerShell approaches first, or clearly separate platform-specific guidance.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-template.md .../blob/main/articles/backup/quick-backup-vm-template.md
High Priority View Details →
Scanned: 2025-12-29 18:00
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. All deployment and cleanup examples use Azure PowerShell scripts, with no Azure CLI (bash) or Linux shell equivalents provided. The template referenced is for a Windows VM, and the PowerShell approach is presented first and in detail, while Azure CLI and REST API are only mentioned in passing. There are no Linux-specific instructions or examples, and Windows tools and patterns are used exclusively throughout the page.
Recommendations
  • Add equivalent Azure CLI (bash) examples for deploying the ARM template, including parameter input and resource group creation.
  • Provide cleanup instructions using Azure CLI commands, not just PowerShell.
  • Reference and/or provide a template for deploying a Linux VM with backup, or clarify how to adapt the template for Linux.
  • When listing deployment options, mention Azure CLI and the portal before or alongside PowerShell, not after.
  • Link directly to Linux/CLI quickstart guides where available.
  • Ensure that monitoring and backup job instructions include both PowerShell and CLI options.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-terraform.md ...blob/main/articles/backup/quick-backup-vm-terraform.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively demonstrates backing up a Windows virtual machine in Azure using Terraform, with no mention or example of Linux VM equivalents. The description, checklist, and verification steps all focus on Windows VMs, and the 'Next steps' section directs users to further Windows VM resources. There is no parity for Linux VM scenarios, nor any guidance for Linux-specific backup considerations.
Recommendations
  • Add parallel examples and instructions for backing up Linux virtual machines in Azure using Terraform.
  • Update the checklist and verification steps to include Linux VM resource names and backup commands.
  • Provide guidance on differences in backup configuration or recovery for Linux VMs, such as OS disk types, authentication, or agent requirements.
  • Balance 'Next steps' links to include articles about Azure Linux VMs and their backup procedures.
  • Consider renaming the article or clearly indicating its Windows-specific scope if Linux parity is not intended.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-blob-vaulted-backup-cli.md .../main/articles/backup/quick-blob-vaulted-backup-cli.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing PowerShell and linking to PowerShell-based instructions before or alongside CLI examples. The 'create a Backup vault' link points to a PowerShell guide, and the restore section lists Azure PowerShell before Azure CLI and REST API. There are no explicit Linux-specific instructions or examples, and the documentation does not mention Linux tools or shell environments.
Recommendations
  • Provide explicit Bash/Linux shell examples alongside or before PowerShell examples.
  • Ensure links for key tasks (e.g., creating a Backup vault) include both Azure CLI and PowerShell options, with CLI (cross-platform) listed first.
  • Add notes clarifying that Azure CLI commands work on Linux, macOS, and Windows.
  • Avoid referencing PowerShell-specific guides in CLI-focused documentation unless parity is maintained.
  • Include troubleshooting or environment setup instructions for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-kubernetes-backup-bicep.md .../main/articles/backup/quick-kubernetes-backup-bicep.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a clear Windows bias by exclusively providing deployment instructions using Azure PowerShell, referencing Windows-specific interaction patterns (e.g., right-click to paste in shell), and omitting equivalent Azure CLI or Bash examples. The prerequisites and deployment steps focus on PowerShell, with no mention of Linux-native tools or workflows, despite Bicep and Azure CLI being cross-platform.
Recommendations
  • Add Azure CLI and Bash examples for deploying the Bicep template, ensuring Linux and macOS users are equally supported.
  • Update instructions to use platform-neutral language for shell interactions (e.g., 'paste the code into your terminal'), or provide platform-specific notes.
  • Mention both Azure PowerShell and Azure CLI as options in the prerequisites and deployment sections.
  • Order examples so that cross-platform tools (Azure CLI, Bash) are presented before or alongside PowerShell.
  • Explicitly state that all steps can be performed on Linux, macOS, or Windows, and link to relevant cross-platform installation guides.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/register-public-access-vault-backup-server.md ...s/backup/register-public-access-vault-backup-server.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes the process for Microsoft Azure Backup Server (MABS), which is a Windows-only product. All instructions, UI references, and screenshots are specific to the Windows environment, with no mention of Linux equivalents or cross-platform alternatives. There are no Linux commands, tools, or workflows provided, and the documentation assumes the user is operating in a Windows GUI context.
Recommendations
  • If Linux support is available for similar backup scenarios (e.g., via Azure Backup Agent or other tools), add equivalent Linux instructions and examples.
  • Explicitly state early in the documentation that MABS is Windows-only, and provide links to Linux backup solutions if applicable.
  • Where possible, include PowerShell and CLI examples alongside GUI instructions, and mention if/when these are only available on Windows.
  • Add a section or note addressing Linux users, guiding them to appropriate documentation for their platform.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-all-files-volume-mars.md .../main/articles/backup/restore-all-files-volume-mars.md
High Priority View Details →
Scanned: 2025-12-29 18:00
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 instructions and screenshots reference the Microsoft Azure Backup snap-in, which is a Windows-specific tool. There are no examples, instructions, or mentions of Linux systems, nor any cross-platform or Linux alternatives. The documentation assumes the user is operating in a Windows environment and does not address Linux users or provide parity in guidance.
Recommendations
  • Add explicit statements about platform support, clarifying whether the MARS Agent and these instructions are Windows-only or if Linux is supported.
  • If Linux is supported, provide equivalent step-by-step instructions for restoring files on Linux systems, including relevant commands and screenshots.
  • Mention and link to Linux-compatible backup and restore tools (such as Azure CLI, azcopy, or other Azure Backup solutions for Linux) if MARS Agent is not available for Linux.
  • Ensure that any platform-specific limitations or differences are clearly documented at the beginning of the article.
  • Consider adding a comparison table or section that outlines feature parity and differences between Windows and Linux restore processes.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-azure-backup-server-vmware.md .../articles/backup/restore-azure-backup-server-vmware.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing exclusively on the Microsoft Azure Backup Server (MABS) Administrator Console, which is a Windows-only tool. All procedures and screenshots are based on the Windows GUI. Individual file restore (ILR) is only supported for Windows Server VMs, with no mention of Linux VM support or equivalent Linux file-level recovery workflows. Registry key modifications are described using Windows Registry paths, and there are no Linux-specific instructions, examples, or considerations.
Recommendations
  • Include explicit statements about the support (or lack thereof) for Linux VMs, especially for individual file recovery. If unsupported, clarify this early in the documentation.
  • If Linux VM file-level recovery is supported, provide equivalent step-by-step instructions and screenshots for Linux VMs, or link to relevant Linux recovery documentation.
  • Mention and document any Linux tools, commands, or workflows that can be used in conjunction with MABS for Linux VM recovery.
  • When describing configuration changes (e.g., increasing parallel restores), note whether these are only applicable to Windows environments and provide Linux alternatives if available.
  • Consider adding a comparison table summarizing feature parity (or gaps) between Windows and Linux VM recovery scenarios.
GitHub Create Pull Request
← Previous Page 9 of 21 Next →