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 1126-1150 of 1604 flagged pages
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-enhanced-policy.md
...in/articles/backup/backup-azure-vms-enhanced-policy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples before CLI examples, using Windows-specific tools and patterns (such as PowerShell cmdlets and Windows time zone handling), and offering more comprehensive step-by-step guidance for PowerShell users. Linux-specific considerations, shell examples, or parity in depth of CLI instructions are missing.
Recommendations
- Provide equivalent Bash (Linux shell) examples alongside PowerShell for all command-line operations, especially for scripting and automation scenarios.
- Ensure CLI (az) examples are as detailed as PowerShell, including parameter explanations and sample JSON payloads for policy creation.
- Include notes or sections addressing any OS-specific prerequisites or differences, such as file path formats, environment variables, or scheduling nuances.
- If screenshots or UI steps are OS-agnostic, clarify this; otherwise, provide Linux desktop screenshots where appropriate.
- Explicitly mention that both Windows and Linux VMs are supported, and highlight any differences in backup behavior or requirements.
- Add troubleshooting tips or links specific to Linux VM backup scenarios.
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 →
Detected Bias Types
Missing Linux Example
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by only providing individual file restore instructions for Windows Server VMs, omitting Linux VM scenarios. It references Windows-specific features (e.g., registry keys for configuration) and does not mention or provide parity for Linux-based VMs or tools. The workflow and terminology are tailored to Windows environments, with no guidance for Linux users.
Recommendations
- Add explicit instructions or notes for restoring individual files from Linux VMs, or clarify if this is unsupported.
- If Linux file-level restore is not supported, state this limitation clearly and provide alternative guidance or workarounds.
- Include examples or screenshots involving Linux VMs where possible, or at least acknowledge their usage and limitations.
- When referencing configuration changes (such as registry keys), provide equivalent steps for Linux environments if applicable, or note their absence.
- Ensure that recovery workflows and terminology are inclusive of both Windows and Linux VM scenarios.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias in several areas: Windows-specific tools (VSS) and workflows are described in greater detail and are mentioned before Linux equivalents. PowerShell is referenced for restore operations, but no CLI or Linux-native automation examples are provided. Linux backup consistency relies on custom scripting, but no example scripts or detailed guidance are included, unlike the explicit Windows VSS integration. Overall, Linux users receive less actionable guidance and fewer concrete examples.
Recommendations
- Provide parallel Linux CLI and automation examples wherever PowerShell is referenced (e.g., for restoring VMs with managed disks).
- Include example pre/post scripts for common Linux workloads to help users achieve application-consistent backups.
- Mention Linux tools (e.g., fsfreeze, LVM snapshots) explicitly and describe their role in the backup process, similar to how VSS is described for Windows.
- Ensure that Linux guidance is as detailed and actionable as Windows guidance, including troubleshooting steps and best practices.
- When listing options or processes, present Windows and Linux approaches side by side, rather than always listing Windows first.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a noticeable Windows bias. Troubleshooting steps and error resolutions frequently reference Windows-specific tools (e.g., Services.msc, Event Viewer, regedit, command prompt, VSS, BitLocker, registry edits, icacls, MSIEXEC), and many examples or commands are provided only for Windows. PowerShell and Windows command-line instructions are given for several operations, while equivalent Linux commands or procedures are often missing or only briefly mentioned. In several sections, Windows solutions are described in detail before Linux alternatives, and some error resolutions lack Linux-specific guidance altogether.
Recommendations
- For every Windows-specific troubleshooting step (e.g., using Services.msc, Event Viewer, registry edits), provide equivalent Linux instructions (e.g., systemctl/service commands, journalctl/syslog, relevant config files).
- Where PowerShell or Windows command prompt commands are given, include corresponding Bash or shell commands for Linux VMs.
- When referencing Windows tools (e.g., VSS, BitLocker, MSIEXEC), clarify their Linux equivalents or note if the issue is Windows-only.
- Ensure Linux examples are present and as detailed as Windows examples, especially in error troubleshooting sections.
- When listing steps for both OSes, present them in parallel or clearly separated sections, rather than Windows-first.
- Add more Linux-focused troubleshooting scenarios (e.g., SELinux/AppArmor, systemd service management, disk mounting issues) where relevant.
- Review all error codes and ensure Linux-specific guidance is included where applicable, not just for a few select errors.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-add-storage.md
...s/blob/main/articles/backup/backup-mabs-add-storage.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily Windows-centric, with all instructions, screenshots, and tooling (Server Manager, PowerShell cmdlets, ReFS, Windows Server versions) focused exclusively on Windows environments. There are no Linux examples, alternatives, or mentions of cross-platform support, and Windows-specific tools and patterns are presented as the default and only option.
Recommendations
- Clearly state early in the documentation whether Azure Backup Server and Modern Backup Storage are Windows-only, or if there is any Linux support or roadmap.
- If Linux support exists or is planned, provide equivalent Linux instructions, examples, and screenshots (e.g., using Linux file systems, CLI tools, or relevant management consoles).
- If the product is Windows-only, explicitly mention this limitation at the top of the page to set user expectations.
- Where PowerShell is used, note if there are any cross-platform PowerShell Core options or REST APIs that could be used from Linux.
- Consider adding a comparison table or FAQ about platform support to help users quickly understand OS compatibility.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-install-azure-stack.md
...ain/articles/backup/backup-mabs-install-azure-stack.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. It exclusively references Windows Server as the supported OS, uses Windows-specific paths (C:\, D:\), and only provides instructions and screenshots for Windows tools and interfaces. There are no Linux equivalents or examples, and PowerShell is the only command-line tool mentioned. The installation process, prerequisites, and troubleshooting are all described solely for Windows, with no mention of Linux support or alternatives.
Recommendations
- Clarify early in the documentation whether Azure Backup Server supports only Windows or if Linux is also supported. If Linux is not supported, state this explicitly.
- If Linux support exists or is planned, provide parallel instructions, examples, and screenshots for Linux environments, including shell commands and Linux filesystem paths.
- Include Linux-based prerequisites and installation steps, such as required packages, domain joining alternatives, and storage configuration.
- Offer troubleshooting steps and command-line tools relevant to Linux (e.g., Bash scripts, systemd services) if applicable.
- Balance the order of presentation so that, where both platforms are supported, Linux and Windows instructions are given equal prominence.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-azure-encrypted-virtual-machines.md
...les/backup/restore-azure-encrypted-virtual-machines.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (PowerShell) for VM creation from restored disks, linking to Windows OS disk swap documentation, and providing more detailed guidance for Windows scenarios. Linux-specific instructions are minimal and appear after Windows content, with Linux restore steps condensed to a single section and lacking concrete examples or commands.
Recommendations
- Provide equivalent Linux CLI (az CLI, Bash) examples for restoring VMs from disks, alongside or before PowerShell examples.
- Include links to Linux OS disk swap documentation, not just Windows.
- Expand the 'Restore an encrypted Linux VM' section with step-by-step instructions and command-line examples (e.g., using az CLI or ARM templates).
- Ensure that Linux and Windows procedures are presented in parallel, with equal detail and visibility.
- Avoid referencing Windows tools (like PowerShell) as the only automation method; always mention cross-platform alternatives.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-during-vm-creation.md
...blob/main/articles/backup/backup-during-vm-creation.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows resources and examples. The 'Deploy a protected VM using a Resource Manager template' section links only to a Windows VM template, with no Linux equivalent provided. Additionally, automation guidance references PowerShell without mentioning CLI or Bash alternatives. While both Windows and Linux quick-create links are present, Windows is listed first, and Linux-specific automation or template examples are missing.
Recommendations
- Provide parallel examples and links for Linux VMs, such as a Resource Manager template for deploying and backing up a Linux VM.
- Include automation instructions using Azure CLI or Bash scripts alongside PowerShell, ensuring Linux administrators have clear guidance.
- When referencing quick-create guides, alternate the order or present Windows and Linux equally to avoid implicit prioritization.
- Explicitly mention that all backup features and steps apply equally to Linux VMs, or note any differences.
- Audit screenshots and UI walkthroughs to ensure they are not Windows-centric, or provide Linux-relevant visuals where appropriate.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-instant-restore-capability.md
...n/articles/backup/backup-instant-restore-capability.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation provides a PowerShell example for configuring snapshot retention but does not include equivalent instructions or examples for Linux users (e.g., using Azure CLI or REST API). The only command-line automation shown is via PowerShell, which is primarily a Windows tool. There is no mention of Linux-specific tools or parity in scripting approaches, and the PowerShell section appears before any mention of cross-platform methods.
Recommendations
- Add equivalent Azure CLI examples for configuring snapshot retention, as Azure CLI is cross-platform and widely used on Linux.
- Include REST API instructions or examples for users who may automate backup configuration outside of PowerShell or the Azure portal.
- Explicitly mention that PowerShell is available on Linux and macOS, or clarify when examples are cross-platform.
- Ensure that all automation and scripting instructions are presented in a platform-neutral way, or provide both Windows (PowerShell) and Linux (Azure CLI/bash) examples side by side.
- Consider adding a section or note for Linux administrators highlighting supported tools and recommended workflows.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-files-applications-azure-stack.md
...s/backup/backup-mabs-files-applications-azure-stack.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Powershell Heavy
Windows First
Summary
The documentation exclusively describes backup and recovery procedures using Microsoft Azure Backup Server, which is a Windows-based tool. All instructions, screenshots, and workflows are based on the Azure Backup Server console, with no mention of Linux-based alternatives, command-line options, or cross-platform tools. There are no examples or guidance for Linux VMs or file systems, nor any reference to Linux-native backup tools or scripting. The documentation assumes a Windows-centric environment throughout.
Recommendations
- Include explicit guidance for backing up and recovering files from Linux-based Azure Stack VMs, such as using Azure Backup agent for Linux or native Linux backup tools.
- Provide command-line examples (e.g., Bash scripts, az CLI commands) for Linux environments alongside or in place of GUI-based, Windows-only workflows.
- Mention any limitations or differences when protecting Linux workloads, and link to relevant Linux backup documentation.
- Add screenshots or walkthroughs for Linux backup scenarios, if supported.
- Clarify in the introduction that the described process is Windows-centric, and provide a section or links for Linux users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-protection-matrix.md
.../main/articles/backup/backup-mabs-protection-matrix.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation exhibits a strong Windows bias. All detailed examples, supported workloads, and recovery scenarios are focused on Windows operating systems and applications (e.g., Windows Server, SQL Server, Exchange, SharePoint). Linux is only mentioned as a guest OS within Windows/Hyper-V/VMware environments, with no native Linux installation or agent support described. Recovery options for Linux are limited to entire VM restores, while Windows supports item-level recovery. Windows-specific tools and patterns (e.g., NTFS, VSS, Control Panel, Visual C++ redistributable) are referenced throughout, with no Linux equivalents or alternatives provided.
Recommendations
- Provide parity in documentation by including Linux-native backup and recovery scenarios, not just Linux as a VM guest.
- Offer item-level recovery options or clearly state limitations for Linux workloads, and suggest workarounds if possible.
- Include Linux-specific tools, filesystems (e.g., ext4, xfs), and backup agent installation instructions where applicable.
- List Linux examples and scenarios alongside Windows in all relevant tables and sections, not as an afterthought.
- Reference Linux management patterns (e.g., systemd, cron, shell commands) where Windows tools (e.g., Control Panel, VSS) are mentioned.
- Clarify any limitations or roadmap for improved Linux support in MABS, so Linux users can plan accordingly.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-sharepoint-azure-stack.md
.../articles/backup/backup-mabs-sharepoint-azure-stack.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. All instructions, tools, and examples assume a Windows Server context, with exclusive references to Windows-specific tools (e.g., CMD, Registry Editor, NT AUTHORITY\SYSTEM, Windows file paths, and Windows services). There are no Linux equivalents, nor is there any mention of Linux-based SharePoint deployments or Azure Backup Server support for Linux. The documentation does not address cross-platform scenarios or provide parity for Linux administrators.
Recommendations
- Explicitly state whether Microsoft Azure Backup Server (MABS) and SharePoint farm protection are supported or unsupported on Linux. If unsupported, clarify this early in the documentation.
- If any Linux-based scenarios are possible (e.g., for other workloads or future support), provide parallel instructions, examples, and tool references for Linux environments.
- Where possible, use platform-agnostic language and clarify when steps are Windows-specific.
- Add a section or note addressing Linux users, either to direct them to alternative solutions or to explain current limitations.
- If MABS is Windows-only, consider linking to Azure-native backup solutions or third-party tools that support Linux workloads.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-system-state-and-bmr.md
...in/articles/backup/backup-mabs-system-state-and-bmr.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All examples, workflows, and tools referenced are specific to Windows Server (e.g., Windows Server Backup, WinRE, PowerShell cmdlets, Windows file paths). There is no mention of Linux or cross-platform support, nor are any Linux equivalents or examples provided. The documentation assumes the reader is operating in a Windows-only environment.
Recommendations
- Clearly state early in the documentation whether Azure Backup Server supports Linux system state or bare-metal recovery, and if not, provide links to relevant Linux backup documentation.
- If Linux is supported, add equivalent Linux workflows, examples, and tool references (e.g., using rsync, tar, or Linux-native backup agents).
- Provide parity in command-line examples, showing both PowerShell/Windows and Bash/Linux commands where applicable.
- Reference Linux file paths and configuration files alongside Windows paths.
- If certain features are Windows-only, explicitly call this out in the prerequisites and limitations section.
- Consider including a comparison table of supported features for Windows and Linux to set clear expectations.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-managed-disks-cli.md
.../blob/main/articles/backup/backup-managed-disks-cli.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: variable assignment in CLI examples uses PowerShell syntax (e.g., $DiskId = ...), which is not portable to Linux/macOS shells; references to PowerShell and Windows tools appear in related content and permissions assignment sections; and there is a lack of explicit Linux/bash shell examples or guidance, which may confuse non-Windows users.
Recommendations
- Provide all CLI variable assignment examples in both PowerShell and bash syntax, or use bash syntax by default for cross-platform compatibility (e.g., DiskId="..." instead of $DiskId = ...).
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and clarify any shell-specific syntax.
- Include Linux/bash-specific instructions or notes wherever PowerShell syntax or Windows tools are mentioned.
- In 'Next steps' and 'Related content', ensure parity by linking to Linux/bash-based guides (e.g., 'Restore Managed Disk using Azure CLI on Linux/macOS').
- Avoid using Windows/PowerShell variable assignment as the only example; if both are shown, present bash first or side-by-side.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-sql-azure-stack.md
...ob/main/articles/backup/backup-mabs-sql-azure-stack.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows environments, specifically referencing Microsoft Azure Backup Server (MABS), which is a Windows-only tool. All instructions, screenshots, and terminology are based on Windows UI patterns and tools, with no mention of Linux equivalents or cross-platform alternatives. There are no examples or guidance for Linux-based SQL Server deployments or backup workflows.
Recommendations
- Explicitly state that MABS is a Windows-only solution and clarify support limitations for Linux-based SQL Server instances.
- Provide guidance or references for backing up SQL Server on Linux (if supported), including alternative tools or Azure-native backup options.
- Include examples or links for command-line/scripted backup and recovery workflows that could be run on Linux (e.g., using az CLI, REST API, or other cross-platform tools).
- If Linux is not supported, add a clear note at the top of the page to inform users and suggest alternative backup strategies for Linux SQL Server deployments.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-whats-new-mabs.md
...lob/main/articles/backup/backup-mabs-whats-new-mabs.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation for Microsoft Azure Backup Server (MABS) consistently prioritizes Windows environments, referencing Windows Server and Windows-specific features and tools throughout. There is a lack of Linux-specific examples, instructions, or parity in feature descriptions. Windows tools (e.g., registry keys, PowerShell cmdlets, ReFS, Hyper-V) are mentioned exclusively, and Linux workloads or backup scenarios are not addressed. The documentation assumes a Windows-centric deployment and omits guidance for Linux-based workloads or administrators.
Recommendations
- Add explicit sections or notes about Linux workload support, if available, including supported distributions and limitations.
- Provide Linux-specific examples for backup, restore, and agent installation, including command-line instructions for common distributions.
- Mention Linux equivalents when discussing Windows tools (e.g., registry keys vs. configuration files, PowerShell vs. shell scripts).
- Clarify whether features such as item-level recovery, parallel backups, and immutable vaults are available for Linux workloads, and provide usage instructions if so.
- Include a support matrix that clearly lists both Windows and Linux workloads, with feature parity and differences highlighted.
- If Linux is not supported, explicitly state this early in the documentation to set expectations for cross-platform users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-managed-disks.md
...docs/blob/main/articles/backup/backup-managed-disks.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation primarily focuses on the Azure portal workflow and, where automation is mentioned, references PowerShell before CLI. There are no explicit Linux or cross-platform command-line examples within the main content, and scripting guidance is biased toward PowerShell with CLI as a secondary mention. No Linux-specific tools, shell scripts, or guidance are provided, and the 'Next steps' section lists PowerShell before CLI. This ordering and lack of Linux-first or parity examples indicate a subtle Windows bias.
Recommendations
- When referencing automation or scripting, present Azure CLI examples alongside or before PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that both PowerShell and CLI are supported, and provide equal visibility to both in the main workflow steps, not just as links.
- Include example CLI commands inline for key operations (e.g., configuring backup, assigning roles) to improve accessibility for Linux users.
- If scripts are referenced, ensure both PowerShell and Bash (or shell) script templates are available and linked.
- In the 'Next steps' and similar lists, alternate or randomize the order of PowerShell and CLI to avoid reinforcing a Windows-first perception.
- Consider a short section or callout for Linux users, clarifying that all operations can be performed from Linux using the Azure CLI.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-overview.md
...zure-docs/blob/main/articles/backup/backup-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page for Azure Backup demonstrates a Windows bias by primarily referencing Windows-centric tools (such as the Microsoft Azure Recovery Services (MARS) agent, DPM, and Azure Backup Server), mentioning Windows/Hyper-V before Linux/VMware, and not providing explicit Linux or cross-platform examples for on-premises backup scenarios. Linux-specific backup agents or instructions are not mentioned for on-premises workloads, and the examples and terminology are more familiar to Windows administrators.
Recommendations
- Include explicit references to Linux backup tools or agents (if supported), and provide guidance for backing up Linux-based on-premises servers.
- Present examples for both Windows and Linux platforms when describing backup scenarios, especially for on-premises workloads.
- Avoid listing Windows/Hyper-V before Linux/VMware unless there is a technical reason; strive for parity or alternate the order.
- Clarify whether the MARS agent or other backup agents support Linux, and if not, suggest alternatives for Linux environments.
- Add links or references to documentation that addresses Linux backup scenarios, including command-line or scripting examples relevant to Linux users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-sql-backup.md
...-docs/blob/main/articles/backup/tutorial-sql-backup.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation assumes SQL Server is running on Windows VMs and only describes the use of Windows-specific extensions (AzureBackupWindowsWorkload, NT Service accounts, SqlIaaSExtension). There are no instructions or examples for SQL Server running on Linux VMs, nor any mention of Linux-specific considerations or tools. The documentation is Windows-centric both in technical details and in the absence of Linux parity.
Recommendations
- Explicitly state whether the tutorial applies only to Windows-based SQL Server VMs or provide equivalent instructions for SQL Server on Linux VMs.
- Include details about backup support, required extensions, and service accounts for SQL Server on Linux VMs (if supported).
- Add Linux-specific examples, screenshots, and troubleshooting steps where applicable.
- Clarify any differences in agent/extension installation, permissions, and backup/restore workflows for Linux-based SQL Server VMs.
- If Linux is not supported, clearly state this at the top of the documentation to set expectations.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is consistently mentioned before Azure CLI and REST API as a non-portal client for monitoring and automation. The examples and references to custom dashboards and automation scripts prioritize PowerShell, which is traditionally associated with Windows environments. Additionally, several workload types and tools (such as DPM and Azure Backup Server) are Windows-centric, and there is no explicit mention or example of Linux-specific backup agents or Linux-oriented monitoring workflows.
Recommendations
- Ensure that CLI examples are presented alongside or before PowerShell examples, especially in sections discussing automation or custom dashboards.
- Include explicit references to Linux-based backup scenarios, such as using the Azure CLI on Linux or monitoring Linux VMs.
- Where possible, provide Linux shell (bash) script examples in addition to PowerShell.
- Clarify that Azure CLI and REST API are fully cross-platform and provide links to Linux-specific guidance.
- Mention Linux-compatible backup agents or tools if available, and ensure parity in documentation for both Windows and Linux workloads.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-rbac-rs-vault.md
...docs/blob/main/articles/backup/backup-rbac-rs-vault.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: it references Windows-specific backup agents and tools (such as SCDPM and Azure Backup Server), mentions on-premises Windows Server registration explicitly, and highlights PowerShell as a primary automation interface. There is little to no mention of Linux equivalents, Linux-specific backup scenarios, or cross-platform parity in examples or tool references. Linux/Unix systems and their management tools are not addressed, and the documentation does not provide guidance or examples for Linux users.
Recommendations
- Include explicit references to Linux-based backup scenarios, such as registering on-premises Linux servers or using Linux backup agents if supported.
- Provide examples and guidance for managing Azure Backup and RBAC using Bash/Azure CLI on Linux, not just PowerShell.
- Mention Linux/Unix systems alongside Windows when discussing on-premises registration and supported platforms.
- Clarify whether features and role requirements apply equally to Linux workloads, and add notes or tables for any differences.
- Where PowerShell is referenced, also provide equivalent Azure CLI or Bash commands, and link to cross-platform tooling documentation.
- Add a section or FAQ addressing common Linux backup management questions in Azure.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-azure-sql-vm-rest-api.md
.../main/articles/backup/restore-azure-sql-vm-rest-api.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments, specifically SQL Server on Windows VMs. All directory paths in examples use Windows-style paths (e.g., C:\SQLfiles\Default.ldf), and there is no mention of Linux-based SQL Server VMs or examples relevant to Linux. The documentation assumes the use of Windows containers and file systems, and does not provide parity or guidance for Linux users.
Recommendations
- Include explicit guidance and examples for restoring SQL Server databases on Linux-based Azure VMs, if supported.
- When showing directory paths or file system operations, provide both Windows and Linux path examples (e.g., C:\SQLfiles\Default.ldf and /var/opt/mssql/data/Default.ldf).
- Clarify in the prerequisites and introduction whether the procedure applies only to Windows-based SQL Server VMs or if Linux is supported.
- If Linux is not supported, state this clearly at the beginning of the documentation.
- If Linux is supported, add Linux-specific REST API request body examples, including appropriate file paths and container naming conventions.
- Mention any differences in restore behavior or requirements between Windows and Linux SQL Server VMs.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-postgresql-cli.md
...ocs/blob/main/articles/backup/backup-postgresql-cli.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways. Although the main focus is on Azure CLI (which is cross-platform), the explanations and object model discussions repeatedly reference PowerShell as the default or primary method for managing backup policies. File path examples (e.g., .\OSSPolicy.json) use Windows-style backslashes, and there are no explicit Linux or macOS command-line examples or file path conventions. The documentation describes PowerShell object manipulation in detail, but only briefly mentions that Azure CLI users must use files, without providing Linux-specific guidance or examples. There is also a tendency to mention PowerShell and Windows-centric approaches before or instead of Linux equivalents.
Recommendations
- Provide explicit Linux/macOS shell examples alongside or instead of Windows/PowerShell examples, especially for file paths (e.g., use ./OSSPolicy.json instead of .\OSSPolicy.json).
- When discussing object manipulation, offer parity in explanation for both PowerShell (objects) and CLI (JSON/files), including sample jq or sed commands for Linux users.
- Avoid referring to PowerShell as the 'default' or primary method; instead, present both PowerShell and CLI approaches neutrally.
- Include notes or callouts for Linux/macOS users regarding file path conventions, shell differences, and any required environment setup.
- Where possible, use cross-platform syntax in examples, or provide both Windows and Linux variants.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. When mentioning command-line options for moving Backup vaults, it lists PowerShell before CLI, and does not provide explicit Linux/bash examples or references. The only command-line tool mentioned by name is PowerShell, with no Linux-specific scripting or shell guidance. All procedural examples use the Azure portal UI, which is cross-platform, but the lack of parity in command-line references and examples may disadvantage Linux users.
Recommendations
- When referencing command-line tools, mention Azure CLI before or alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux.
- Provide explicit bash/Azure CLI command examples for key operations (e.g., moving Backup vaults), not just PowerShell.
- Where scripts or automation are referenced, clarify that both PowerShell and bash/CLI scripts may need updating after resource moves.
- Consider adding a section or callout for Linux users, highlighting any differences or providing Linux-specific guidance.
- Ensure that all command-line documentation is balanced, with equal prominence and detail for both Windows (PowerShell) and Linux (CLI/bash) users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-database-azure-vms.md
...rticles/backup/backup-sql-server-database-azure-vms.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a Windows-centric bias. It assumes SQL Server VMs are Windows-based, references Windows-specific tools and extensions (e.g., AzureBackupWindowsWorkload, NT Service accounts), and provides connectivity troubleshooting scripts only for Windows. There are no examples or guidance for Linux-based SQL Server VMs, nor mention of Linux-specific requirements or differences.
Recommendations
- Explicitly state whether the instructions apply to both Windows and Linux SQL Server VMs, or clarify if only Windows is supported.
- If Linux-based SQL Server on Azure VMs is supported, add parallel sections or notes for Linux, including prerequisites (e.g., Linux VM Agent, .NET requirements if any), service account equivalents, and extension installation.
- Provide Linux-specific troubleshooting scripts or guidance, similar to the Windows connectivity test scripts.
- Reference Linux documentation for VM extensions and agent installation where appropriate.
- When mentioning tools or extensions (e.g., AzureBackupWindowsWorkload, NT Service\AzureWLBackupPluginSvc), clarify Linux equivalents or note if not applicable.
- Include CLI or shell-based examples for Linux where PowerShell or Windows UI steps are described.
- Review and update all screenshots and step-by-step instructions to indicate any OS-specific differences.