Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 776-800 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/quick-backup-vm-bicep-file.md
...ob/main//articles/backup/quick-backup-vm-bicep-file.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All deployment and cleanup examples are provided exclusively in PowerShell, with no Azure CLI (bash) or Linux-native shell examples. The Bicep template provisions only Windows VMs, with no mention of Linux VM options or parameters. References to tools and workflows (such as 'right-click to paste' and PowerShell cmdlets) are Windows-centric, and there is no guidance for users on Linux or macOS platforms.
Recommendations
- Add Azure CLI (bash) examples for deploying the Bicep template, including equivalent commands for parameter input and resource group deployment.
- Provide a Linux VM option in the Bicep template, such as an additional parameter for selecting between Windows and Linux images, and document the allowed values.
- Include cleanup instructions using Azure CLI commands, not just PowerShell.
- Mention cross-platform compatibility of Azure Cloud Shell, and provide instructions for both bash and PowerShell environments.
- Update references to input methods (e.g., pasting in Cloud Shell) to be platform-neutral.
- Link to Linux-specific quickstarts or tutorials for VM backup with Bicep where available.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/quick-kubernetes-backup-arm.md
...b/main//articles/backup/quick-kubernetes-backup-arm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell deployment instructions, with no equivalent Azure CLI, Bash, or Linux-native example. PowerShell is both mentioned and demonstrated as the primary automation tool, and the deployment workflow assumes a Windows/PowerShell environment. Linux or cross-platform users are not given direct guidance for template deployment.
Recommendations
- Add an Azure CLI example for deploying the ARM template, using Bash syntax suitable for Linux/macOS users.
- Explicitly mention that both PowerShell and CLI can be used, and provide parallel instructions for each.
- Where possible, use neutral language (e.g., 'shell window' instead of 'PowerShell window') and clarify that the steps are cross-platform.
- Include links to official documentation for both PowerShell and CLI deployment methods.
- Review other sections (such as prerequisites) to ensure Linux tools and workflows are equally represented.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/bastion-create-host-powershell.md
...in//articles/bastion/bastion-create-host-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page is heavily focused on PowerShell, with all deployment instructions and code samples provided exclusively in Azure PowerShell. There are no examples or guidance for Bash, Azure CLI, or Linux-native workflows within the main content, and the only mention of Azure CLI is a brief link in a list of alternative methods. Additionally, the VM creation quickstart links prioritize Windows VM creation articles, with no direct reference to Linux VM creation guides.
Recommendations
- Add parallel Azure CLI (bash) examples for each PowerShell deployment step, either inline or in clearly marked tabs.
- Include explicit references and links to Linux VM creation quickstarts alongside the Windows VM quickstart links.
- Ensure that any prerequisites or setup instructions are platform-agnostic or provide both Windows and Linux alternatives.
- Consider restructuring the article or adding tabs to allow users to choose their preferred platform (PowerShell or CLI) from the start.
- Review terminology to avoid implying PowerShell is the default or only supported method for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/quickstart-developer.md
...cs/blob/main//articles/bastion/quickstart-developer.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias. Windows is mentioned first in several contexts (e.g., VM creation, port requirements, keyboard shortcuts), and Windows-specific tools and behaviors (such as CTRL+ALT+END for Windows VMs) are described in detail, while Linux equivalents are only briefly mentioned or omitted. There are no explicit Linux command-line or desktop examples, and the only Linux reference is to port 22 and a link to a Linux VM quickstart.
Recommendations
- Provide Linux-specific examples and screenshots alongside Windows ones, such as what a Linux desktop connection looks like via Bastion.
- Include Linux keyboard shortcut guidance for common remote desktop actions, similar to the Windows shortcut explanations.
- Mention Linux tools or behaviors (e.g., X11 forwarding, clipboard integration in Linux desktop environments) where relevant.
- Ensure that Linux is mentioned equally or before Windows in lists, such as port requirements and VM creation links.
- Add troubleshooting tips or notes for connecting to Linux VMs (e.g., handling SSH keys, desktop environments, or session types).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/quick-backup-vm-terraform.md
...lob/main//articles/backup/quick-backup-vm-terraform.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively focuses on creating and backing up an Azure Windows virtual machine, with no mention or example of Linux VMs. All VM-related steps, variable names, and next steps reference Windows specifically. There are no Linux equivalents or guidance for users who wish to back up Linux VMs, and the documentation does not provide parity in examples or terminology.
Recommendations
- Provide parallel instructions and Terraform code samples for creating and backing up a Linux virtual machine in Azure.
- Update checklist and step descriptions to reference both Windows and Linux VMs, or clarify that the process is similar for Linux with links to relevant documentation.
- Include example variable names and outputs for Linux VMs (e.g., azurerm_linux_virtual_machine_name) alongside Windows examples.
- Add a 'Next steps' link to articles about Azure Linux VMs and their backup procedures.
- Consider renaming the article or clearly stating in the introduction that it is Windows-specific, and provide a cross-link to a Linux-focused quickstart if available.
Azure Docs
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 providing individual file restore instructions exclusively for Windows Server VMs, omitting Linux VM scenarios. It references Windows-specific features (such as registry keys for configuration) and does not mention or provide parity for Linux-based VM restores or tools. The documentation assumes a Windows-centric environment, both in feature support and in the examples provided.
Recommendations
- Include explicit guidance on restoring individual files from Linux-based VMs, or clearly state if this is unsupported.
- If Linux file-level restore is not supported, provide alternative recommendations or workarounds for Linux VMs.
- Balance documentation by mentioning Linux and Windows support status early and equally, rather than focusing on Windows first.
- Where Windows-specific tools (like registry keys) are referenced, provide equivalent Linux/Unix configuration methods if available, or clarify their absence.
- Add examples or notes for Linux administrators to clarify what restore options are available for Linux VMs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/scripts/set-system-state-backup-policy.md
...icles/backup/scripts/set-system-state-backup-policy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively provides a PowerShell script using Windows-specific modules (e.g., MSOnlineBackup) and registry paths, with no mention of Linux or cross-platform alternatives. All instructions and next steps are tailored to Windows environments, and there are no examples or guidance for Linux users.
Recommendations
- Add equivalent script samples for Linux environments, using bash or Python where possible.
- Document whether the MARS agent or similar backup functionality is available on Linux, and if so, provide Linux-specific instructions.
- If the feature is Windows-only, clearly state this limitation at the beginning of the documentation.
- Include a comparison table or section outlining differences in backup policy management between Windows and Linux platforms.
- Provide links to Linux backup policy documentation or third-party tools if native support is unavailable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/restore-all-files-volume-mars.md
...main//articles/backup/restore-all-files-volume-mars.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All instructions, screenshots, and terminology reference Windows-specific tools (such as the Microsoft Azure Backup snap-in), and there are no examples or guidance for Linux systems. There is no mention of Linux support, nor are any Linux commands, tools, or UI elements referenced.
Recommendations
- Clearly state whether the MARS Agent supports Linux. If not, mention this limitation at the top of the article.
- If Linux is supported, provide parallel instructions, screenshots, and examples for Linux systems, including relevant commands and UI differences.
- Reference Linux backup/restore tools and patterns where appropriate, or provide links to Linux-specific documentation.
- Avoid using Windows-specific terminology (e.g., 'snap-in', 'desktop app') without Linux equivalents or clarifications.
- Ensure that all steps and options are described for both Windows and Linux, or explicitly state platform limitations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/quick-kubernetes-backup-bicep.md
...main//articles/backup/quick-kubernetes-backup-bicep.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell deployment instructions, referencing PowerShell and Windows shell behaviors (e.g., right-click to paste), and omitting equivalent Azure CLI or Bash examples that would be more familiar to Linux/macOS users. The prerequisites and deployment sections focus on PowerShell, with no mention of Linux-native tools or workflows.
Recommendations
- Add Azure CLI deployment instructions alongside the PowerShell example, including a Bash-compatible script.
- In the prerequisites, mention both Azure PowerShell and Azure CLI as supported options, with installation links for each.
- Replace or supplement Windows-specific instructions (such as right-click to paste) with cross-platform guidance (e.g., Ctrl+Shift+V in many Linux terminals).
- Ensure that all steps and examples are presented in a platform-neutral order, or alternate between Windows and Linux-first instructions.
- Explicitly state that the process can be performed on Windows, Linux, or macOS, and provide any OS-specific notes as needed.
Azure Docs
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 exhibits a Windows bias by referencing Windows-specific tools and workflows first, such as PowerShell for VM creation, and providing detailed steps or links for Windows (e.g., OS disk swap) without equivalent Linux guidance. Linux-specific instructions are minimal and appear later in the document, with only a brief mention of reinstalling the ADE extension for Linux VMs. There are no Linux CLI or automation examples, and Windows-centric links are used for general VM operations.
Recommendations
- Provide equivalent Linux CLI (e.g., Azure CLI, Bash) examples alongside or before PowerShell examples for VM creation and disk swap operations.
- Include detailed, step-by-step instructions for restoring and re-encrypting Linux VMs, not just a brief note.
- Link to both Windows and Linux documentation for OS disk swap and other VM management tasks.
- Ensure that automation and scripting examples are cross-platform (PowerShell and Bash/Azure CLI) to support both Windows and Linux administrators.
- Review the order of presentation to avoid always listing Windows tools or workflows first; consider parallel presentation or alternating order.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/tutorial-postgresql-backup.md
...ob/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 towards Windows environments by referencing PowerShell scripts as the primary method for granting privileges to database users, without providing equivalent Linux/bash/psql examples. The mention of PowerShell occurs first and most prominently, with Linux alternatives only briefly mentioned as secondary options. There are no explicit Linux command-line examples or detailed instructions for non-Windows users, which may hinder users working in Linux environments.
Recommendations
- Provide equivalent bash/psql command examples alongside PowerShell scripts for granting privileges and other database operations.
- Explicitly mention and document Linux-native tools (e.g., psql, bash scripts) wherever PowerShell is referenced.
- Ensure that all steps involving scripts or command-line actions include both Windows (PowerShell) and Linux (bash/psql) instructions, ideally with side-by-side examples.
- Review and update screenshots or UI instructions to clarify that the process is cross-platform, or note any platform-specific differences.
- Consider adding a section or call-out for Linux users, summarizing the recommended tools and steps for common tasks.
Azure Docs
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 strong Windows bias. All operational examples, file paths, and tool references assume a Windows environment (e.g., use of PsExec, NT AUTHORITY\SYSTEM, C:\Program Files paths, and SSMS). There are no examples or guidance for restoring SQL Server on Linux-based Azure VMs, nor are Linux file paths, permissions, or tools mentioned. Instructions for mounting Azure File Shares and managing permissions are Windows-specific. The documentation presumes the use of SQL Server Management Studio (SSMS), which is primarily a Windows tool, and does not mention cross-platform alternatives or command-line options suitable for Linux environments.
Recommendations
- Provide equivalent instructions and examples for restoring SQL Server databases on Linux-based Azure VMs, including Linux file paths and permission management.
- Include guidance for mounting Azure File Shares on Linux (e.g., using cifs-utils) and setting appropriate permissions for the SQL Server process on Linux.
- Offer T-SQL restore examples that are platform-agnostic and clarify any differences in file system paths or prerequisites between Windows and Linux.
- Mention and provide examples for using cross-platform tools (such as Azure CLI, sqlcmd, or Azure Data Studio) for restore operations, not just SSMS.
- Explicitly state any limitations or differences in restore procedures between Windows and Linux SQL Server deployments.
- When referencing tools like PsExec or NT AUTHORITY\SYSTEM, provide Linux equivalents (such as sudo or service accounts) or clarify that these steps are Windows-specific.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/sap-hana-database-instances-restore.md
...articles/backup/sap-hana-database-instances-restore.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows/Azure Portal-centric bias. All procedural steps and screenshots are based on the Azure Portal UI, which is most commonly used in Windows environments. There is a specific mention of using 'PowerShell or CLI script' for permissions, but no explicit Linux shell or command-line examples are provided. There are no Linux-specific instructions, shell commands, or references to Linux-native tools, despite SAP HANA commonly running on Linux VMs.
Recommendations
- Provide explicit Linux shell (bash) command examples for mounting and managing disks after snapshot restore, especially since SAP HANA typically runs on Linux.
- Include Azure CLI examples for all steps where PowerShell is mentioned, and ensure these examples are runnable on Linux/macOS.
- Add instructions or links for performing restore operations via the Linux command line, not just through the Azure Portal.
- Clarify that the procedures apply to both Windows and Linux VMs, and specify any OS-specific steps or differences.
- Where screenshots are used, consider including at least one example from a Linux environment or terminal.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/soft-delete-virtual-machines.md
.../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 page demonstrates a Windows bias by providing detailed instructions and code samples exclusively for Azure PowerShell, with no equivalent examples for Linux users (such as Azure CLI or Bash). The PowerShell section is prominent and detailed, while Linux-native tools and workflows are not mentioned. This may disadvantage users who administer Azure from Linux or prefer cross-platform tools.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell operations, including deleting backup items, undoing deletions, and resuming backups.
- Explicitly mention that all operations can be performed from any OS using Azure CLI, and provide Bash-friendly examples.
- If certain features are only available via PowerShell, clearly state this limitation and provide a roadmap or alternatives for Linux users.
- Reorganize the documentation to present cross-platform (CLI) examples before or alongside PowerShell examples to avoid a 'Windows-first' impression.
- Include a table or section comparing the steps for Azure Portal, PowerShell, and CLI to ensure parity and clarity for all users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/scripts/set-file-folder-backup-policy.md
...ticles/backup/scripts/set-file-folder-backup-policy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively provides a PowerShell script sample for managing backup policies, referencing Windows-specific tools (such as the MARS agent and PowerShell modules like MSOnlineBackup). There are no Linux or cross-platform examples, nor any mention of equivalent Linux tools or scripting approaches. The instructions and context are entirely Windows-centric.
Recommendations
- Add equivalent script samples for Linux environments, using Bash or Python and relevant Linux backup tools (e.g., rsync, cron, or third-party backup agents).
- Clearly indicate in the introduction whether the procedure is Windows-only, and provide links or references to Linux-compatible solutions if available.
- If the MARS agent or the described backup policy management is not supported on Linux, explicitly state this and suggest alternative approaches for Linux systems.
- Ensure future documentation includes parity between Windows and Linux by providing side-by-side examples or a dedicated section for each platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/vm-upload-download-native.md
...ob/main//articles/bastion/vm-upload-download-native.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation prioritizes Windows workflows by presenting Windows RDP and native client usage first, with detailed steps and references to Windows-specific tools (MSTSC, right-click Copy/Paste). Linux/native SSH workflows are described later, with less detail and no explicit Linux-native file manager or SCP usage examples. There are no explicit Linux GUI or command-line examples for file transfer, and the documentation refers to 'Connect from a Linux native client' only as a link, not inline.
Recommendations
- Provide Linux/Unix-native examples (e.g., using Nautilus, Dolphin, or command-line SCP/SFTP) alongside or before Windows examples.
- Balance the order of presentation: alternate or parallelize Windows and Linux instructions, or start with a cross-platform overview.
- Include explicit Linux command-line examples for file transfer (e.g., SCP, SFTP) and clarify which steps apply to macOS as well.
- Reference Linux-native tools and workflows, not just Windows RDP/MSTSC and Copy/Paste.
- Ensure that all steps and screenshots (if any) are available for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/troubleshoot-error-cli-parse.md
...articles/digital-twins/troubleshoot-error-cli-parse.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation references Windows shells (CMD, PowerShell) and the Azure Cloud Shell PowerShell environment alongside Bash, but consistently lists Windows options before Linux/Bash equivalents. There are no Linux-specific examples or troubleshooting steps, and the guidance for escaping characters is generic rather than tailored to common Linux shells. The focus on PowerShell and CMD, and the lack of Linux/Unix-specific details, indicate a Windows-first and PowerShell-heavy bias.
Recommendations
- Provide explicit Linux/Bash shell examples for escaping special characters, such as showing how to escape quotes or special symbols in Bash.
- List Linux/Bash environments before or alongside Windows environments when suggesting alternative shells.
- Include troubleshooting steps or notes specific to Linux shells (e.g., zsh, bash, sh), highlighting their unique parsing behaviors.
- Mention common Linux tools or patterns (such as using single quotes to avoid variable expansion in Bash) where relevant.
- Ensure that links to further reading or references include Linux-focused content or examples.
Azure Docs
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 exhibits a moderate Windows bias. It references PowerShell scripts for key troubleshooting tasks (e.g., finding the Recovery Services vault, undeleting file shares) without providing equivalent Bash, Azure CLI, or Linux-native alternatives. The scripts and automation guidance are Windows/PowerShell-centric, and there are no Linux command-line examples or explicit cross-platform instructions. This may hinder Linux administrators or those preferring non-Windows environments.
Recommendations
- For every PowerShell script or reference, provide an equivalent Azure CLI or Bash script example, or explicitly state if only PowerShell is supported.
- Where scripts are linked (e.g., 'Undelete script'), offer both PowerShell and Bash/Azure CLI versions, or clarify cross-platform compatibility.
- Add troubleshooting steps and automation guidance using Azure CLI commands, which are cross-platform and widely used on Linux.
- Review all tool and script references to ensure Linux users are not excluded, and update documentation to mention platform compatibility.
- Consider including a 'Platform compatibility' note at the top of the page, clarifying which instructions are Windows-only and which are cross-platform.
Azure Docs
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 using the Azure Portal and Azure PowerShell to manage soft delete for SQL Server and SAP HANA backups in Azure VMs. However, it lacks any command-line examples or tooling references for Linux environments (such as Azure CLI, Bash, or native Linux tools). The only script-based automation shown is via PowerShell, which is primarily a Windows-centric tool, and there are no Linux-specific instructions or parity for users who may be managing SAP HANA on Linux VMs.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention and demonstrate how to perform soft delete and restore operations for SAP HANA on Linux VMs using native Linux tools or scripts, if available.
- Where possible, provide Bash script examples or references for Linux administrators.
- Clarify in the documentation whether all operations can be performed equally from Linux environments, and provide links or guidance for Linux users.
- Consider reordering or parallelizing instructions so that Windows/PowerShell and Linux/Azure CLI examples are presented side-by-side.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/whats-new.md
...ocs/azure-docs/blob/main//articles/backup/whats-new.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page for Azure Backup service release notes shows some evidence of Windows bias. Several features and updates reference Windows-specific tools (such as MARS agent and Microsoft Azure Backup Server), and Windows workloads (like SQL Server in Azure VM) are mentioned explicitly. There is a lack of explicit mention of Linux equivalents or parity for these tools, and no Linux-specific examples or guidance are provided. In some cases, Windows tooling is referenced without clarifying Linux support, which may give the impression that certain backup features are Windows-centric.
Recommendations
- Where Windows-specific tools (e.g., MARS agent, Microsoft Azure Backup Server) are mentioned, clarify if Linux equivalents exist or explicitly state Linux support status.
- Include examples or notes for Linux-based workloads (e.g., backing up Linux VMs, Linux file systems, or Linux database workloads) where relevant.
- When listing supported platforms for backup features, always mention both Windows and Linux (if supported), and avoid listing Windows first by default.
- Provide parity in documentation for Linux management tools (e.g., Azure CLI, REST API, or Linux-native agents) alongside Windows tools like PowerShell or MARS.
- Add links or references to Linux-specific backup guidance or best practices where available.
Azure Docs
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
Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, with all configuration steps, registry edits, and troubleshooting guidance tailored exclusively to Windows systems. There are no instructions, examples, or references for enabling or verifying TLS 1.2 on Linux-based systems, nor any mention of Linux tools or configuration files. The only protocol configuration guidance is via Windows registry and .NET Framework registry keys, and all external links and FAQs reference Windows documentation.
Recommendations
- Add a dedicated section for enabling and verifying TLS 1.2 on Linux systems, including common distributions (e.g., Ubuntu, CentOS, RHEL).
- Provide example commands for checking and enforcing TLS 1.2 usage on Linux, such as updating OpenSSL configuration or using system-wide crypto policies.
- Include troubleshooting steps for Linux environments, such as verifying supported TLS versions with openssl s_client or checking relevant log files.
- Reference Linux-specific documentation and tools alongside Windows resources, ensuring parity in guidance.
- Clarify in the introduction or prerequisites which operating systems the instructions apply to, and provide links or guidance for other platforms if not covered in detail.
Azure Docs
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
Powershell Heavy
Summary
The documentation is heavily oriented towards Windows environments, specifically referencing the MARS agent (which is Windows-only), the MARS console, and Windows PowerShell cmdlets. There are no Linux-specific instructions, examples, or references to Linux tools or workflows. All automation and scripting examples use PowerShell or Azure CLI, but the core backup/restore workflow assumes use of the Windows-only MARS agent and GUI console.
Recommendations
- Clearly state early in the documentation that the MARS agent and associated workflows are only supported on Windows, and provide links to equivalent Linux backup solutions (such as Azure Backup for Linux VMs or Azure CLI-based backup for Linux).
- If possible, provide parallel documentation or links for Linux backup agents or scripts that can securely store secrets in Azure Key Vault.
- Where automation is discussed, clarify which steps are Windows-only and which (such as Azure CLI or Key Vault operations) are cross-platform.
- Add a comparison table or section outlining backup options for both Windows and Linux, and how passphrase/key management differs between them.
- For any Azure CLI examples, ensure they are tested and work on both Windows and Linux shells, and note any OS-specific differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/bastion-connect-vm-ssh-linux.md
...main//articles/bastion/bastion-connect-vm-ssh-linux.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page is generally focused on connecting to Linux VMs via SSH using Azure Bastion and is mostly platform-neutral in its main flow. However, in sections that reference creating or managing Azure Key Vault secrets, the documentation repeatedly links to PowerShell-based instructions (e.g., 'quick-create-powershell') and explicitly recommends using PowerShell or Azure CLI, without providing explicit Linux/bash examples or prioritizing cross-platform CLI parity. There are no explicit Linux shell examples or references to Linux-native tooling for these tasks.
Recommendations
- Provide explicit bash/Azure CLI examples alongside or before PowerShell examples for tasks such as creating a Key Vault and storing SSH keys.
- Update links that currently point to PowerShell-specific quickstarts (e.g., 'quick-create-powershell') to also include or prioritize cross-platform or bash/Azure CLI guides.
- Clarify that Azure CLI is fully supported on Linux/macOS and provide sample commands for common tasks (e.g., storing secrets, assigning policies) in bash syntax.
- Where PowerShell is mentioned, always mention Azure CLI as an equal alternative, and provide both command syntaxes where possible.
- Consider adding a 'Platform differences' or 'Using on Linux/macOS' section to address any nuances for non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/configuration-settings.md
.../blob/main//articles/bastion/configuration-settings.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation consistently lists Azure PowerShell (a Windows-centric tool) before Azure CLI in configuration tables, and provides direct links to PowerShell cmdlets, with less emphasis on cross-platform or Linux-native tooling. There are no Linux-specific examples or mentions of Linux shell scripting, and the documentation assumes familiarity with Windows tools and patterns.
Recommendations
- Alternate the order of PowerShell and CLI examples/tables, or list Azure CLI first to reflect its cross-platform nature.
- Include explicit Linux shell (bash) examples for common configuration tasks, especially where PowerShell is highlighted.
- Reference Linux-native tools or scripting patterns where appropriate, not just Azure CLI.
- Clarify that Azure CLI is fully cross-platform and provide parity in example depth and links.
- Consider adding a section or callout for Linux administrators, summarizing the most relevant commands and considerations.
Azure Docs
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 provides both Azure CLI and PowerShell examples for configuring selective disk backup and restore, but the PowerShell examples are inherently Windows-centric. There is a notable emphasis on Windows tools and patterns, such as referencing BitLocker for encryption and using PowerShell as a primary scripting interface. Linux-specific instructions are limited to brief notes (e.g., ensuring 'lsblk' and 'lsscsi' are available), and there are no Linux shell (bash) script examples or explicit Linux command-line walkthroughs. Windows terminology and tools (e.g., drive C:, BitLocker) are mentioned before or more prominently than their Linux equivalents.
Recommendations
- Add explicit Linux (bash) command-line examples for common operations, such as using Azure CLI from a Linux shell.
- Include Linux-specific scripting examples (e.g., bash scripts) alongside PowerShell examples.
- When discussing encryption, mention Linux (dm-crypt) and Windows (BitLocker) equivalently and in parallel.
- Ensure that Linux prerequisites and troubleshooting steps are as detailed as those for Windows (e.g., provide sample commands to install 'lsblk' and 'lsscsi' on various distributions).
- Where possible, use neutral language (e.g., 'command line' instead of 'PowerShell') and avoid assuming Windows as the default environment.
- Add screenshots or walkthroughs of the Azure portal experience for both Windows and Linux VMs, highlighting any differences.