Azure Docs

14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

2185 issues found
Showing 676-700 of 2185 flagged pages
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/about-azure-vm-restore.md ...s/blob/main//articles/backup/about-azure-vm-restore.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by referencing PowerShell as the tool for restoring encrypted VMs, and by linking only to Windows-specific encryption documentation. There are no Linux-specific examples or references for restoring encrypted VMs, nor are Linux tools or workflows mentioned. The restore scenarios and links focus on Windows VMs and tools, with Linux parity missing in critical restore operations.
Recommendations
  • Add explicit examples and instructions for restoring encrypted Linux VMs, including references to relevant Linux documentation.
  • Provide parity in tooling by mentioning CLI or Bash-based workflows alongside PowerShell for VM restore operations.
  • Include links to Linux disk encryption documentation (e.g., for VMs encrypted with Azure Disk Encryption for Linux).
  • Ensure that restore scenarios and troubleshooting sections address both Windows and Linux VMs equally, with clear distinctions where workflows differ.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/automation-backup.md ...e-docs/blob/main//articles/backup/automation-backup.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is repeatedly mentioned as a primary automation method, and in automation scenarios, PowerShell is listed before CLI and other cross-platform tools. There are no explicit Linux-specific examples or mentions of Bash scripting, and the sample automation scenarios focus on PowerShell and Azure Automation Runbooks (which are often Windows-centric), without providing equivalent Linux/Bash/CLI-focused walkthroughs.
Recommendations
  • Provide explicit Linux/Bash/CLI examples alongside PowerShell in all automation scenarios.
  • When listing automation methods, alternate or randomize the order, or list CLI before PowerShell to avoid a 'Windows-first' impression.
  • Include sample scripts or walkthroughs using Bash and Azure CLI for configuring backups, exporting data, and automating responses.
  • Highlight cross-platform compatibility for all automation clients, and clarify when a method is platform-specific.
  • Add references to Linux-native tools or scripting environments where appropriate (e.g., Bash, shell scripts, cron jobs for scheduling).
GitHub Create Pull Request
Azure Docs 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-12 23:44
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, with all examples and instructions referencing Windows tools (e.g., robocopy, Windows Server Backup utility, PowerShell). There is no mention of Linux support, tools, or examples, and the MARS agent is implicitly presented as a Windows-only solution. Linux users are not addressed, and there are no cross-platform considerations.
Recommendations
  • Clearly state in the introduction whether the MARS agent is Windows-only or if Linux is supported. If it is Windows-only, make this explicit to set expectations.
  • If Linux support exists or is planned, provide equivalent Linux examples and tools (e.g., rsync instead of robocopy, bash scripts instead of PowerShell).
  • If the product is not available for Linux, suggest alternative Azure backup solutions for Linux workloads and link to their documentation.
  • Avoid assuming PowerShell or Windows tools by default; where possible, provide cross-platform automation examples.
  • Add a section or FAQ entry addressing Linux/Unix users and their options for backup and restore with Azure.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/active-directory-backup-restore.md ...in//articles/backup/active-directory-backup-restore.md
High Priority View Details →
Scanned: 2025-07-12 23:44
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 (e.g., PowerShell scripts, ntdsutil.exe, DSRM) are Windows-specific, with no mention of Linux-based alternatives or scenarios. The documentation assumes the use of Windows Server for domain controllers and does not address cross-platform or Samba-based Active Directory deployments.
Recommendations
  • Include a section or note clarifying support (or lack thereof) for non-Windows (e.g., Samba on Linux) Active Directory domain controllers, and provide guidance if supported.
  • Where PowerShell scripts are given, provide equivalent commands for Linux-based management tools if available (e.g., samba-tool for Samba AD DCs).
  • Mention and link to documentation for backing up and restoring Samba-based Active Directory environments if Azure Backup or similar tools support them.
  • Explicitly state that the procedures are for Windows Server-based AD, and provide parity guidance or alternatives for Linux-based AD implementations where possible.
  • Avoid assuming all users are on Windows; consider the needs of mixed-environment administrators.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/archive-tier-support.md ...ocs/blob/main//articles/backup/archive-tier-support.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page lists PowerShell as a supported client before CLI, and the only explicit client pivots/examples referenced are for Azure portal and PowerShell, with CLI mentioned but not demonstrated. There are no Linux-specific examples or references, and the workloads and screenshots focus exclusively on Azure Virtual Machines (typically Windows-centric in Azure documentation), with no mention of Linux VMs or Linux command-line usage. This creates a subtle Windows bias by prioritizing Windows tools and omitting Linux parity.
