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 926-950 of 1604 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-cloud-as-tape.md ...n/articles/backup/backup-azure-backup-cloud-as-tape.md
High Priority View Details →
Scanned: 2025-08-19 00:01
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, as the primary on-premises backup solution. There are no mentions of Linux backup agents, Linux-compatible tools, or examples relevant to Linux environments. The 'Try Azure Backup' link specifically points to a Windows/MARS agent guide, further emphasizing the Windows-centric approach. No Linux-specific instructions, screenshots, or parity guidance are present.
Recommendations
  • Include references to Linux backup solutions supported by Azure Backup, such as Azure Backup Server or native Linux agents.
  • Provide example workflows, screenshots, or command-line instructions for configuring Azure Backup on Linux systems.
  • Add links to documentation for Linux backup scenarios alongside or before Windows-specific links.
  • Clarify in the introduction that Azure Backup supports both Windows and Linux workloads, and outline any differences in setup or capabilities.
  • Ensure parity in examples and terminology, avoiding exclusive focus on Windows tools like DPM.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-exchange-server.md ...articles/backup/backup-azure-backup-exchange-server.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes backup procedures using System Center Data Protection Manager (DPM), a Windows-only tool, and all steps, screenshots, and file paths are specific to Windows environments. There are no examples or mentions of Linux-based Exchange servers, Linux tools, or cross-platform alternatives. Windows conventions (e.g., C:\ paths, DPM Console UI) are used throughout, and no Linux parity or guidance is provided.
Recommendations
  • Explicitly state that DPM is a Windows-only solution and clarify platform limitations at the start of the article.
  • If possible, provide links or references to Linux-compatible backup solutions for Exchange (if supported), or clarify that Exchange Server is only supported on Windows.
  • Include a section or note for users seeking to back up Exchange workloads on Linux (if such scenarios exist), or direct them to relevant documentation for Linux-based backup tools.
  • Ensure that related content and automation examples (such as PowerShell scripts) are accompanied by notes about platform compatibility, and suggest alternatives for non-Windows environments where feasible.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-server-vmware.md ...n/articles/backup/backup-azure-backup-server-vmware.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows environments. All command-line examples use PowerShell scripts, Windows Registry edits, and Windows-specific tools (e.g., Certificate Import Wizard, .reg files). There are no Linux or cross-platform instructions, and all administrative steps assume the Azure Backup Server is running on Windows. Linux equivalents for certificate management, scripting, or configuration are not mentioned or provided.
Recommendations
  • Provide equivalent Linux-based instructions for certificate import (e.g., using openssl and update-ca-certificates).
  • Offer shell script (bash) alternatives for PowerShell scripts, or clarify that MABS is Windows-only if that is the case.
  • Document how to perform configuration steps (such as editing registry or service management) on Linux, or state platform limitations explicitly.
  • If MABS is not supported on Linux, add a clear note at the top of the documentation stating that all instructions are for Windows environments only.
  • Include Linux/Unix command-line examples where possible, especially for VMware environments that may be managed from non-Windows systems.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-sharepoint.md ...main/articles/backup/backup-azure-backup-sharepoint.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation is heavily focused on System Center Data Protection Manager (DPM), a Windows-only backup solution, and does not mention or provide examples for Linux environments or tools. All instructions, tools, and workflows assume a Windows/SharePoint/DPM ecosystem, and the only automation reference is to PowerShell. There are no Linux equivalents, alternative tools, or cross-platform considerations discussed.
Recommendations
  • Include information on whether Linux-based SharePoint alternatives (e.g., SharePoint Online, or open-source equivalents) can be backed up to Azure, and how.
  • If DPM is Windows-only, clearly state this limitation and suggest Azure-native or cross-platform backup solutions for Linux environments.
  • Provide examples or references for backing up non-Windows workloads (e.g., Linux web servers or databases) to Azure, possibly in a 'See also' section.
  • If automation is discussed via PowerShell, mention or provide equivalent CLI/bash/REST API examples for Linux users where possible.
  • Clarify in the prerequisites and introduction that the documented workflow is specific to Windows environments, and link to Linux backup documentation if available.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-database-postgresql.md ...in/articles/backup/backup-azure-database-postgresql.md
