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 1151-1175 of 1604 flagged pages
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-database-from-azure-vm-blade.md
...ckup/backup-sql-server-database-from-azure-vm-blade.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-specific tools and extensions (such as AzureBackupWindowsWorkload and NT Service accounts), and by not mentioning or providing instructions for Linux-based SQL Server VMs. There are no examples or guidance for backing up SQL Server running on Linux VMs, nor is there any discussion of Linux-specific requirements or differences.
Recommendations
- Explicitly state whether the documented process supports both Windows and Linux SQL Server VMs, or clarify if it is Windows-only.
- If Linux SQL Server VMs are supported, provide parallel instructions and screenshots for Linux, including any differences in agent/extension installation, service accounts, and permissions.
- Mention Linux-specific tools, extensions, or service accounts if applicable, or provide links to Linux backup documentation.
- Add a section comparing Windows and Linux support, highlighting any limitations or differences.
- Ensure that terminology and screenshots do not assume a Windows environment unless it is a documented prerequisite.
Create Pull Request
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-on-availability-groups.md
...les/backup/backup-sql-server-on-availability-groups.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation assumes a Windows-centric environment for SQL Server Always On Availability Groups, with no mention of Linux-based SQL Server deployments. All instructions, terminology, and backup tooling (such as the workload backup extension and Recovery Services vault registration) implicitly target Windows VMs. There are no examples, notes, or guidance for Linux-based SQL Server AGs, which are supported by SQL Server and Azure. The documentation also refers to concepts and error codes typical of Windows deployments, and does not address Linux-specific considerations or tools.
Recommendations
- Explicitly state whether the guidance applies to both Windows and Linux SQL Server AGs, or clarify any limitations.
- Add sections or notes describing how to back up SQL Server AGs running on Linux VMs, including any differences in agent installation, registration, and supported features.
- Provide Linux-specific examples, such as using shell commands for agent installation, or referencing Linux file paths and system services.
- Mention any differences in error codes, troubleshooting steps, or backup/restore workflows for Linux-based AGs.
- Ensure parity in terminology and instructions so that Linux administrators can follow the documentation without ambiguity.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-azure-troubleshoot.md
...rticles/backup/backup-sql-server-azure-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All examples, file paths, and troubleshooting steps reference Windows-specific tools, directories (e.g., C:\Program Files), and services (e.g., Control Panel, Local Security Policy). The extension required is named AzureBackupWindowsWorkload, and there is no mention of Linux-based SQL Server VMs or their backup processes. PowerShell is referenced as the automation tool for re-registration, with no mention of Bash or CLI alternatives. Antivirus exclusions, service accounts, and permissions are all described in a Windows context, with no Linux equivalents or guidance.
Recommendations
- Add explicit guidance and examples for SQL Server running on Linux VMs, including Linux file paths, service management, and extension installation.
- Provide Linux-specific troubleshooting steps, such as how to check service status, configure permissions, and manage antivirus exclusions on Linux.
- Include Bash/CLI commands alongside PowerShell for automation and scripting tasks.
- Reference Linux equivalents for Windows tools (e.g., Control Panel, Local Security Policy) or note when a step is Windows-only.
- Clarify in the introduction whether the documentation applies only to Windows VMs, or expand scope to cover Linux VMs if supported.
- Where only Windows is supported, explicitly state this to avoid confusion for Linux users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix-iaas.md
...lob/main/articles/backup/backup-support-matrix-iaas.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: Windows scenarios, tools, and examples are presented before Linux equivalents, and some features (such as file/folder-level backup with the MARS agent, DPM, or MABS) are only available for Windows. PowerShell is mentioned as the primary automation tool for restore operations, with no equivalent Linux/CLI examples. Windows-specific tools and backup agents (MARS, DPM, MABS) are referenced throughout, with Linux support often noted as 'not supported' or requiring workarounds. Linux-specific guidance is limited and less detailed, and some restore and backup scenarios lack Linux parity or examples.
Recommendations
- Provide Azure CLI and Bash examples alongside PowerShell for backup and restore operations, especially in sections where PowerShell is referenced for VM creation or disk attachment.
- Present Linux and Windows scenarios in parallel tables or sections, rather than listing Windows first and Linux as an afterthought.
- Expand Linux-specific documentation, including detailed steps for file-level backup/restore, and clarify any workarounds or alternatives for Linux users.
- Where features are Windows-only (e.g., MARS agent, DPM, MABS), clearly state the lack of Linux support up front and suggest alternative approaches for Linux workloads.
- Include more Linux-focused use cases and examples, such as restoring to Linux VMs, handling LVM/RAID, and using custom scripts for app-consistent backups.
- Review all automation and scripting guidance to ensure Linux/CLI parity, not just PowerShell.
- Where possible, prioritize cross-platform/OS-agnostic features (such as agentless backups) in the documentation structure and examples.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-automation.md
...blob/main/articles/backup/backup-support-automation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation consistently lists PowerShell as the first automation method in all tables, and provides PowerShell examples for every operation, regardless of whether the workload is cross-platform or Linux-specific (e.g., SAP HANA). This prioritization of PowerShell, a Windows-centric tool, and the lack of explicit mention of Linux-native scripting (such as Bash) or Linux-specific nuances, demonstrates a Windows-first and PowerShell-heavy bias. The documentation also refers to 'PowerShell' as a primary automation tool, which is more familiar to Windows users, even though Azure CLI is cross-platform and often preferred on Linux.
Recommendations
- Alternate the order of automation methods in tables, sometimes listing Azure CLI before PowerShell, especially for Linux-centric workloads (e.g., SAP HANA, PostgreSQL).
- Explicitly mention that Azure CLI commands and examples are cross-platform and can be used on Linux, macOS, and Windows.
- Where possible, provide Bash script examples or reference Bash usage for Linux administrators, not just PowerShell.
- Add a note or section clarifying the cross-platform nature of Azure CLI and REST API, and highlight any Linux-specific considerations or best practices.
- For workloads that are primarily Linux-based (e.g., SAP HANA), consider omitting PowerShell where not supported and emphasizing CLI or REST API.
- Ensure that documentation for automation tasks does not assume familiarity with PowerShell, and provide parity in guidance for Linux users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix.md
...ocs/blob/main/articles/backup/backup-support-matrix.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a clear Windows bias. Windows-based backup methods (MARS agent, DPM, MABS) are described in detail and appear first in tables and explanations, while Linux support is often listed as 'not supported' or only as a secondary note. There are no Linux-specific examples or tools mentioned, and the documentation focuses heavily on Windows tools and backup agents. Linux support is generally limited to VM-level backup via extensions, with no direct on-premises Linux backup options provided.
Recommendations
- Provide Linux-specific backup examples and workflows where possible, especially for on-premises scenarios.
- List Linux support and options alongside Windows in all tables, not as afterthoughts or exclusions.
- Include parity in tool descriptions: if a Windows tool (like MARS agent) is mentioned, clarify Linux alternatives or explicitly state roadmap plans.
- Add practical examples or references for configuring app-consistent backups on Linux (e.g., sample custom scripts).
- Avoid always listing Windows options first; alternate or group by scenario rather than OS.
- Clarify the limitations for Linux support and, where possible, provide guidance or workarounds for Linux users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix-mars-agent.md
...in/articles/backup/backup-support-matrix-mars-agent.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation for the MARS agent is exclusively focused on Windows environments. All examples, supported operating systems, and instructions reference only Windows or Windows Server. There is no mention of Linux or other non-Windows platforms, and all tools and commands (e.g., PowerShell, MMC, DISM.exe, registry edits) are Windows-specific. The support matrix, installation instructions, and troubleshooting steps are all tailored to Windows, with no Linux equivalents or alternatives provided.
Recommendations
- Explicitly state in the introduction that the MARS agent is only available for Windows, and provide guidance or links for Linux backup alternatives (such as Azure Backup for Linux VMs or Azure Backup Server support for Linux).
- If Linux support is planned, add a section outlining current limitations and a roadmap for Linux compatibility.
- Where Windows-specific tools or commands are mentioned (e.g., PowerShell, registry edits), clarify that these are not applicable to Linux, and suggest equivalent Linux procedures if available.
- Add a comparison table or FAQ highlighting the differences in backup support and tooling between Windows and Linux environments in Azure.
- Provide links to documentation for Linux backup solutions (such as Azure VM backup for Linux or third-party agents) to help Linux users find relevant information.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-sql-database-azure-vm.md
.../main/articles/backup/restore-sql-database-azure-vm.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows-centric bias. All operational examples, file paths, and tool references (e.g., PsExec, NT AUTHORITY\SYSTEM, C:\Program Files, SSMS) are specific to Windows environments. There are no instructions, examples, or even mentions of restoring SQL Server databases on Linux-based Azure VMs, nor are Linux file paths, permissions, or tools discussed. The only restore tooling referenced is SQL Server Management Studio (SSMS), which is Windows-only, and the use of Windows command-line utilities is assumed throughout.
Recommendations
- Add explicit instructions and examples for restoring SQL Server on Linux-based Azure VMs, including relevant file paths (e.g., /var/opt/mssql/), permissions, and service management commands.
- Provide Linux equivalents for all Windows-specific tools and commands (e.g., use 'sudo' and Linux file permissions instead of NT AUTHORITY\SYSTEM and PsExec).
- Mention and provide examples for cross-platform tools such as Azure CLI and SQLCMD, and clarify how to perform restores using these tools on Linux.
- Avoid assuming the presence of SSMS; suggest alternatives like Azure Data Studio or SQLCMD for Linux users.
- When referencing file locations or commands, present both Windows and Linux variants side by side.
- Explicitly state any limitations or differences for SQL Server on Linux in Azure VMs, if applicable.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-the-mabs-server.md
...cs/blob/main/articles/backup/backup-the-mabs-server.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All operational instructions, command-line examples, and tool references (such as PowerShell, mountvol.exe, diskshadow.exe, psexec.exe, Net Share, Windows Explorer, and VSS) are specific to Windows. There are no examples, instructions, or considerations for Linux environments, nor are cross-platform alternatives mentioned. The documentation assumes the use of Windows-only tools and patterns throughout.
Recommendations
- Clearly state early in the documentation that MABS is a Windows-only product, if that is the case. If not, provide equivalent instructions and examples for Linux environments.
- Where possible, provide cross-platform alternatives or note the lack thereof. For example, if certain backup or restore operations can be performed using SQL tools available on Linux, include those examples.
- Avoid assuming the use of Windows Explorer or Windows-specific GUI tools; suggest command-line or cross-platform alternatives where applicable.
- If the use of Windows tools (e.g., mountvol.exe, diskshadow.exe, psexec.exe) is unavoidable, explain their purpose and suggest any open-source or Linux equivalents, or explicitly state that these steps are only possible on Windows.
- For SQL Server backup/restore operations, include examples using sqlcmd or other tools available on Linux, if supported.
- If Linux is not supported at all, make this explicit in the prerequisites or introduction to avoid confusion for cross-platform administrators.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/guidance-best-practices.md
...s/blob/main/articles/backup/guidance-best-practices.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows environments by referencing PowerShell and Windows-centric tools (such as MARS agent, DPM/MABS) for automation and hybrid backup scenarios, without providing equivalent Linux examples or mentioning Linux-native tools. There are no explicit Linux CLI or shell script examples, and the hybrid backup section focuses solely on Windows-based agents. Automation is often described in the context of PowerShell, and video tutorials reference PowerShell procedures, with no mention of Bash, Linux CLI, or Linux backup agents.
Recommendations
- Include Linux-specific examples and guidance alongside PowerShell, such as Bash scripts or Azure CLI commands for common backup operations.
- When discussing automation, provide parity by showing both PowerShell and Bash/CLI procedures for tasks like auto-retry of failed jobs.
- In hybrid backup sections, mention and link to documentation for Linux backup agents (such as Azure Backup Server for Linux or third-party solutions) and clarify support for Linux workloads.
- Ensure that references to tools like MARS, DPM, and MABS are balanced with Linux equivalents or alternatives, and clarify their platform support.
- Add explicit Linux workload backup scenarios, including any prerequisites, limitations, and best practices for Linux systems.
- When listing supported workloads and features, clearly indicate Linux support and provide links to relevant Linux documentation.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/install-mars-agent.md
...e-docs/blob/main/articles/backup/install-mars-agent.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is exclusively focused on Windows environments, both in its intent and technical instructions. All examples, prerequisites, and installation steps are for Windows machines only, with explicit references to Windows tools (e.g., .exe installers, Windows-specific wizards, and settings). There is no mention of Linux support, alternatives, or parity, and the MARS agent is presented as a Windows-only solution.
Recommendations
- Clearly state in the introduction and prerequisites whether the MARS agent is supported only on Windows, and if so, provide guidance or links for Linux backup solutions (such as Azure Backup for Linux VMs or other agents).
- If Linux support is available or planned, add equivalent Linux installation and configuration instructions, including command-line examples and references to Linux tools.
- Avoid using 'Windows machines' as the default or only example; instead, use more inclusive phrasing or provide parallel sections for Linux where applicable.
- Mention any limitations or differences in backup capabilities between Windows and Linux environments, and direct users to appropriate documentation for Linux scenarios.
- If the MARS agent is not available for Linux, explicitly state this and suggest alternative backup strategies for Linux workloads.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-telemetry.md
...ure-docs/blob/main/articles/backup/manage-telemetry.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references the Microsoft Azure Backup Server (MABS) console, which is a Windows-based tool, and provides only GUI-based instructions relevant to Windows environments. There are no Linux equivalents, command-line alternatives, or cross-platform considerations mentioned. The terminology and screenshots are specific to Windows, and there is no indication that Linux is supported or how to manage telemetry on non-Windows systems.
Recommendations
- Clarify whether MABS is Windows-only or if there are Linux-compatible components. If Linux is supported, provide equivalent instructions for managing telemetry settings on Linux systems.
- Include command-line examples (e.g., PowerShell for Windows, Bash for Linux) for managing telemetry settings, if applicable.
- If only Windows is supported, explicitly state this at the beginning of the documentation to set expectations for Linux users.
- If telemetry can be managed via configuration files or scripts, document the file locations and syntax for both Windows and Linux environments.
- Ensure that any future updates to the documentation consider parity between Windows and Linux instructions, where applicable.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/microsoft-azure-backup-server-protection-v3-ur1.md
...kup/microsoft-azure-backup-server-protection-v3-ur1.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias: Windows workloads and tools are described in detail and always appear first, with extensive coverage of Windows-specific features (NTFS, VSS, ReFS, deduplication, system state, bare metal, etc.). Linux is only mentioned as a VM guest, with no details on native Linux workload protection, agent installation, or file-level recovery. Windows tools and patterns (e.g., Volume Shadow Copy Service, NTFS, Windows Management Framework) are referenced exclusively, and there are no Linux command-line or configuration examples. Recovery options are consistently limited to Windows VMs/files, with Linux only supporting full-VM recovery.
Recommendations
- Provide parity by including Linux-native workload protection details, such as supported distributions, file systems, and backup/recovery scenarios beyond VM-level.
- Add Linux-specific examples for agent installation, configuration, and recovery (e.g., command-line steps for popular distributions).
- Clarify limitations and alternatives for Linux environments (e.g., file-level recovery, application-aware backup for Linux workloads).
- Mention Linux tools and patterns where relevant (e.g., LVM snapshots, ext4/xfs support, Linux backup agents).
- Reorganize documentation to present Windows and Linux support side-by-side where possible, rather than relegating Linux to a separate, minimal section.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/microsoft-azure-backup-server-protection-v3.md
.../backup/microsoft-azure-backup-server-protection-v3.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias: all workload examples, supported platforms, and backup/recovery scenarios are centered on Windows operating systems and Microsoft applications (e.g., Windows Server, SQL Server, Exchange, SharePoint, Hyper-V). Linux is only mentioned as a guest VM, with limited support (entire VM backup only, no file-level recovery), and there are no examples or details for Linux workloads, filesystems, or application backups. Windows-specific technologies (NTFS, VSS, ReFS, Windows Management Framework) are referenced exclusively, with no Linux equivalents or alternatives discussed.
Recommendations
- Add explicit support matrix rows for Linux distributions, including supported filesystems (e.g., ext4, xfs) and backup/recovery capabilities (file-level, application-aware, etc.).
- Provide examples and details for Linux workloads, such as how to back up and recover Linux VMs, files, and applications.
- Clarify any limitations or differences in Linux support (e.g., snapshot consistency, file-level recovery) and reference relevant Linux tools or technologies (e.g., LVM snapshots, rsync, etc.) where appropriate.
- If Linux support is limited by design, state this clearly and provide links to alternative Azure backup solutions for Linux workloads.
- Avoid referencing only Windows-specific tools and patterns (e.g., VSS, NTFS, Windows Management Framework) without mentioning Linux equivalents or noting their absence.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/selective-disk-backup-restore.md
.../main/articles/backup/selective-disk-backup-restore.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided extensively and in detail, and Windows-specific tools and terminology (e.g., BitLocker, C: drive, PowerShell cmdlets) are used throughout. While Linux is mentioned, Linux-specific instructions, examples, or command-line usage are minimal or absent. The documentation assumes familiarity with Windows paradigms and tools, and Linux considerations are often relegated to notes or limitations rather than being integrated into the main workflow.
Recommendations
- Add explicit Linux command-line examples (e.g., bash scripts, Linux CLI usage) alongside PowerShell, especially for disk identification and management.
- Provide Linux-specific troubleshooting steps and error messages, similar to those given for Windows/PowerShell.
- When discussing OS-specific limitations or requirements (e.g., BitLocker for Windows, dm-crypt for Linux), present them in parallel and with equal detail.
- Include Linux-first or Linux-equal examples in all sections, not just as notes or afterthoughts.
- Clarify any differences in workflow or prerequisites for Linux VMs (e.g., how to install and use lsblk/lsscsi, how to identify LUNs on Linux, how to check backup status from the Linux VM).
- Balance the order of presentation: do not always mention Windows/PowerShell first; alternate or present both together.
- Where possible, provide sample outputs or screenshots from Linux VMs in the portal/UI sections.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/save-backup-passphrase-securely-in-azure-key-vault.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/save-backup-passphrase-securely-in-azure-key-vault.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 the MARS agent, which is a Windows-only backup solution. All operational instructions and screenshots are based on the MARS console, a Windows GUI application. There are no Linux equivalents, examples, or mentions of cross-platform support. Automation references (such as Set-OBMachineSetting) are for Windows PowerShell only. The documentation does not acknowledge or provide alternatives for Linux users.
Recommendations
- Clearly state at the beginning that the MARS agent and this workflow are Windows-only, and provide links to equivalent Linux backup solutions (such as Azure Backup for Linux VMs or Azure CLI-based backup).
- If possible, include parity documentation for Linux-based backup agents and how to securely store their credentials/passphrases in Azure Key Vault.
- Where automation is discussed, mention whether similar automation is available for Linux (e.g., via shell scripts or Azure CLI) or clarify that it is not supported.
- Add a comparison table or section outlining backup options for both Windows and Linux, with links to relevant documentation for each platform.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/soft-delete-azure-file-share.md
...b/main/articles/backup/soft-delete-azure-file-share.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows environments by referencing a PowerShell script for undeleting file shares and not providing equivalent CLI or Linux-native examples. The only script-based recovery method mentioned is a PowerShell script, and there is no mention of using Azure CLI, Bash, or cross-platform tools for these operations. This may disadvantage users on Linux or macOS systems who do not use PowerShell.
Recommendations
- Provide equivalent Azure CLI and Bash script examples for undeleting file shares and other operations, alongside the existing PowerShell script.
- When referencing scripts or automation, mention both PowerShell and cross-platform (CLI/Bash) options, or clarify if a feature is only available via PowerShell.
- Ensure that links to scripts or documentation include both Windows and Linux/macOS instructions where possible.
- Explicitly state platform compatibility for any scripts or tools referenced, and avoid assuming the user is on Windows.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/soft-delete-sql-saphana-in-azure-vm.md
...articles/backup/soft-delete-sql-saphana-in-azure-vm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed instructions for the Azure Portal and Azure PowerShell, but does not mention or provide examples for Linux-native tools, Azure CLI, or shell scripting. All command-line automation is shown using PowerShell, which is traditionally a Windows-centric tool, despite its cross-platform support. There are no bash or Linux CLI examples, and the documentation does not address Linux administrators' workflows.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell operations, as Azure CLI is widely used on Linux.
- Include bash/shell scripting examples where appropriate, especially for automation scenarios.
- Explicitly mention cross-platform compatibility for PowerShell, or clarify if the steps are supported on Linux.
- Consider providing a 'Linux administrator' tab or section, outlining steps and tools familiar to Linux users.
- Reference Linux-native tools or patterns where relevant, such as scripting with cron or using SSH for remote operations.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/soft-delete-virtual-machines.md
...b/main/articles/backup/soft-delete-virtual-machines.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed instructions for managing soft delete of VM backups via the Azure Portal and Azure PowerShell, but does not mention or provide examples for Linux command-line tools (such as Azure CLI) or shell scripting. PowerShell is emphasized as the only scripting/automation interface, which is more familiar to Windows users. There are no Linux-specific examples or guidance, and the documentation does not mention parity with Linux tools.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell operations, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that all operations can be performed from Linux environments using Azure CLI or REST API, and provide links or examples.
- Where scripting is shown, offer both PowerShell and Bash/Azure CLI snippets side by side.
- Review screenshots and UI instructions to ensure they are not Windows-centric (e.g., avoid referencing right-click if not applicable on all platforms).
- Include a section or note on automation from Linux/macOS environments, referencing relevant tools and documentation.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sql-support-matrix.md
...e-docs/blob/main/articles/backup/sql-support-matrix.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily Windows-centric, explicitly stating that only Windows Server operating systems are supported and that Linux is not supported. All examples, requirements, and supported tools (e.g., PowerShell) are Windows-specific, with no mention of Linux alternatives or parity. The documentation does not provide any Linux commands, tools, or guidance, and the feature set is described solely in the context of Windows environments.
Recommendations
- Clearly state early in the document that Linux is not supported, and provide a link to any roadmap or alternatives for Linux users if available.
- If partial Linux support is planned or available in preview, mention it and provide relevant instructions or limitations.
- When referencing tools (e.g., PowerShell), note the absence of Linux/CLI support and suggest workarounds or alternatives where possible.
- Include a comparison table or section outlining feature parity (or lack thereof) between Windows and Linux for Azure SQL Server Backup.
- If Linux support is not planned, suggest alternative backup strategies for SQL Server on Linux in Azure VMs, or link to relevant documentation.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/transport-layer-security.md
.../blob/main/articles/backup/transport-layer-security.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows environments, providing only Windows-specific instructions (such as registry edits and KB articles) and omitting any guidance for Linux systems. All configuration steps, troubleshooting, and examples are tailored exclusively to Windows, with no mention of Linux equivalents or cross-platform considerations.
Recommendations
- Add a section describing how to ensure TLS 1.2 is enabled and enforced on Linux-based systems, including relevant configuration files (e.g., OpenSSL, GnuTLS, or system-wide crypto policies).
- Provide Linux command-line examples (such as using openssl or update-alternatives) to verify and configure TLS support.
- Include troubleshooting steps and error messages relevant to Linux environments.
- Reference Linux-specific documentation or Microsoft Learn pages related to Azure Backup on Linux.
- Clarify in the introduction or prerequisites if the guidance is only applicable to Windows, or explicitly state cross-platform support and differences.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/troubleshoot-azure-files.md
.../blob/main/articles/backup/troubleshoot-azure-files.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows/Powershell bias by providing scripts and automation examples exclusively in Powershell, referencing scripts with 'powershell' in their filenames, and not offering equivalent CLI or Bash scripts for Linux/macOS users. There are no Linux-specific instructions or examples, and automation guidance is Windows-centric.
Recommendations
- Provide equivalent Azure CLI or Bash scripts for all Powershell script references, ensuring Linux/macOS users have parity.
- When linking to scripts (e.g., for finding Recovery Services vaults or undeleting file shares), offer both Powershell and Azure CLI/Bash alternatives, or clearly indicate cross-platform options.
- Avoid using only Windows-centric terminology (such as 'Powershell script') in main troubleshooting steps; instead, refer to 'automation script' and specify both Windows and Linux options.
- Include explicit Linux/macOS troubleshooting steps or notes where relevant, especially for command-line or scripting tasks.
- Review all automation and scripting guidance to ensure cross-platform compatibility and representation.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-postgresql-backup.md
...lob/main/articles/backup/tutorial-postgresql-backup.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows environments by primarily referencing PowerShell scripts for privilege assignment and not providing equivalent Linux/Unix command-line (e.g., Bash, psql) examples. The mention of PowerShell occurs first and most prominently, with alternatives like PG admin or PSQL tool only briefly mentioned and without concrete examples. No Linux-specific instructions or screenshots are provided, and the overall workflow assumes a Windows-centric administrative approach.
Recommendations
- Provide explicit Linux/Unix command-line examples (e.g., using Bash and psql) for all steps where PowerShell is referenced, especially for granting privileges to database users.
- When mentioning PowerShell, always mention Linux/Unix alternatives in parallel, not as an afterthought.
- Include screenshots or terminal output from Linux environments where applicable.
- Clarify that all steps can be performed from both Windows and Linux environments, and provide parity in instructions.
- Consider providing downloadable scripts for both PowerShell and Bash/psql.
- Review all references to administrative tools to ensure Linux-native tools are given equal prominence.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-restore-disk.md
...ocs/blob/main/articles/backup/tutorial-restore-disk.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page is generally cross-platform and CLI-focused, but it exhibits subtle Windows bias. It references PowerShell as an alternative in the introduction and links to a PowerShell-specific guide before mentioning Linux alternatives. Some terminology and linked resources (such as zone-pinned VM documentation) default to Windows examples or documentation. There are no explicit Linux command examples, and the only mention of Linux is in the context of prerequisites, not in the main workflow or examples.
Recommendations
- Provide explicit Linux/Bash shell examples alongside or before PowerShell references, especially in introductory sections.
- When referencing alternative tooling (such as PowerShell), also provide links to Linux-specific guides or clarify that the CLI commands are cross-platform.
- Ensure that all linked documentation (e.g., for availability zones, VM creation) includes both Windows and Linux examples, or links to both.
- Where possible, use neutral terminology (e.g., 'VM' instead of 'Windows VM') and avoid defaulting to Windows-centric documentation.
- Add a brief section or callout confirming that all CLI commands work identically on Linux, macOS, and Windows, and provide troubleshooting tips for common Linux shell issues (such as line continuation differences).
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/upgrade-mars-agent.md
...e-docs/blob/main/articles/backup/upgrade-mars-agent.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes upgrading the Microsoft Azure Recovery Services (MARS) agent in a Windows environment. All instructions, screenshots, and tool references (e.g., Remote Desktop, DPM Console) are Windows-specific. There are no examples, instructions, or even mentions of Linux systems or command-line alternatives. The documentation assumes the use of Windows tools and patterns throughout.
Recommendations
- Clarify early in the documentation that the MARS agent is only supported on Windows, if that is the case. If Linux is supported, provide equivalent instructions and examples for Linux environments.
- If the agent is Windows-only, explicitly state this in the introduction to avoid confusion for Linux administrators.
- If cross-platform support is planned or available, include Linux installation and upgrade instructions, using Linux-native tools (e.g., SSH, shell commands) and screenshots.
- Where possible, provide PowerShell and command-line alternatives to GUI steps, which can help both Windows Server Core and potential cross-platform scenarios.
- Add a section addressing common questions about non-Windows environments, clarifying support boundaries.