Recommendations
  • Provide explicit CLI (az) examples alongside PowerShell for all operations, especially for moving recovery points to archive tier.
  • Include references and screenshots for both Windows and Linux VMs where applicable.
  • Ensure that documentation pivots and links for CLI are as prominent as those for PowerShell and portal.
  • Add a section or examples specifically addressing Linux VM backup and archive tier usage.
  • Clarify that the features and procedures apply equally to Linux VMs, or note any differences.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/azure-backup-glossary.md ...cs/blob/main//articles/backup/azure-backup-glossary.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The glossary page demonstrates a Windows bias in several ways. Windows-specific technologies (such as VSS, DPM, MABS, and MARS Agent) are referenced without Linux equivalents or with Linux mentioned only as an afterthought. The 'Application consistent backup' entry foregrounds Windows VSS and only parenthetically mentions Linux scripts. Several backup features (bare metal backup, system state backup, item-level restore) are described in terms of Windows workloads. References to Azure PowerShell are present, but there is no mention of Linux-native tools or workflows. Linux backup scenarios and terminology are largely absent or treated as exceptions.
Recommendations
  • For each Windows-specific technology or term (e.g., VSS, DPM, MABS, MARS Agent), add corresponding Linux equivalents or clarify Linux support (e.g., mention pre/post snapshot scripts, Linux backup agents, or open-source tools).
  • In definitions like 'Application consistent backup', provide equal detail for Linux approaches (e.g., describe how pre/post scripts work, mention supported Linux distributions, and link to relevant documentation).
  • Where backup features are described in a Windows-centric way (e.g., bare metal backup, system state backup), clarify Linux support or note if the feature is not available for Linux.
  • Add references to Linux-native tools and workflows (e.g., Azure CLI, REST API usage from Linux, Linux backup agents) alongside or before Windows/PowerShell references.
  • Ensure that examples and terminology are inclusive of both Windows and Linux workloads, or explicitly state any platform limitations.
GitHub Create Pull Request
Azure Docs 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-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments. All command-line examples use PowerShell or Windows executables, and there are no Linux-specific instructions or examples. Windows tools and patterns (such as PowerShell cmdlets, .exe installers, and references to Windows Server features like Hyper-V) are mentioned exclusively and before any Linux equivalents. Linux support is only briefly mentioned as a footnote, with no practical guidance or parity in examples.
Recommendations
  • Provide explicit Linux backup and recovery instructions, including example commands for agent installation and configuration on Linux VMs.
  • Include Linux-specific prerequisites and troubleshooting steps, not just a single line about file-consistent snapshots.
  • Offer parity in command-line examples: for every PowerShell or .exe example, provide a Linux shell equivalent (e.g., bash commands, systemd service management, etc.).
  • Clarify any limitations or differences in backup and recovery workflows for Linux VMs, and provide guidance for common Linux distributions.
  • Reference Linux-native tools or patterns where appropriate, and avoid assuming a Windows-only environment in procedures and screenshots.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/how-to-manage-twin.md ...lob/main//articles/digital-twins/how-to-manage-twin.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a bias toward Windows development environments. All code samples are in C# and reference .NET SDKs, with setup instructions tailored to Visual Studio and Windows-centric workflows. There are no Linux-specific instructions, examples, or mentions of cross-platform command-line usage (e.g., Bash, shell scripts). The guidance for downloading files and setting up projects assumes a Windows GUI (right-click, Save As), and package installation commands are shown only for dotnet CLI, with no mention of alternatives for Linux users. There is also a lack of parity in showing how to perform operations using REST APIs, Azure CLI, or other cross-platform tools.
