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 751-775 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/install-mars-agent.md
...-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 installing and using the Microsoft Azure Recovery Services (MARS) agent for Windows environments. All instructions, prerequisites, and examples are tailored to Windows systems, with references to Windows-specific tools (e.g., .exe installers, Windows OS settings, Windows VMs). There is no mention of Linux support, alternatives, or equivalent backup solutions for non-Windows platforms. The documentation assumes the user is operating in a Windows environment throughout.
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 users to appropriate Azure backup solutions (e.g., Azure Backup for Linux VMs, Azure CLI-based backup, or third-party tools).
- If Linux is supported, add equivalent Linux installation instructions, including commands, package names, and configuration steps.
- Include examples and screenshots for Linux environments where applicable, or explicitly mention the lack of Linux support and suggest alternatives.
- Avoid using Windows-specific terminology (e.g., .exe files, Windows OS settings) without clarifying platform applicability.
- Add a comparison table or section outlining backup options for both Windows and Linux, helping users choose the correct approach for their platform.
Create Pull Request
Azure Docs
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
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. While the main focus is on Azure CLI (which is cross-platform), several example variable assignments use PowerShell syntax (e.g., $DiskId = ...), which is not valid in Bash or Linux shells. There are no explicit Bash/Linux shell examples or notes for Linux users. Additionally, in the 'Next steps' section, Azure PowerShell is mentioned before Azure CLI, suggesting a Windows-first approach. There are no Linux-specific instructions or clarifications for cross-platform users.
Recommendations
- Provide both PowerShell and Bash/Linux shell examples for variable assignments and scripting steps. For example, show both $DiskId=... (PowerShell) and DiskId=... (Bash).
- Add a note clarifying that Azure CLI commands work on Windows, macOS, and Linux, and show how to adapt variable usage for each shell.
- In the 'Next steps' section, list Azure CLI before PowerShell, or present both equally, to avoid Windows-first ordering.
- Explicitly mention that all CLI commands are cross-platform, and provide troubleshooting tips for common shell differences (e.g., file redirection, quoting, environment variables).
- Where referencing scripts or automation, provide sample scripts for both PowerShell and Bash.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/encryption-at-rest-with-cmk.md
...b/main//articles/backup/encryption-at-rest-with-cmk.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is featured prominently and often listed before Azure CLI, and there are multiple references to Windows-specific tools and patterns (e.g., BitLocker, MARS agent). Linux-specific tools or workflows are not mentioned with equal prominence, and the documentation assumes familiarity with PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Ensure parity between PowerShell and Azure CLI examples by presenting them in parallel or alternating their order.
- Explicitly mention Linux equivalents (e.g., DM-Crypt) wherever Windows tools like BitLocker are referenced, and provide links to relevant documentation.
- Avoid language that assumes PowerShell as the default or primary automation tool; clarify that both PowerShell and CLI are cross-platform.
- Where Windows-specific limitations (such as MARS agent) are discussed, also clarify Linux agent/tool support and any equivalent limitations.
- Consider including Bash scripting examples for Linux users where appropriate, especially for automation scenarios.
- Review the order of examples and tool mentions to avoid consistently prioritizing Windows/PowerShell over cross-platform or Linux-native options.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/quick-backup-postgresql-flexible-server-arm.md
.../backup/quick-backup-postgresql-flexible-server-arm.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 by providing only PowerShell deployment instructions, referencing the Azure PowerShell module as a prerequisite, and omitting any Azure CLI or Bash examples. There is no mention of Linux-native tooling or cross-platform deployment methods, and the 'Next steps' section also links to a PowerShell-specific guide.
Recommendations
- Add Azure CLI and Bash examples for deploying the ARM template, ensuring parity with the PowerShell instructions.
- List both Azure PowerShell and Azure CLI as prerequisites, with installation links for each.
- In the 'Deploy the template' section, provide step-by-step instructions for both Windows (PowerShell) and Linux/macOS (Bash/CLI) users.
- Ensure that 'Next steps' includes links to both PowerShell and CLI-based restore guides.
- Use neutral language when referring to tools, e.g., 'Use Azure PowerShell or Azure CLI to deploy the template,' rather than only mentioning PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/quickstart-host-portal.md
.../blob/main//articles/bastion/quickstart-host-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates subtle Windows bias. In the prerequisites, the Windows VM creation link is listed before the Linux VM link. In the required VM inbound ports, the Windows port (3389) is listed before the Linux port (22). In the section about keyboard shortcuts, only Windows VM shortcut keys are discussed, with no equivalent Linux/SSH examples. There is also a focus on RDP (a Windows protocol) alongside SSH, but no Linux-specific connection guidance or troubleshooting. No Linux desktop/GUI access or SSH-specific tips are provided.
Recommendations
- Alternate the order of Windows and Linux VM creation links, or present them together to avoid implying priority.
- In lists (such as required ports), alternate or group Windows and Linux information equally.
- Add Linux/SSH-specific connection tips, such as how to use SSH key authentication, X11 forwarding, or common SSH troubleshooting steps.
- Include Linux desktop/GUI access guidance (e.g., using Bastion to connect to a Linux VM with a GUI, if supported) or clarify if only CLI access is available.
- Provide keyboard shortcut guidance for Linux VMs (e.g., how to send Ctrl+Alt+Del or other common shortcuts in a Linux session).
- Ensure that all instructions and examples are provided for both Windows and Linux users where applicable.
Azure Docs
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 by referencing PowerShell before CLI when discussing command-line options for moving Backup vaults. No explicit Linux-specific examples or tools are provided, and the only command-line examples mentioned are PowerShell and Azure CLI, with PowerShell listed first. There are no screenshots or walkthroughs for Linux environments or non-Windows command-line shells. The rest of the documentation is focused on the Azure Portal UI, which is cross-platform, but the lack of parity in command-line examples and the ordering of tools suggests a subtle preference for Windows environments.
Recommendations
- When mentioning command-line options, list Azure CLI before PowerShell or present both equally, as Azure CLI is cross-platform and widely used on Linux.
- Provide explicit Linux/macOS shell examples (e.g., bash) alongside PowerShell examples where scripts or commands are referenced.
- Include screenshots or walkthroughs for command-line operations in Linux environments, not just the Azure Portal UI.
- Clarify that all command-line instructions are cross-platform where applicable, and note any differences for Linux users.
- Consider adding a section or callout for Linux administrators to ensure parity and inclusivity.
Azure Docs
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 page demonstrates a strong Windows bias. The protection matrix almost exclusively lists Windows operating systems, workloads, and file systems, with only a single, minimal mention of Linux support (as a guest VM, with limited snapshot support). All detailed examples, requirements, and recovery options are for Windows environments, and Windows-specific technologies (NTFS, VSS, ReFS, Windows Management Framework, Hyper-V, etc.) are referenced throughout. There are no Linux-native workloads, file systems, or recovery scenarios described, and Linux support is only referenced as a secondary scenario (VM guest), not as a first-class platform.
Recommendations
- Add a dedicated section or matrix rows for Linux workloads, including supported distributions, file systems (e.g., ext4, xfs), and backup/recovery scenarios.
- Clarify whether Azure Backup Server can be installed on Linux or if it can only protect Linux VMs as guests; if not supported, state this explicitly.
- Provide Linux-specific guidance for backup and recovery, including any limitations, required agents, or integration with Linux-native tools (e.g., LVM snapshots, rsync, etc.).
- Include parity in example scenarios, such as item-level recovery for Linux VMs, and describe any differences in snapshot consistency or restore options.
- Reference Linux documentation and tools alongside Windows ones, and avoid assuming NTFS/VSS as the only supported technologies.
Azure Docs
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 for MABS (Azure Backup Server) V3 UR1 protection matrix demonstrates a strong Windows bias. Windows workloads, tools, and patterns are described in detail and always appear first. Linux support is minimal, limited to guest VM backup with only file-consistent snapshots, and lacks parity in features such as item-level recovery. There are no Linux-specific examples, tools, or recovery scenarios, and the documentation assumes NTFS and other Windows-specific technologies throughout.
Recommendations
- Provide Linux-specific backup and recovery examples, including item-level recovery if supported.
- Include Linux-native tools and patterns (e.g., mention ext4, xfs, LVM, or Linux backup agents where applicable).
- List Linux workloads alongside Windows workloads in all tables, not as a separate or last section.
- Clarify any feature gaps for Linux and provide guidance or workarounds for Linux administrators.
- Avoid assuming NTFS or Windows-only file systems in requirements and highlight Linux file system compatibility.
- If PowerShell or Windows-specific tools are mentioned, offer equivalent Linux command-line or scripting examples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/manage-telemetry.md
...re-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-only application, and all instructions and screenshots are specific to the Windows GUI. There are no command-line examples (such as PowerShell or CMD), but more importantly, there is no mention of Linux tools, Linux-based management, or parity for non-Windows environments. The documentation implicitly assumes a Windows environment throughout.
Recommendations
- Clarify early in the documentation that MABS is a Windows-only product, if that is the case, to set expectations for Linux users.
- If any telemetry management is possible via command-line tools (e.g., PowerShell, CMD), provide those examples alongside GUI instructions.
- If there is any Linux support (e.g., for agents or workloads), document how telemetry is managed in those contexts.
- If Linux is not supported, explicitly state this to avoid confusion for cross-platform administrators.
- Consider referencing Azure-native backup solutions that support Linux, and link to their telemetry management documentation for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/offline-backup-azure-data-box-dpm-mabs.md
...icles/backup/offline-backup-azure-data-box-dpm-mabs.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation is heavily biased towards Windows environments. All instructions, examples, and prerequisites are specific to Windows Server and Windows-based tools (e.g., PSExec, PowerShell modules, Windows Registry, Windows file paths). There is no mention of Linux support, nor are there any Linux-specific instructions or alternatives provided. The documentation assumes the use of DPM/MABS, which are Windows-only products, but even generic steps (such as mounting NFS shares, certificate management, or Azure Data Box usage) are presented solely in a Windows context.
Recommendations
- Clearly state early in the documentation that the process is only supported on Windows, if that is the case. If Linux support is possible (e.g., for Azure Data Box or MARS agent), provide equivalent Linux instructions.
- For generic steps (such as mounting NFS shares, connecting to Azure Data Box, or transferring files), include Linux command-line examples (e.g., using mount, smbclient, or NFS utilities on Linux).
- If PowerShell is required, clarify if cross-platform PowerShell Core can be used, or provide Bash/CLI alternatives where possible.
- For certificate management and registry edits, provide Linux equivalents (such as using OpenSSL for certificates and relevant config file edits instead of Windows Registry).
- If DPM/MABS are Windows-only, but Azure Data Box can be used in Linux environments for other backup tools, link to or mention those scenarios to help Linux users.
- Avoid assuming Windows file paths and UI navigation (e.g., C:\Program Files, Windows Certificate Manager) without noting alternatives or limitations for non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/soft-delete-azure-file-share.md
.../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 a Windows bias by referencing a PowerShell script for undeleting file shares and not providing equivalent CLI or Linux-based examples. The only script linked is a PowerShell script, and there are no mentions of cross-platform tools like Azure CLI or Bash scripts. This may disadvantage users on Linux or macOS platforms.
Recommendations
- Provide Azure CLI examples alongside or instead of PowerShell scripts for operations such as undeleting file shares.
- Explicitly mention that the operations can be performed from any platform (Windows, Linux, macOS) using cross-platform tools.
- Link to or provide Bash script examples where automation is discussed, not just PowerShell.
- Ensure that documentation references both Azure Portal and CLI-based workflows, not just those familiar to Windows users.
- Where scripts are referenced, clarify their platform compatibility and offer alternatives for non-Windows environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/monitoring-and-alerts-overview.md
...ain//articles/backup/monitoring-and-alerts-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently referencing PowerShell as a primary non-portal client, listing it before CLI and REST API, and linking to PowerShell-specific guides. There is a lack of explicit Linux or Bash examples, and no mention of Linux-specific tools or usage patterns. The documentation assumes familiarity with Windows-centric tools and workflows, potentially making it less accessible for Linux administrators.
Recommendations
- Provide explicit Bash/Azure CLI examples alongside or before PowerShell examples in all sections referencing command-line usage.
- Ensure that links to automation or scripting guides include both PowerShell and Bash/CLI versions.
- Mention Linux/Bash as a first-class option whenever discussing non-portal clients, not just PowerShell.
- Add a section or callout specifically addressing Linux administrators, highlighting parity of features and any Linux-specific considerations.
- Review references to 'PowerShell' and ensure they are always paired with 'CLI' and 'REST API', and that examples are balanced.
- Where possible, include screenshots or walkthroughs using Linux shells or tools, not just Windows/PowerShell environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/quick-backup-vm-template.md
...blob/main//articles/backup/quick-backup-vm-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a significant Windows bias. It exclusively provides PowerShell scripts for deploying the ARM template and managing resources, with no equivalent Azure CLI or Bash examples. The template itself is described as deploying a 'simple Windows VM,' with no mention of Linux VM options. References to further actions (such as starting or monitoring backup jobs) link to PowerShell-specific guides. While the Azure CLI and portal are mentioned in passing, all concrete examples and step-by-step instructions are Windows/PowerShell-centric, and Linux users are not provided with parallel guidance.
Recommendations
- Add Azure CLI and Bash examples alongside PowerShell scripts for all deployment and cleanup steps.
- Include instructions and template options for deploying and backing up Linux VMs, not just Windows VMs.
- When referencing further actions (such as starting or monitoring backup jobs), provide links to both PowerShell and CLI/Linux documentation.
- Reword sections to avoid implying PowerShell is the default or only method; present CLI and portal options equally and early.
- Ensure that all code blocks and walkthroughs have Linux-compatible alternatives, and clearly label them.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/private-endpoints.md
...e-docs/blob/main//articles/backup/private-endpoints.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong Windows and PowerShell bias. All command-line examples and automation scripts are provided exclusively in PowerShell, with no Bash, Azure CLI, or Linux-native alternatives. The documentation references Windows file paths (e.g., C:\<filepath>), and all scripting and automation guidance assumes a Windows environment. There is no mention of Linux tools or cross-platform approaches, and the use of Azure Cloud Shell is always in PowerShell mode. This could hinder Linux or macOS users who prefer or require Bash or Azure CLI workflows.
Recommendations
- Provide equivalent Azure CLI (az) commands and Bash scripts for all PowerShell examples and automation steps.
- Include Linux/macOS file path examples alongside Windows paths where file references are made.
- Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI or REST API, and provide those workflows.
- When referencing Cloud Shell, show both Bash and PowerShell options.
- For downloadable scripts, offer Bash or Python alternatives where feasible, or document how to run PowerShell scripts on Linux/macOS.
- Add a section or callouts for Linux users, highlighting any OS-specific considerations or differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/sql-support-matrix.md
...-docs/blob/main//articles/backup/sql-support-matrix.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Windows Tools
Summary
The documentation is heavily biased toward Windows environments. Only Windows Server operating systems are listed as supported, and it is explicitly stated that Linux is not supported. All examples and references (such as PowerShell) are Windows-centric, and there is no mention of Linux tools, commands, or equivalent workflows. The documentation assumes the reader is operating in a Windows environment and does not provide parity or guidance for Linux users.
Recommendations
- Clearly state early in the document that only Windows is supported, and provide a roadmap or link to Linux support if/when available.
- If Linux support is planned, include a section outlining expected parity and timelines.
- Where PowerShell or Windows tools are mentioned, note the absence of Linux/CLI alternatives and provide equivalent Linux guidance if/when available.
- Consider adding a FAQ or explicit callout for Linux users, clarifying the current limitations and suggesting alternative backup strategies for SQL Server on Linux in Azure VMs.
- Monitor and update the documentation promptly if/when Linux support is introduced, ensuring examples and instructions are provided for both platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/pre-backup-post-backup-scripts.md
...ain//articles/backup/pre-backup-post-backup-scripts.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing only Windows-style paths (e.g., 'Drive:'), using Windows-specific folder structures, and providing examples and instructions that assume a Windows environment. There are no examples or guidance for Linux systems, and all tool references (such as cscript for VBScript) are Windows-specific. The documentation does not mention or address Linux equivalents or cross-platform considerations.
Recommendations
- Include Linux-specific instructions and examples, such as using Linux file paths (e.g., /opt/mabs/Scripting) and shell scripts.
- Clarify whether MABS supports Linux agents and, if so, provide parity in documentation for Linux environments.
- Mention Linux scripting options (e.g., bash, sh, Python) alongside Windows scripting tools.
- Provide sample ScriptingConfig.xml entries using Linux paths and script types.
- Explicitly state any platform limitations or differences in script execution between Windows and Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/quick-backup-azure-files-vault-tier-bicep.md
...es/backup/quick-backup-azure-files-vault-tier-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 PowerShell deployment instructions, referencing the Azure PowerShell module as a prerequisite, and omitting equivalent Azure CLI or Bash examples. The deployment workflow assumes familiarity with PowerShell and does not address Linux or cross-platform users directly.
Recommendations
- Add Azure CLI and Bash deployment instructions alongside PowerShell, ensuring parity for Linux and macOS users.
- In the prerequisites section, mention both Azure PowerShell and Azure CLI as options, with links to their respective installation guides.
- When referencing the Azure Cloud Shell, clarify that both Bash and PowerShell environments are available, and provide instructions for both.
- Ensure that all management and restore steps include CLI and REST API examples, not just PowerShell.
- Review all code snippets and instructions to ensure they are platform-agnostic or provide alternatives for non-Windows environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/quick-backup-postgresql-flexible-server-cli.md
.../backup/quick-backup-postgresql-flexible-server-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits a Windows-first bias by referencing PowerShell objects and patterns as defaults, describing modification workflows in terms of PowerShell object manipulation, and using Windows-style file paths (e.g., '.\OSSPolicy.json'). Linux/Unix equivalents (such as bash scripting, forward slashes in file paths, or Linux-native workflows) are not mentioned or exemplified. The documentation assumes familiarity with PowerShell and Windows conventions, which may hinder Linux users.
Recommendations
- Provide Linux/Unix-specific examples alongside or before Windows/PowerShell examples, including bash commands and forward-slash file paths (e.g., './OSSPolicy.json').
- Avoid describing PowerShell object manipulation as the default; instead, present both PowerShell and CLI/file-based workflows equally, or clarify which is for which platform.
- Explicitly mention that file redirection and path syntax may differ on Linux/macOS (e.g., use '>' for redirection and '/' for paths).
- Wherever PowerShell is referenced, provide equivalent bash or shell scripting guidance for Linux users.
- Add a section or callout for cross-platform differences, especially regarding file handling and scripting environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/offline-backup-server-previous-versions.md
...cles/backup/offline-backup-server-previous-versions.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, examples, and screenshots assume the use of Windows Server, Windows client, or Windows-specific tools. There is no mention of Linux support, nor are there any Linux command-line examples or alternative workflows. All utilities referenced are Windows executables, and registry edits, command prompts, and PowerShell commands are used exclusively. The documentation does not address how to perform these tasks on Linux systems or whether it is even possible.
Recommendations
- Explicitly state whether Linux is supported or not for DPM/MABS offline backup workflows.
- If Linux support exists, provide equivalent instructions, commands, and examples for Linux environments (e.g., bash commands, Linux file paths, Linux-compatible utilities).
- Mention and document any cross-platform or Linux-native tools that can be used for offline backup and Azure Import/Export workflows.
- If only Windows is supported, clarify this early in the documentation to set expectations for Linux users.
- Provide guidance or references for Linux users who may need to perform similar offline backup operations, even if via different Azure services or tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/quick-backup-azure-files-vault-tier-arm.md
...cles/backup/quick-backup-azure-files-vault-tier-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 examples and instructions, with no equivalent Azure CLI or Bash examples for Linux/macOS users. The 'Deploy the template' section explicitly features PowerShell, and the 'Next steps' section lists PowerShell-based management tasks before CLI or REST API options. There is no mention of Linux-specific workflows or cross-platform command-line instructions.
Recommendations
- Add Azure CLI and Bash examples for deploying the ARM template, alongside or before PowerShell examples.
- In the 'Deploy the template' section, provide explicit instructions for both Windows (PowerShell) and Linux/macOS (CLI/Bash) users.
- In the 'Next steps' section, list Azure CLI and REST API options before or alongside PowerShell, or group them by platform to avoid implicit prioritization.
- Include a note clarifying that all deployment and management steps can be performed on any OS using the Azure CLI, not just via PowerShell.
- Where possible, provide links to cross-platform tools and documentation, and avoid assuming the user is on Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/bastion-faq.md
.../azure-docs/blob/main//articles/bastion/bastion-faq.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-specific instructions and tools, such as referencing Windows settings for keyboard layout configuration and mentioning RDP (a Windows protocol) more prominently. There are no explicit Linux or macOS examples for common administrative tasks, and Linux-specific workflows (such as SSH client usage or keyboard layout configuration on Linux) are omitted. The documentation also references Windows tools and patterns without providing Linux equivalents.
Recommendations
- Provide parallel Linux (and macOS) instructions for tasks such as setting keyboard layouts, connecting via SSH, and using native clients.
- Include examples and references for both RDP (Windows) and SSH (Linux/macOS) workflows wherever applicable.
- Avoid listing Windows tools or settings first; instead, present cross-platform options together or in a platform-neutral order.
- Explicitly mention supported browsers and clients for Linux, not just Windows and Mac.
- Add links to documentation on configuring keyboard layouts and remote access tools on Linux and macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/query-backups-using-azure-resource-graph.md
...les/backup/query-backups-using-azure-resource-graph.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it mentions that automation clients such as PowerShell, CLI, and SDK are supported, PowerShell is listed first and is the only automation client with a direct documentation link in the main text. There are no explicit Linux or Bash shell examples, and no mention of Linux-specific tools or workflows. The focus on PowerShell and the absence of Linux/Bash examples or references may make Linux users feel less prioritized.
Recommendations
- List Azure CLI before PowerShell when mentioning automation clients, or present both together to avoid implying a preference.
- Provide direct links to both PowerShell and Azure CLI documentation equally.
- Include at least one example of running an ARG query using Azure CLI (az resource-graph query) and/or Bash scripting.
- Explicitly mention that all automation steps can be performed on Linux, macOS, and Windows.
- If possible, add a section or callout for Linux users, highlighting any platform-specific considerations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/quick-blob-vaulted-backup-cli.md
...main//articles/backup/quick-blob-vaulted-backup-cli.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page, while focused on Azure CLI (which is cross-platform), exhibits subtle Windows bias. References to creating a Backup vault link to a PowerShell-based guide, and the 'Next step' section lists Azure PowerShell before Azure CLI, suggesting a Windows-first approach. There is no explicit mention of Linux or Linux-specific considerations, and PowerShell is presented as a primary tool alongside CLI.
Recommendations
- Ensure that all prerequisite and example links referencing PowerShell have equivalent Azure CLI or Bash examples, and link to those for cross-platform parity.
- In the 'Next step' section, list Azure CLI before Azure PowerShell to avoid Windows-first ordering, or group them without preference.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS to reinforce cross-platform support.
- If any included files ([blob-backup-create-policy-cli.md], etc.) contain OS-specific instructions, ensure Linux and macOS are equally represented.
- Provide Bash shell examples or notes where relevant, especially for scripting or automation contexts.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/quick-backup-postgresql-flexible-server-bicep.md
...ackup/quick-backup-postgresql-flexible-server-bicep.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 by providing only PowerShell deployment instructions and referencing Windows-specific shell behaviors (e.g., right-click to paste). There are no CLI, Bash, or Linux-native examples, and the 'Next steps' section continues the PowerShell focus. Linux users are left without guidance for deploying the Bicep file or restoring backups using cross-platform tools.
Recommendations
- Add Azure CLI (az deployment group create ...) examples for deploying the Bicep template, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash shell instructions and note how to paste code in common Linux/macOS terminals.
- Rephrase instructions to avoid Windows-specific actions (e.g., 'right-click to paste'), or provide Linux/macOS equivalents.
- In the 'Next steps' section, link to both PowerShell and Azure CLI (or Bash) restore guides.
- Explicitly state that the process works on all platforms and provide parity in tooling and examples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/quick-backup-postgresql-database-portal.md
...cles/backup/quick-backup-postgresql-database-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell scripts as the primary method for granting privileges to database users, both in the prerequisites and in the main configuration flow. PowerShell is mentioned first and most prominently, with Linux/Unix-native alternatives (such as psql or bash scripting) only briefly referenced as alternatives. There are no explicit Linux command-line examples or detailed instructions for non-Windows environments, and the documentation assumes familiarity with Windows-centric tools and workflows.
Recommendations
- Provide explicit Linux/Unix command-line examples (e.g., using psql or bash scripts) alongside PowerShell scripts for all steps involving privilege assignment or automation.
- Mention Linux-native tools (such as psql, bash, or shell scripts) before or alongside PowerShell, not only as an afterthought.
- Include screenshots or walkthroughs using Linux terminals or tools where applicable.
- Clarify that all steps can be completed from Linux/macOS environments, and provide parity in instructions for non-Windows users.
- Where ARM templates or Azure CLI are referenced, ensure examples are cross-platform and not tailored only to Windows/PowerShell environments.