High Priority View Details →
Scanned: 2025-08-19 00:01
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 in several ways: PowerShell is emphasized as the primary scripting method, and the only detailed example for granting database privileges is a PowerShell script. Instructions for setting environment variables and running scripts are given exclusively for Windows (via Control Panel and System Properties), with no equivalent Linux/macOS guidance. While the PSQL tool is mentioned, its setup and usage are only described in a Windows context. There are no CLI/bash or Linux-native examples for these steps.
Recommendations
  • Provide equivalent Linux/macOS instructions for setting environment variables (e.g., using export in bash or editing ~/.bashrc).
  • Include bash or shell script examples for granting database privileges, alongside or instead of PowerShell scripts.
  • When referencing tools like PSQL, show installation and usage steps for both Windows and Linux/macOS.
  • Avoid assuming the user is on Windows in step-by-step guides; offer cross-platform alternatives where possible.
  • When mentioning scripting options (PowerShell, CLI), present them in a neutral order or group, not with Windows-first prominence.
GitHub Create Pull Request
Backup 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-08-19 00:01
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 PowerShell and Windows-centric tools before Linux equivalents, and by omitting explicit Linux/Unix command-line examples. The only explicit tooling reference for assigning permissions points to a PowerShell-based guide, and the 'Next steps' section lists PowerShell before CLI, which is more cross-platform. There are no Linux-specific instructions or examples, and the documentation does not mention Bash, shell scripting, or Linux-native tools for interacting with the REST API.
Recommendations
  • Provide explicit examples using Azure CLI (az), which is cross-platform, for all operations currently referenced via PowerShell or the Azure portal.
  • When referencing external guides (e.g., for assigning permissions), link to both PowerShell and CLI/Linux instructions, or to a neutral, cross-platform page.
  • In the 'Next steps' section, list Azure CLI before or alongside PowerShell to avoid the impression of Windows-first guidance.
  • Include example REST API invocations using curl or httpie, which are available on Linux, macOS, and Windows, to demonstrate true cross-platform usage.
  • Where scripting is discussed, mention both PowerShell and Bash/shell scripting as options for automation.
  • Audit all referenced links and ensure parity between Windows and Linux instructions throughout the documentation.
GitHub Create Pull Request
Backup 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-08-19 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples for moving Recovery Services vaults, while lacking equivalent Linux shell or cross-platform scripting examples. Windows-specific update instructions are mentioned before Linux, and there is no mention of Linux-native tools or shell commands for resource management beyond the Azure CLI. The CLI section is brief and lacks parity with the PowerShell section, and there are no Bash or Linux-specific automation examples.
Recommendations
  • Provide equivalent Bash or shell script examples for moving Recovery Services vaults using Azure CLI, demonstrating how Linux users can automate these tasks.
  • Ensure that instructions for updating certificates and CRLs on Linux are as detailed as those for Windows, possibly including example commands (e.g., using apt, yum, or update-ca-certificates).
  • Present cross-platform (CLI) instructions before or alongside PowerShell examples, emphasizing that both Windows and Linux users are supported.
  • Mention and link to Linux-native tools or scripting environments (e.g., Bash, zsh) where appropriate, and avoid assuming PowerShell as the default automation environment.
  • Where scripts are provided, offer both PowerShell and Bash/CLI versions to ensure Linux users have clear, actionable guidance.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-delete-vault.md ...blob/main/articles/backup/backup-azure-delete-vault.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. PowerShell is the primary automation method described, with detailed steps and scripts, while Linux-native alternatives are not mentioned. Windows-specific tools (MARS, MABS, DPM, ARMClient via Chocolatey) are referenced without Linux equivalents or cross-platform guidance. The CLI section is minimal and notes its limitations, and there are no Bash or cross-platform scripting examples. The documentation assumes the use of Windows consoles and management tools throughout.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for all PowerShell examples, especially for vault and backup item deletion.
  • Highlight cross-platform tools and workflows (e.g., Azure CLI, REST API) before or alongside Windows/PowerShell methods.
  • Document how to install and use ARMClient on Linux/macOS, including package manager alternatives to Chocolatey.
  • Clarify which management consoles (MARS, MABS, DPM) are Windows-only and suggest Linux-compatible alternatives or note limitations.
  • Add explicit Linux/macOS instructions for script execution, environment setup, and prerequisites.
  • Ensure screenshots and UI steps are not exclusively Windows-centric (e.g., avoid only showing Windows-style context menus or dialogs).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-recovery-services-vault-overview.md ...ackup/backup-azure-recovery-services-vault-overview.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. While it mentions support for both Linux and Windows IaaS VMs, it repeatedly foregrounds Windows-centric tools and scenarios (such as System Center DPM, Windows Server, and Azure Backup Server) without equivalent Linux examples or tools. The 'Next steps' section provides a backup guide specifically for Windows Server but omits any Linux-specific backup instructions. There are no Linux command-line or tool examples, and Windows tools are referenced by name without Linux alternatives.