Recommendations
  • Add explicit instructions and examples for Linux users, including setup using common Linux editors (e.g., VS Code, Vim) and command-line tools.
  • Provide alternative code samples or instructions for using the Azure CLI and REST API directly, which are cross-platform.
  • Include Bash shell commands for downloading files (e.g., using wget or curl) alongside the Windows GUI instructions.
  • Clarify that the .NET SDK and dotnet CLI are cross-platform, and provide installation instructions for Linux and macOS.
  • When referencing project setup, mention cross-platform editors and workflows, not just Visual Studio.
  • Ensure that any references to tools or workflows (such as file downloads or dependency management) include both Windows and Linux equivalents.
  • Consider including at least one example in a language commonly used on Linux (e.g., Python) if supported by the SDK.
GitHub Create Pull Request
Azure Docs 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-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias, primarily in the 'Next steps' section, where Azure PowerShell is mentioned as a primary method for backup and restore operations, and is listed before Azure CLI in some cases. There are no explicit Linux or Bash examples or references, and the documentation does not mention Linux-specific tools or workflows, despite AKS being a cross-platform service often managed from Linux/macOS environments. The focus on Azure portal and PowerShell, with CLI mentioned less prominently, may disadvantage Linux users.
Recommendations
  • Ensure that Azure CLI (which is cross-platform) is always mentioned alongside or before Azure PowerShell, especially in 'Next steps' and example sections.
  • Add explicit Bash/Linux shell examples or references where command-line operations are discussed.
  • Clarify that all CLI commands work on Linux, macOS, and Windows, and provide links to CLI installation/setup for non-Windows platforms.
  • If PowerShell is referenced, also provide equivalent Bash/CLI instructions for parity.
  • Consider including a section or note on managing AKS backup from Linux/macOS environments to reinforce cross-platform support.
GitHub Create Pull Request
Azure Docs 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-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias, particularly in the 'Next steps' section, where Azure PowerShell is listed before ARM/Bicep/Terraform and is given equal prominence to Azure CLI. There is also a reference to Azure PowerShell for backup/restore operations, but no explicit mention of Linux-native tools or shell scripting. While the core AKS backup functionality is Linux-centric (the backup extension only supports Linux-based node pools), the documentation does not provide Linux shell (bash) examples or highlight Linux command-line workflows, and PowerShell is referenced as a primary automation tool.
Recommendations
  • In the 'Next steps' section, list Azure CLI before Azure PowerShell to reflect the Linux-first nature of AKS clusters and their management.
  • Provide explicit bash/shell command examples for backup and restore operations, especially for Linux administrators.
  • Clarify that Azure PowerShell is cross-platform, but highlight that Azure CLI is the primary tool for Linux environments.
  • Consider adding a section or callout for Linux-native automation (e.g., bash scripting, kubectl usage) where relevant.
  • Ensure parity in documentation examples and workflows for both Windows and Linux users, especially in automation and scripting contexts.
GitHub Create Pull Request
Azure Docs 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-12 23:44
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 primarily referencing the Azure portal and Azure PowerShell for backup and restore operations, with no mention of Azure CLI or Linux-native tooling. The only command-line example shown is with kubectl, which is cross-platform, but all Azure-specific automation is directed to PowerShell. There are no Azure CLI examples or Linux shell scripts, and the 'Next steps' section lists PowerShell before any other automation options. This may make Linux users feel secondary or unsupported.
Recommendations
  • Add Azure CLI examples alongside or before PowerShell examples for all automation steps, especially for backup and restore operations.
  • Explicitly mention that all kubectl commands work cross-platform and provide any necessary Linux-specific notes.
  • In the 'Next steps' section, list Azure CLI and Linux-native options before or alongside PowerShell.
  • Where screenshots or UI instructions are given, consider providing CLI equivalents for users who prefer scripting or non-Windows environments.
  • Review all references to Azure PowerShell and ensure Azure CLI parity is documented and linked.
