← Back to Dashboard
10
Pages Scanned
3
Pages Flagged
10
Changed Pages
30.0%
% Pages Flagged

Scan Information

Started At: 2025-07-14 17:05:46

Finished At: 2025-07-14 17:33:54

Status: completed

Target URL: https://github.com/MicrosoftDocs/azure-docs/tree/main/articles

Current Phase: discovery

Problematic Pages

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/microsoft-azure-backup-server-protection-v3.md [View Details]
High Priority
Bias Types:
⚠️ missing_linux_example
⚠️ windows_first
⚠️ windows_tools
Summary:
The documentation page demonstrates a strong Windows bias. All workload examples, supported platforms, and backup scenarios are focused on Windows operating systems and Microsoft workloads (Windows Server, SQL Server, Exchange, SharePoint, Hyper-V). Linux is only mentioned as a guest OS in Hyper-V or VMware, with no details on native Linux backup, file-level recovery, or parity of features. Windows-specific tools and technologies (NTFS, VSS, ReFS, Windows Management Framework, NTLM authentication) are referenced throughout, and there are no Linux-specific instructions, requirements, or examples. The matrix and narrative consistently list Windows scenarios first or exclusively.
Recommendations:
  • Add explicit support matrix rows for native Linux workloads (not just as VMs), including supported distributions, file systems, and backup/recovery capabilities.
  • Provide Linux-specific requirements, limitations, and supported features (e.g., file-level backup, application-aware backup, snapshot mechanisms like LVM or filesystem freeze).
  • Include Linux examples and scenarios alongside Windows ones, ensuring parity in documentation structure and detail.
  • Reference Linux tools and patterns (e.g., ext4, XFS, LVM, rsync, SSH-based authentication) where relevant.
  • Clarify any feature gaps or differences between Windows and Linux support, and provide guidance or workarounds for Linux users.
  • Avoid listing only Windows-specific technologies (NTFS, VSS, ReFS) without mentioning Linux equivalents or alternatives.
GitHub Create pull request
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/microsoft-azure-backup-server-protection-v3-ur1.md [View Details]
High Priority
Bias Types:
⚠️ windows_first
⚠️ missing_linux_example
⚠️ windows_tools
Summary:
The documentation page demonstrates a strong Windows bias. Windows workloads and tools are described in detail and appear first in all tables and sections. Linux support is limited to guest VMs, with no examples or details for native Linux workloads, file systems, or application backups. Windows-specific technologies (NTFS, VSS, ReFS, Windows domains, etc.) are referenced throughout, while Linux equivalents are not mentioned. Recovery options for Linux are limited and less granular than for Windows. There are no PowerShell examples, but the overall structure and content heavily favor Windows environments.
Recommendations:
  • Add explicit examples and documentation for protecting native Linux workloads (e.g., file-level backup, application backup for Linux-based apps like MySQL, PostgreSQL).
  • Include Linux file system support details (e.g., ext4, xfs, btrfs) and clarify any limitations or requirements.
  • Describe Linux-specific backup and recovery workflows, including agent installation and configuration on Linux systems.
  • Provide parity in recovery options for Linux VMs (e.g., item-level/file-level recovery) or clearly state limitations and roadmap.
  • Reference Linux authentication and domain/workgroup equivalents where Windows domains are discussed.
  • List Linux tools or commands where Windows tools (e.g., VSS, NTFS, ReFS) are mentioned, or clarify that such features are unavailable.
  • Reorganize tables and sections to give Linux workloads equal prominence, not always after Windows.
GitHub Create pull request
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/gateway-migration.md [View Details]
High Priority
Bias Types:
⚠️ powershell_heavy
⚠️ missing_linux_example
⚠️ windows_tools
Summary:
The documentation page demonstrates a bias toward Windows by providing migration instructions and advanced configuration steps (such as adding multiple prefixes to GatewaySubnet) exclusively via PowerShell, with no mention of Azure CLI, Bash, or other cross-platform/Linux-friendly tools. There are no Linux-specific or cross-platform command examples, and PowerShell is presented as the only scripting interface for automation, which may disadvantage Linux users.
Recommendations:
  • Provide equivalent Azure CLI examples for all PowerShell instructions, especially for migration and subnet configuration tasks.
  • Explicitly mention cross-platform options (e.g., Azure CLI, Bash scripts) alongside PowerShell in all relevant sections and next steps.
  • Where PowerShell is required due to feature gaps, clearly state this and provide a roadmap or workaround for Linux users.
  • Add a section or callout for Linux/macOS administrators, summarizing which steps can be performed using cross-platform tools and which currently require PowerShell.
  • Ensure that links to migration guides and troubleshooting include both PowerShell and Azure CLI/Bash options where possible.
GitHub Create pull request

No problematic pages found in this scan. All pages appear to be Linux-friendly! 🐧