Recommendations
  • Include explicit Linux backup scenarios and examples, such as backing up a Linux VM or using Linux command-line tools.
  • Balance references to Windows tools (e.g., System Center DPM, Windows Server) with Linux-native backup solutions or mention their parity.
  • In the 'Next steps' section, add links to documentation for backing up Linux VMs and managing Linux workloads.
  • Where possible, provide cross-platform examples or clarify when a feature or tool is Windows-only.
  • Ensure that screenshots, walkthroughs, and sample commands are not exclusively Windows-focused.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-restore-files-from-vm.md .../articles/backup/backup-azure-restore-files-from-vm.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally presents Windows steps, tools, and troubleshooting guidance before Linux equivalents, and often in greater detail. Windows-specific tools and patterns (e.g., registry edits, Windows Explorer, .NET requirements) are described with more prominence and screenshots. PowerShell is referenced as a primary automation method, while Linux CLI is mentioned secondarily. Although Linux steps are present, they are sometimes less detailed or appear after Windows instructions.
Recommendations
  • Present Windows and Linux instructions in parallel or side-by-side, rather than always listing Windows first.
  • Ensure that Linux troubleshooting steps are as detailed as Windows ones, including screenshots and explicit command examples.
  • When referencing automation (e.g., PowerShell), also provide equivalent Bash or shell script examples for Linux.
  • Highlight Linux-specific tools and workflows (e.g., file managers, system utilities) with the same prominence as Windows tools.
  • Where possible, use neutral language and structure (e.g., 'For Windows' and 'For Linux' headings together) to avoid implying Windows is the default or primary platform.
  • Expand the 'Next steps' section to include Linux-focused automation and management guides, not just PowerShell and Azure CLI.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-scdpm-troubleshooting.md .../articles/backup/backup-azure-scdpm-troubleshooting.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows environments, referencing only Windows-specific tools (e.g., 'net stop dpmra'), Windows authentication patterns (NT AUTHORITY\SYSTEM), and making no mention of Linux equivalents or cross-platform considerations. All troubleshooting steps and terminology assume a Windows server context, with no guidance for Linux users or environments.
Recommendations
  • Include troubleshooting steps and examples for Linux environments, if Data Protection Manager or Azure Backup Server supports Linux workloads.
  • Provide equivalent Linux commands (e.g., systemctl or service commands) alongside Windows commands like 'net stop/start'.
  • Mention Linux authentication/user patterns if applicable, not just Windows-specific accounts like 'NT AUTHORITY\SYSTEM'.
  • Clarify in the introduction or prerequisites if the product is Windows-only; if not, ensure Linux parity throughout the documentation.
  • Add notes or sections for Linux-specific errors, logs, and recovery steps where relevant.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-restore-system-state.md ...n/articles/backup/backup-azure-restore-system-state.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is exclusively focused on restoring System State for Windows Server using Azure Backup. All instructions, tools, screenshots, and command-line examples are specific to Windows environments (e.g., Windows Server Backup, wbadmin, MARS agent, Windows Recovery Environment). There are no references to Linux systems, tools, or equivalent recovery processes, and no cross-platform considerations are mentioned.