GitHub Create Pull Request
Azure Docs 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-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page references Azure PowerShell as an alternative method for restoring AKS clusters, but does not mention or provide equivalent instructions for Linux-native tools, Azure CLI, or kubectl. The only explicit command-line example is PowerShell, and there is no mention of Linux workflows or parity. This suggests a bias toward Windows/PowerShell environments, both by omission and by presenting PowerShell as the primary or only alternative to the portal.
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 examples using kubectl for relevant restore operations, especially for item-level or namespace restores.
  • When referencing PowerShell, always provide equivalent CLI/bash examples and mention them first or equally.
  • Explicitly state that all operations can be performed from Linux, macOS, and Windows, and clarify any OS-specific requirements.
  • Review linked articles (e.g., the PowerShell restore guide) to ensure Linux/CLI parity and cross-reference them here.
GitHub Create Pull Request
Azure Docs 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-12 23:44
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, specifically Hyper-V on Windows Server, and Microsoft Azure Backup Server (MABS), which is itself a Windows-based product. Linux is only briefly mentioned as a supported guest OS, with no detailed instructions or examples for Linux VMs. All procedures, tools, and screenshots are Windows-centric, and item-level recovery is explicitly stated as available only for Windows Server VMs. There are no Linux command-line examples, nor guidance for Linux-specific backup or recovery scenarios.
Recommendations
  • Provide explicit step-by-step instructions for backing up and restoring Linux VMs, including any differences or limitations compared to Windows VMs.
  • Include examples or screenshots showing the process for Linux VMs, or clarify the process if it is identical.
  • Document any Linux-specific prerequisites, such as required integration components or agent installation steps.
  • Clarify the limitations for Linux VMs (e.g., only file-consistent snapshots) and provide guidance on best practices for Linux backup and recovery.
  • If item-level recovery is not supported for Linux, state this clearly and suggest alternative approaches for Linux file recovery.
  • Where possible, use neutral terminology (e.g., 'guest OS' instead of 'Windows Server VM') and avoid assuming the guest is always Windows.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-web-pubsub/tutorial-serverless-notification.md ...s/azure-web-pubsub/tutorial-serverless-notification.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation exhibits a mild Windows bias, primarily through the exclusive mention of the 'Storage Emulator' (a Windows-only tool) for local development and troubleshooting, and by referencing Microsoft Edge as the suggested browser. There are no explicit PowerShell or cmd.exe examples, and most commands are cross-platform (bash/Azure CLI). However, the documentation does not mention Linux/macOS equivalents for the Storage Emulator, nor does it reference cross-platform storage emulators like Azurite. Additionally, the troubleshooting note for local storage only addresses the Windows scenario, omitting guidance for Linux/macOS users.
Recommendations
  • Mention Azurite as the recommended cross-platform storage emulator for local development, and provide installation and usage instructions for Linux/macOS users.
  • Update troubleshooting notes to include steps for Linux/macOS users, referencing Azurite or other supported storage emulators.
  • Avoid recommending Windows-specific browsers (such as Edge) unless necessary, or provide alternatives for other platforms.
  • Wherever a tool or step is platform-specific, clearly indicate alternatives or equivalent steps for Linux/macOS.
  • Consider adding a table or section summarizing platform-specific requirements and solutions to ensure parity.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-alternate-dpm-server-troubleshoot.md ...ckup/backup-azure-alternate-dpm-server-troubleshoot.md
High Priority View Details →
Scanned: 2025-07-12 23:44
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, referencing only Windows Server, Windows Client, and DPM (Data Protection Manager), which are all Windows-specific. There are no examples or troubleshooting steps for Linux-based backup servers or agents, nor is there mention of Linux-compatible tools or workflows. The terminology and recommendations assume a Windows ecosystem.
Recommendations
  • Include troubleshooting steps and error messages relevant to Linux-based backup scenarios, if supported.
  • Mention whether Azure Backup Server supports Linux environments, and if not, clarify this limitation explicitly.
  • Provide parity in examples and recommendations for both Windows and Linux users, including references to Linux backup agents or tools where applicable.
  • If only Windows is supported, add a note at the beginning of the documentation to inform users that the guidance is Windows-specific.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-arm-restore-vms.md .../main//articles/backup/backup-azure-arm-restore-vms.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific examples and links (such as PowerShell and Windows VM tutorials) are provided without Linux equivalents, especially in sections about restoring VMs with special configurations, availability sets, and network configurations. References to Windows tools and patterns (e.g., bcdedit, netdom, RDP, Windows-specific licensing) are present, while Linux-specific guidance is minimal or absent. Where Linux is mentioned, it is often as an aside, and no Linux command-line examples are given.
Recommendations
  • Provide Linux-specific examples and links alongside Windows ones, especially for restoring VMs, configuring network settings, and managing restored VMs.
  • Include Azure CLI and Bash script examples for operations currently only shown with PowerShell or Windows tools.
  • Reference Linux documentation (e.g., for attaching disks, configuring network interfaces, resetting passwords) in parallel with Windows documentation.
  • When mentioning Windows-specific tools (e.g., bcdedit, netdom), provide equivalent Linux troubleshooting steps (e.g., using GRUB, chroot, or cloud-init).
  • Clarify which restore steps or limitations apply to Linux VMs, and explicitly document any differences in post-restore steps for Linux (e.g., SSH key management, agent installation).
  • Balance the order of presentation so that Linux and Windows are treated equally (e.g., do not always mention Windows first or exclusively).
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-backup-server-vmware.md ...//articles/backup/backup-azure-backup-server-vmware.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows environments, with all command-line examples using PowerShell, exclusive use of Windows tools (e.g., Registry Editor, Certificate Import Wizard), and instructions that assume the Azure Backup Server is running on Windows. There are no examples or guidance for Linux-based management or alternative tooling, and Windows-specific patterns (such as registry edits) are presented as the only option.
Recommendations
  • Provide equivalent command-line examples using Bash or other Linux shells where possible, especially for certificate management and scripting.
  • Document how to perform certificate import and trust establishment on Linux-based Azure Backup Server installations (if supported), including use of tools like openssl and update-ca-certificates.
  • Clarify whether Azure Backup Server can be installed or managed from Linux, and if not, explicitly state this limitation early in the prerequisites.
  • Where registry edits are required, offer alternative configuration methods for Linux (if supported), or note the lack of Linux support.
  • For scripts (e.g., ExcludeDisk.ps1), provide or reference Linux-compatible alternatives or explain the Windows-only limitation.
  • Add a section or callout summarizing OS support and any platform-specific limitations, so Linux users can quickly determine applicability.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-backup-cloud-as-tape.md ...//articles/backup/backup-azure-backup-cloud-as-tape.md
High Priority View Details →
Scanned: 2025-07-12 23:44
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 referencing System Center Data Protection Manager (DPM), a Windows-only tool, without mentioning Linux backup solutions or agents. The 'Try Azure Backup' link points specifically to a Windows/MARS agent guide, and there are no examples or references for Linux environments or tools. No Linux-specific instructions, screenshots, or parity guidance are provided.
Recommendations
  • Include equivalent Linux backup agent options and instructions, such as using Azure Backup Server or Azure CLI for Linux workloads.
  • Provide examples and screenshots for configuring backup and retention policies on Linux systems.
  • Add links to Linux-specific Azure Backup documentation (e.g., 'Back up Linux VMs with Azure Backup').
  • Mention cross-platform compatibility and clarify which features/tools are Windows-only versus available for Linux.
  • Ensure that introductory and 'Next steps' sections offer Linux guidance alongside Windows.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-backup-sharepoint.md ...ain//articles/backup/backup-azure-backup-sharepoint.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes backup and restore procedures using System Center Data Protection Manager (DPM), a Windows-only tool, with no mention of Linux-based alternatives or cross-platform tools. All instructions, terminology, and referenced tools are specific to the Windows ecosystem, and there are no examples or guidance for Linux environments or administrators.