Recommendations
  • Clearly state in the introduction that the procedure is Windows-specific, and provide links to equivalent Linux backup/restore documentation if available.
  • If Azure Backup supports Linux system state or similar functionality, add a dedicated section or a separate article for Linux, including step-by-step instructions, tools (e.g., rsync, tar, Azure CLI), and recovery workflows.
  • Where possible, mention cross-platform Azure Backup capabilities and clarify any feature gaps between Windows and Linux.
  • If Linux is not supported for system state backup/restore, explicitly state this limitation to set user expectations.
  • Ensure parity in documentation structure and detail for both Windows and Linux scenarios if/when Linux support is available.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-security-feature.md .../main/articles/backup/backup-azure-security-feature.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All examples, tools, and workflows focus exclusively on Microsoft-centric backup solutions (MABS, DPM, MARS), which are only available for Windows environments. There are no references to Linux backup agents, Linux-based workloads, or cross-platform scenarios. Command-line examples and troubleshooting steps reference only Windows tools (e.g., PowerShell cmdlets like Remove-DPMChildDatasource, Remove-OBPolicy). The documentation does not mention or provide parity for Linux backup scenarios, nor does it clarify the lack of support for non-Windows platforms.
Recommendations
  • Explicitly state the Windows-only scope of the documented features and tools at the beginning of the article.
  • Add a section or note addressing the current limitations for Linux and non-Windows workloads, including any roadmap or alternatives for Linux backup security features.
  • If Azure Backup supports Linux workloads in any capacity, provide equivalent examples, workflows, and troubleshooting steps for Linux environments (e.g., using Azure CLI, shell scripts, or Linux-native agents).
  • Avoid referencing only Windows tools and PowerShell cmdlets; where possible, include cross-platform command-line examples (e.g., Azure CLI) or clarify when a feature is Windows-specific.
  • Ensure that future documentation updates track and highlight feature parity (or gaps) between Windows and Linux backup solutions.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-system-state.md ...blob/main/articles/backup/backup-azure-system-state.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is exclusively focused on Windows Server, with all instructions, screenshots, and tools (such as the MARS agent) tailored for Windows environments. There are no references to Linux systems, Linux backup tools, or cross-platform parity. The workflow, agent downloads, and backup/restore steps are all Windows-specific, and Linux is not mentioned as a supported scenario or given any equivalent guidance.
Recommendations
  • If Azure Backup supports Linux system state or similar backups, add a parallel section or separate article for Linux, including equivalent steps, tools, and screenshots.
  • Explicitly state in the introduction and prerequisites that the guide is Windows-only, and provide a link to Linux backup documentation if available.
  • Where possible, mention cross-platform alternatives or clarify the scope (e.g., 'This guide is for Windows Server. For Linux, see...').
  • If Linux is not supported for system state backup with Azure Backup, clearly state this limitation to avoid confusion.
  • Ensure future documentation on backup covers both Windows and Linux scenarios, or provides clear parity in examples and tooling.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-mars-troubleshoot.md ...main/articles/backup/backup-azure-mars-troubleshoot.md