Recommendations
  • Include information about cross-platform backup solutions that support SharePoint or similar workloads, if available.
  • If DPM is the only supported tool, explicitly state that it is Windows-only and suggest alternatives for Linux environments where possible.
  • Provide parity by referencing or linking to Linux-compatible Azure backup tools or scripts, even if SharePoint itself is Windows-based.
  • Add a section clarifying platform requirements and limitations, so Linux administrators are aware of the scope and can seek appropriate solutions.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-backup-sharepoint-mabs.md ...articles/backup/backup-azure-backup-sharepoint-mabs.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All instructions, tools, and examples assume a Windows Server context, with references to Windows-specific components such as the Registry Editor, NT AUTHORITY\SYSTEM, and the use of CMD commands. There are no examples or guidance for Linux environments, nor any mention of Linux-compatible tools or workflows. The documentation presumes the use of Windows-based SharePoint and SQL Server, and all administrative steps are described using Windows paradigms.
Recommendations
  • Explicitly state early in the documentation that MABS and SharePoint backup are only supported on Windows, if that is the case. If Linux support is possible, provide equivalent instructions, tools, and examples for Linux environments.
  • Wherever command-line instructions are given (e.g., CMD, Registry Editor), provide Linux shell equivalents or clarify if these steps are not applicable to Linux.
  • If MABS or SharePoint backup is not supported on Linux, clearly mention this limitation in the prerequisites section.
  • For monitoring and notification steps, include guidance for integrating with Linux-based monitoring tools (e.g., syslog, Nagios) if possible.
  • Review all tool and path references (e.g., %Program Files%, Registry keys) and provide Linux alternatives or note their absence.
  • If the product is Windows-only, consider a brief section explaining why Linux is not supported and suggest alternative backup strategies for Linux-based SharePoint-like deployments.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-backup-sql.md .../blob/main//articles/backup/backup-azure-backup-sql.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically referencing Data Protection Manager (DPM), which is a Windows-only backup solution. All examples, screenshots, and instructions assume the use of Windows tools and interfaces, with no mention of Linux-based SQL Server deployments or equivalent backup workflows for Linux. There are no Linux or cross-platform command-line examples, and all prerequisites and operational steps are tailored to Windows environments.
Recommendations
  • Add a section or parallel guide for backing up SQL Server on Linux to Azure, using supported tools (such as Azure Backup integration with Linux, or native SQL Server backup to Azure Blob Storage).
  • Include Linux-specific prerequisites and limitations, such as required packages, permissions, and supported distributions.
  • Provide command-line examples for Linux environments (e.g., using bash scripts, sqlcmd, or az CLI) alongside or in place of GUI-based Windows instructions.
  • Clarify in the introduction that the guide is specific to Windows/DPM, and link to equivalent Linux documentation if available.
  • Mention cross-platform alternatives for environments where DPM is not available, such as Azure Backup Server (MABS) or native SQL Server backup to Azure for Linux.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-move-recovery-services-vault.md ...es/backup/backup-azure-move-recovery-services-vault.md
High Priority View Details →
Scanned: 2025-07-12 23:44
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 detailed PowerShell examples for moving Recovery Services vaults, mentioning PowerShell before CLI, and referencing Windows-specific update instructions before Linux equivalents. There are no Linux shell or Bash examples, and Linux guidance is limited to generic statements (e.g., 'refer to distributor guidance').
Recommendations
  • Provide equivalent Bash or shell script examples for moving Recovery Services vaults using the Azure CLI, especially for common Linux environments.
  • Present CLI examples before or alongside PowerShell examples to avoid the impression that Windows tooling is primary.
  • Expand Linux-specific operational guidance (e.g., how to update certificates and CRLs on popular distributions) rather than deferring to distributor documentation.
  • Ensure that all instructions and screenshots are platform-agnostic or include both Windows and Linux perspectives where relevant.
  • Where tools/scripts are referenced, clarify their cross-platform compatibility or provide alternatives for Linux users.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-dataprotection-use-rest-api-backup-disks.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-dataprotection-use-rest-api-backup-disks.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. In the 'Next steps' section, Azure PowerShell is listed before Azure CLI, which is more cross-platform and widely used on Linux. Additionally, the only explicit link for assigning permissions refers to a PowerShell-based guide (backup-managed-disks-ps.md#assign-permissions), with no mention or example of using Azure CLI or other Linux-native tools for this step. No Linux- or Bash-specific command-line examples are provided, and the documentation does not clarify that all REST API operations are platform-agnostic or show how to use tools like curl or az CLI from a Linux shell.
Recommendations
  • When referencing command-line tools, always mention Azure CLI alongside or before PowerShell, as CLI is cross-platform and widely used on Linux.
  • Provide explicit Linux/Bash/curl examples for REST API calls, demonstrating how to perform the same operations from a Linux environment.
  • For permission assignment, link to both PowerShell and Azure CLI instructions, or provide a platform-neutral explanation with both command sets.
  • Clarify in the introduction that the REST API is platform-agnostic and can be used from any OS, and provide example invocations using tools available on Linux.
  • In 'Next steps', list Azure CLI before PowerShell, or group them together as 'Azure CLI/PowerShell' to avoid implying a Windows-first workflow.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-monitoring-built-in-monitor.md ...les/backup/backup-azure-monitoring-built-in-monitor.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific backup tools (DPM, MABS, MARS) and providing links and examples that focus on managing Windows Server backups. There is no mention of Linux backup agents, Linux-specific monitoring, or examples relevant to Linux workloads. The terminology and guidance assume a Windows-centric environment, omitting Linux equivalents and usage patterns.
Recommendations
  • Include explicit references to Linux backup agents (such as Azure Backup for Linux VMs or Azure VM backup for Linux) and how to monitor them.
  • Provide examples or links for monitoring Linux-based workloads, not just Windows Server or DPM/MABS/MARS scenarios.
  • Mention Linux-specific considerations or limitations in backup item naming, monitoring, and alerting.
  • Ensure parity in documentation structure by giving Linux and Windows examples side by side where relevant.
  • Add links to documentation for managing and monitoring Linux backup jobs and items.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-database-postgresql.md ...n//articles/backup/backup-azure-database-postgresql.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias, particularly in the section about running the PowerShell script to grant privileges to database users. It provides step-by-step instructions and screenshots for setting environment variables using Windows Control Panel and System Properties, but omits equivalent instructions for Linux or macOS environments. The use of PowerShell as the primary scripting example and the focus on Windows-specific tools and UI patterns (such as Control Panel and environment variable dialogs) further reinforce this bias. While the documentation mentions that the PSQL tool can be used, it does not provide Linux-specific guidance or examples, nor does it show how to run the script or set environment variables on Linux systems.
Recommendations
  • Provide parallel instructions and screenshots for Linux (and optionally macOS) users, including how to set environment variables (e.g., using export in bash or editing ~/.bashrc).
  • Include examples of running the privilege-granting script using bash or shell scripts, not just PowerShell.
  • Clarify that the PowerShell script can be adapted for Linux environments, or provide a bash version if possible.
  • When referencing tools like PSQL, include installation and usage instructions for both Windows and Linux.
  • Avoid assuming the user is on Windows when describing UI navigation (e.g., Control Panel); instead, offer cross-platform alternatives.
  • In all sections where scripts or environment configuration are required, ensure Linux parity by showing both Windows and Linux workflows.
GitHub Create Pull Request
← Previous Page 28 of 88 Next →