High Priority View Details →
Scanned: 2025-08-19 00:01
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 toward Windows environments. All troubleshooting steps, examples, and tool references are specific to Windows (e.g., MMC console, Internet Explorer, Task Scheduler, Registry Editor, vssadmin, PowerShell). There are no Linux equivalents or mentions, and the MARS agent is treated as a Windows-only solution. Linux users or those seeking cross-platform guidance will find no relevant instructions or parity.
Recommendations
  • Clearly state at the beginning whether the MARS agent is Windows-only, and if so, direct Linux users to the appropriate Azure Backup solutions for Linux.
  • If Linux support is available or planned, provide equivalent troubleshooting steps, examples, and tool references for Linux environments (e.g., using systemctl, journalctl, Linux file paths, and relevant package managers).
  • Where PowerShell or Windows-specific tools are referenced, add corresponding Linux shell commands or procedures if applicable.
  • Avoid assuming the use of Internet Explorer or Windows GUI tools; provide browser-agnostic and CLI-based alternatives.
  • Add a section or links for Linux backup agent troubleshooting, or clarify that Linux users should use a different agent (such as Azure VM backup or Azure Backup for Linux).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-monitor-troubleshoot.md ...n/articles/backup/backup-azure-monitor-troubleshoot.md
High Priority View Details →
Scanned: 2025-08-19 00:01
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 tools (Task Manager, Control Panel), Windows service/process names, and Windows file paths. There are no examples or instructions for Linux-based Azure Backup agents, nor are Linux equivalents for troubleshooting steps provided.
Recommendations
  • Add parallel troubleshooting instructions for Linux-based Azure Backup agents, including relevant process/service names and commands (e.g., using systemctl, ps, or journalctl).
  • Include Linux file path examples for log locations, if supported.
  • Present both Windows and Linux instructions side-by-side or clearly indicate when steps are Windows-specific.
  • Reference cross-platform tools or clarify OS applicability at the start of each troubleshooting section.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-agentless-multi-disk-crash-consistent-overview.md ...ure-vms-agentless-multi-disk-crash-consistent-overview.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows subtle Windows bias by mentioning Windows-specific tools (Volume Shadow Copy Service - VSS) before their Linux equivalents (fsfreeze), and by linking only to Windows VM Agent and snapshot extension documentation. There are no Linux-specific example links or detailed references, and Linux is only mentioned in passing (e.g., 'pre/post scripts for Linux VM backups') without further guidance or parity in documentation links.
Recommendations
  • When referencing tools for backup consistency, mention Linux (fsfreeze) before or alongside Windows (VSS), not after.
  • Provide equivalent documentation links for Linux VM Agent and snapshot extension, not just Windows.
  • Include Linux-specific examples or scenarios, such as how crash-consistent backups interact with common Linux workloads or filesystems.
  • Clarify or expand on the use of pre/post scripts for Linux, possibly linking to relevant Linux backup documentation.
  • Ensure that all instructions, notes, and references are balanced between Windows and Linux environments to improve parity.
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-08-18 00: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 providing restore examples and references that are focused exclusively on Windows VMs, especially in the encrypted VM restore scenario. Only Windows-specific links and PowerShell instructions are mentioned, with no equivalent Linux guidance or examples. There is no mention of Linux disk encryption or restore processes, nor are Linux-specific tools or commands referenced.
Recommendations
  • Include parallel examples and links for restoring encrypted Linux VMs, such as those using Azure Disk Encryption with Linux or other supported Linux encryption methods.
  • Reference Linux-specific documentation and tools (e.g., CLI, shell scripts) alongside PowerShell and Windows instructions.
  • Ensure that restore scenarios and workflows are described for both Windows and Linux VMs, with clear distinctions and parity in guidance.
  • Add links to Linux disk encryption documentation and FAQs where appropriate.
  • Review all restore scenario tables and ensure Linux is represented equally in both examples and troubleshooting guidance.
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-08-18 00: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 referencing PowerShell as the primary automation client, mentioning it before CLI and other cross-platform tools. Example workflows and automation scenarios are described using PowerShell and Azure Automation Runbooks (which are often PowerShell-based), with no explicit Linux shell (Bash) or cross-platform scripting examples. There are no Linux-specific examples or mentions of Bash scripting, and the guidance for automation is oriented toward Windows-centric tools and patterns.
Recommendations
  • Provide explicit Bash (Linux shell) examples alongside or before PowerShell examples for all automation scenarios.
  • When listing automation clients, alternate the order or explicitly state that both PowerShell and CLI are supported equally.
  • Include sample scripts and workflows using Azure CLI in Bash, especially for common tasks like configuring backups and exporting operational data.
  • Highlight cross-platform automation options (e.g., Python SDK, Terraform, Ansible) with concrete Linux-based usage examples.
  • Clarify that Azure Automation Runbooks can use Python or Bash, not just PowerShell, and provide links or examples for those.
  • Add a section or callout for Linux administrators, summarizing Linux-friendly automation approaches.
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-08-18 00:00
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 before Azure CLI and is given as a primary method for backup operations. There are no explicit Linux/Unix shell (bash) examples or references, and PowerShell is highlighted as a main automation tool, which is more common on Windows. The documentation does not provide command-line examples in either PowerShell or bash, but the ordering and emphasis suggest a preference for Windows-centric tools.
Recommendations
  • Ensure parity by providing both Azure CLI (bash) and PowerShell examples for all operations, especially in 'Next steps' and linked articles.
  • When listing command-line tools or automation methods, mention Azure CLI (bash) before or alongside PowerShell to avoid implying a Windows-first workflow.
  • Explicitly state that all operations can be performed from Linux/macOS environments using Azure CLI, and provide links or examples for those platforms.
  • If possible, include a section or callout for Linux/macOS users to clarify any differences or prerequisites.
  • Review linked articles to ensure that Linux-friendly instructions are present and not overshadowed by PowerShell/Windows-specific guidance.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-agentless-multi-disk-crash-consistent-overview.md ...ure-vms-agentless-multi-disk-crash-consistent-overview.md
High Priority View Details →
Scanned: 2025-08-18 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation references Windows-specific tools (Volume Shadow Copy Service - VSS) before mentioning the Linux equivalent (*fsfreeze*), and links to Windows-specific agent and extension documentation without providing Linux equivalents or links. There are no Linux-specific examples or links, and the language and references are Windows-first.
Recommendations
  • When mentioning backup consistency mechanisms, list Linux (*fsfreeze*) before or alongside Windows (VSS), not after.
  • Provide links to both Windows and Linux VM Agent and snapshot extension documentation, not just Windows.
  • Include Linux-specific examples or scenarios, such as how crash-consistent backup interacts with common Linux workloads.
  • Add a section or note clarifying the process for Linux VMs, including any limitations or best practices.
  • Ensure parity in documentation links and references for both operating systems throughout the page.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-restore-vms.md ...b/main/articles/backup/backup-azure-arm-restore-vms.md
High Priority View Details →
Scanned: 2025-08-18 00: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 prioritizing Windows-specific guidance and tools, providing examples and links for Windows scenarios first or exclusively, and omitting equivalent Linux-specific instructions. PowerShell and Windows-centric workflows are referenced without parallel Linux/CLI examples, and several links and guidance are Windows-only.
Recommendations
  • Provide parallel Linux examples and guidance wherever Windows/PowerShell instructions are given, especially for restore operations, network configuration, and post-restore steps.
  • Include links to Linux documentation (e.g., restoring Linux VMs, using Azure CLI/Bash for VM creation and disk attachment) alongside or before Windows links.
  • When referencing tools like PowerShell, also mention Azure CLI or Bash scripts for Linux users.
  • For post-restore steps, add Linux-specific troubleshooting (e.g., resetting SSH keys, reconfiguring cloud-init, handling Linux agents) with relevant commands and links.
  • Balance scenario tables and guidance to include both Windows and Linux VM restore scenarios, not just Windows-centric features (e.g., Hybrid Use Benefit, domain controllers, SQL VMs).
  • Ensure that all code snippets and command-line instructions have Linux/CLI equivalents, not just Windows CMD/PowerShell.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-sql-restore-cli.md ...b/main/articles/backup/backup-azure-sql-restore-cli.md
High Priority View Details →
Scanned: 2025-08-18 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently assumes SQL Server workloads running on Windows-based Azure VMs, referencing 'SQLInstance', 'mssqlserver', and using naming conventions and patterns typical of Windows SQL Server deployments. There are no explicit examples, notes, or guidance for restoring SQL Server on Linux VMs, nor any mention of Linux-specific considerations or tools. The CLI examples and resource names all reflect Windows-centric SQL Server environments, and there is no parity for Linux SQL Server users.
Recommendations
  • Add explicit guidance and examples for restoring SQL Server databases running on Linux-based Azure VMs, including any differences in CLI usage, file paths, or prerequisites.
  • Include notes or sections that clarify support for SQL Server on Linux, and highlight any differences in restore operations or limitations.
  • Provide Linux-specific example resource names, file paths (e.g., /var/opt/mssql/data), and scenarios alongside or before Windows examples.
  • Mention any Linux-specific tools or troubleshooting steps relevant to SQL Server on Linux in Azure VMs.
  • Ensure that documentation language and examples are inclusive of both Windows and Linux SQL Server deployments, or clearly state if only Windows is supported.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-introduction.md .../main/articles/backup/backup-azure-vms-introduction.md
High Priority View Details →
Scanned: 2025-08-18 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently presenting Windows-specific tools (such as VSS and PowerShell) first or exclusively, providing detailed instructions and examples for Windows (e.g., VSS integration, PowerShell restore), while Linux guidance is less detailed, generic, or requires user-supplied scripts. Linux examples are either missing or less prescriptive, and Windows tooling is referenced as the default or primary method.
Recommendations
  • Provide equally detailed, step-by-step Linux examples alongside Windows ones, especially for backup and restore operations.
  • Include sample pre/post scripts for common Linux workloads (e.g., MySQL, PostgreSQL) to parallel the VSS integration for Windows.
  • When referencing PowerShell for restore operations, also provide equivalent Azure CLI and/or Bash examples for Linux users.
  • Avoid always listing Windows tools and processes first; alternate or parallelize the order with Linux equivalents.
  • Clarify and expand on Linux-specific backup and restore best practices, including troubleshooting and automation guidance.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-troubleshoot.md .../main/articles/backup/backup-azure-vms-troubleshoot.md
High Priority View Details →
Scanned: 2025-08-18 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation displays a notable Windows bias. Many troubleshooting steps and examples focus on Windows-specific tools (such as Event Viewer, Services.msc, Registry Editor, and command prompt commands like net start/stop, vssadmin, icacls, msdtc, regedit, etc.) and PowerShell cmdlets are provided for restore operations. Windows error scenarios are described in detail, often with step-by-step instructions, while Linux equivalents are either missing, less detailed, or only briefly mentioned. In several sections, Windows procedures are presented first or exclusively, with Linux guidance appearing later or only in specific cases. Some error resolutions and examples (e.g., VSS, BitLocker, Visual C++ Redistributable) are entirely Windows-centric, with no Linux alternatives or context.
Recommendations
  • For every Windows-specific troubleshooting step (e.g., using Event Viewer, Services.msc, Registry Editor, net commands), provide equivalent Linux instructions (e.g., using journalctl, systemctl, editing configuration files, checking logs in /var/log, etc.).
  • When PowerShell or Windows command prompt examples are given, also provide Bash or shell command equivalents for Linux VMs.
  • Ensure Linux error scenarios are described with the same level of detail as Windows, including common issues with Linux agents, file systems, and backup extensions.
  • Where Windows tools (e.g., VSS, BitLocker, Visual C++ Redistributable) are referenced, clarify their Linux counterparts or note if the issue is not applicable to Linux, and provide Linux-specific troubleshooting where relevant (e.g., LVM snapshots, SELinux, disk encryption with LUKS).
  • In tables and lists, avoid always listing Windows first; alternate or group by OS, or clearly label sections as 'Windows' and 'Linux'.
  • Add Linux-specific examples for restore operations, such as using Azure CLI or Bash scripts, and reference Linux documentation links where PowerShell is mentioned.
  • Review all error code sections to ensure Linux-specific errors and their resolutions are included and not just Windows-centric issues.
GitHub Create Pull Request
← Previous Page 38 of 65 Next →