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 1701-1725 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/quick-install-backup-extension.md
...ain//articles/backup/quick-install-backup-extension.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section and referencing PowerShell as a primary automation example. There are no explicit Linux shell (bash) or cross-platform command-line examples in the main quickstart flow, and the step-by-step instructions focus exclusively on the Azure Portal UI, which is platform-agnostic but often associated with Windows-centric workflows. No Linux-specific tools or terminal commands are provided, and PowerShell is mentioned before CLI, which is more commonly used on Linux.
Recommendations
- In the 'Next steps' section, list Azure CLI before Azure PowerShell to reflect cross-platform parity and the prevalence of CLI usage on Linux.
- Add explicit Linux shell (bash) command examples for installing and configuring the backup extension using Azure CLI.
- Where automation is referenced, provide both PowerShell and bash/CLI script examples side by side.
- Clarify that the Azure Portal instructions are platform-agnostic and provide links to both Windows and Linux automation guides.
- Ensure that any screenshots or UI references do not imply a Windows-only environment.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/quick-backup-vm-portal.md
...s/blob/main//articles/backup/quick-backup-vm-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits a mild Windows bias, primarily by referencing Windows VM creation first and providing more explicit, step-by-step instructions for installing the Windows VM agent (including download links, file paths, and UI steps), while the Linux instructions are more generic and less detailed. The initial VM creation link points specifically to Windows VMs, and Windows-specific tools and file paths are mentioned before Linux equivalents.
Recommendations
- Provide parallel links and instructions for both Windows and Linux VM creation in the introduction.
- Ensure installation steps for the Linux VM agent are as detailed as those for Windows, including example commands for common distributions (e.g., apt, yum, zypper).
- Avoid mentioning Windows tools, file paths, or UI steps before Linux equivalents; present both platforms equally or group them together.
- Where screenshots or examples are shown, include both Windows and Linux scenarios where applicable.
- Review all sections to ensure Linux users are given equal clarity and actionable steps as Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/resources-customer-data-requests.md
...cles/digital-twins/resources-customer-data-requests.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently refers to the Azure portal and REST APIs for managing personal data, but does not provide any command-line examples or tooling guidance for Linux users. The Azure portal is a web-based tool accessible from any OS, but the lack of CLI, shell, or cross-platform scripting examples (such as Azure CLI or curl) means Linux users are not given parity in actionable guidance. There is an implicit 'Windows-first' bias due to the absence of Linux-specific or cross-platform instructions.
Recommendations
- Include examples using Azure CLI (az dt) for identifying, exporting, and deleting data, which works on both Windows and Linux.
- Provide REST API usage examples using curl or HTTPie, which are common on Linux.
- Explicitly mention that the Azure portal is web-based and accessible from any OS, to avoid the impression of Windows exclusivity.
- Where possible, add PowerShell and Bash script examples side by side to demonstrate cross-platform support.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/bastion-vm-copy-paste.md
...s/blob/main//articles/bastion/bastion-vm-copy-paste.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is focused exclusively on Windows virtual machines, with all instructions, prerequisites, and examples tailored to Windows. There is no mention of Linux VMs, nor are there any Linux-specific instructions or examples provided. This creates a bias by omitting guidance for users working with Linux virtual machines.
Recommendations
- Add a parallel section or article for Linux VMs, detailing how copy and paste works when connecting to Linux virtual machines via Azure Bastion.
- Include Linux-specific prerequisites (e.g., supported distributions, required packages, or settings).
- Provide examples of keyboard shortcuts and clipboard behaviors for common Linux desktop environments (e.g., GNOME, KDE, Xfce).
- Clarify any differences or limitations in copy/paste functionality between Windows and Linux VMs.
- Ensure that both Windows and Linux scenarios are equally represented in the documentation navigation and titles.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/sap-ase-database-about.md
...s/blob/main//articles/backup/sap-ase-database-about.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation implicitly assumes a Windows-centric context in several places, such as linking to 'Create a new empty VM' using the Windows VM quick-create portal and not providing explicit Linux examples or references. There is no mention of Linux-specific instructions, tools, or patterns, despite SAP ASE being commonly deployed on Linux. The documentation does not clarify whether the guidance applies equally to Linux VMs, nor does it provide Linux-specific links or considerations.
Recommendations
- Provide explicit examples and links for both Windows and Linux VM creation and management, especially when referencing VM restore or creation steps.
- Clarify in the introduction and relevant sections that the backup and restore procedures apply to both Windows and Linux VMs, or specify any differences.
- Include Linux-specific instructions or considerations where applicable, such as running the preregistration script, managing users, or restoring VMs.
- When referencing Azure documentation (e.g., VM creation), provide both Windows and Linux quick-create links.
- Review all examples and ensure parity by including Linux command-line or portal workflows alongside any Windows-specific guidance.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/sap-ase-database-backup.md
.../blob/main//articles/backup/sap-ase-database-backup.md
Medium Priority
View Details →
Detected Bias Types
Missing Windows Example
Linux First
Summary
The documentation is focused exclusively on Linux-based SAP ASE deployments. All instructions, prerequisites, and discovery steps refer to Linux VMs, with explicit references to 'unprotected Linux VMs' and commands like 'sudo python3'. There are no examples, instructions, or notes for Windows-based SAP ASE deployments, nor any mention of Windows tools, PowerShell, or Windows-specific patterns. The documentation assumes the reader is using Linux throughout.
Recommendations
- Add explicit guidance for SAP ASE deployments on Windows VMs, if supported, including any differences in prerequisites, script execution, and backup configuration.
- Provide Windows-specific examples or notes (e.g., how to check Python version, run scripts, or set up permissions on Windows).
- Clarify in the prerequisites or introduction whether the solution is Linux-only or if Windows is supported, to avoid confusion.
- If Windows is not supported, add a clear statement indicating that only Linux VMs are supported for SAP ASE backup using this method.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/scripts/disable-soft-delete-for-file-shares.md
.../backup/scripts/disable-soft-delete-for-file-shares.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation uses Windows-style path separators (e.g., .\rqbody-disableSoftDelete.json) in command examples and does not provide Linux/macOS equivalents. There is no mention of how to run the commands or reference files on non-Windows systems, which may confuse or exclude Linux/macOS users.
Recommendations
- Provide both Windows and Linux/macOS command examples, especially for file paths (e.g., .\rqbody-disableSoftDelete.json vs ./rqbody-disableSoftDelete.json).
- Explicitly state that armclient is cross-platform and provide installation instructions or references for Linux/macOS.
- Add a note clarifying path separator differences and how to adapt commands for different operating systems.
- Consider including a table or section with side-by-side Windows and Linux/macOS command syntax.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/security-overview.md
...e-docs/blob/main//articles/backup/security-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing the Microsoft Azure Recovery Services (MARS) agent for on-premises backups, which is a Windows-only tool. There are no mentions or examples for Linux-based on-premises backup solutions, nor are Linux-specific agents or procedures discussed. This omission may leave Linux users without clear guidance on securing their backups with Azure Backup.
Recommendations
- Include information and examples for Linux-based on-premises backup scenarios, such as using Azure Backup Server (MABS) or Azure Backup integration with System Center Data Protection Manager (DPM) for Linux workloads.
- Explicitly mention supported backup agents or tools for Linux systems, and provide links to relevant documentation.
- Add sections or callouts that address securing Linux backup data, including encryption, authentication, and recovery procedures.
- Ensure that monitoring, alerting, and security features are described for both Windows and Linux environments where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/view-reports.md
.../azure-docs/blob/main//articles/backup/view-reports.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates a mild Windows bias by referencing Windows-centric backup tools (such as DPM and SQL in Azure VM) more frequently and in greater detail than Linux equivalents. Workload examples and optimization scenarios are often described using Windows technologies (DPM, SQL Server, SAP HANA in Azure VM) with no explicit mention of Linux-based backup scenarios or tools. There are no PowerShell-specific instructions, but the absence of Linux-native backup examples or references suggests a Windows-first perspective.
Recommendations
- Include examples and references for Linux-based backup workloads, such as Azure Backup for Linux VMs, native Linux database workloads (e.g., MySQL, PostgreSQL on Linux), and file system backups.
- When discussing optimization and reporting scenarios, provide parity by describing how these features apply to Linux workloads, not just Windows-centric ones.
- Mention Linux-native tools and backup patterns where relevant, and ensure that screenshots and walkthroughs include Linux-based scenarios.
- Explicitly state support and reporting capabilities for both Windows and Linux workloads to assure users of cross-platform parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/tutorial-restore-disk.md
...cs/blob/main//articles/backup/tutorial-restore-disk.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely cross-platform and focused on Azure CLI, which is available on both Windows and Linux. However, there is a subtle Windows bias: the only cross-reference to alternative tooling is for PowerShell (a Windows-centric tool), and the only deep-link for restoring VMs with another tool is to a PowerShell tutorial. There is no mention of Linux-native scripting environments (e.g., Bash) or parity references for Linux-specific tools. Additionally, in the 'Cross-zonal restore' section, the link for zone-pinned VMs points to a Windows-specific Azure VM page, rather than a general or Linux equivalent.
Recommendations
- Where alternative tooling is referenced (such as PowerShell), also provide links to Linux-native alternatives (e.g., Bash scripting, or at least clarify that Azure CLI commands work identically on Linux and Windows).
- In cross-references, ensure parity by linking to both Windows and Linux documentation for related tasks (e.g., restoring VMs with Bash or other Linux tools, if available).
- When linking to documentation about Azure VM features (such as zone-pinned VMs), use general or Linux-specific pages, or provide both Windows and Linux links.
- Explicitly state that all CLI examples are cross-platform and can be run on both Windows and Linux, to reassure Linux users.
- Consider including a brief section or note on running these commands in common Linux shells (e.g., Bash, Zsh), especially for environment variable syntax and command chaining.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/bastion-connect-vm-scale-set.md
...main//articles/bastion/bastion-connect-vm-scale-set.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page provides instructions for connecting to a virtual machine scale set using Azure Bastion, but it implicitly assumes a Windows-centric workflow by referencing RDP (Remote Desktop Protocol) and does not mention Linux-specific connection methods (such as SSH) or provide Linux-focused examples. There are no explicit examples or guidance for Linux users or for connecting to Linux-based VM instances.
Recommendations
- Include explicit instructions and examples for connecting to Linux VM instances using SSH via Azure Bastion.
- Clarify in the 'Connect' section that both Windows (RDP) and Linux (SSH) connections are supported, and provide step-by-step guidance for each.
- Mention relevant Linux tools (e.g., SSH clients) and workflows alongside Windows tools and patterns.
- Ensure that screenshots or UI references show both RDP and SSH options where applicable.
- Add a note or section addressing any differences in the Bastion connection experience for Linux versus Windows VM scale set instances.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/native-client.md
...zure-docs/blob/main//articles/bastion/native-client.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a 'windows_first' bias by listing Windows native client connection instructions and links before Linux equivalents in both the connection table and the 'Next steps' section. There are no explicit Linux command-line or tool examples provided in the main body, and Linux instructions are only referenced via links, resulting in a 'missing_linux_example' bias.
Recommendations
- Present Linux and Windows instructions/examples in parallel, or alternate which comes first to avoid implicit prioritization.
- Include explicit Linux native client connection examples (e.g., SSH command-line usage) within the main documentation body, not just as external links.
- Ensure that screenshots and walkthroughs are balanced between Windows and Linux environments.
- Mention Linux tools (such as OpenSSH) alongside Windows tools (such as RDP) wherever relevant.
- In the connection table and 'Next steps', list Linux and Windows options together or in alternating order to reinforce parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/troubleshoot-resource-health.md
...articles/digital-twins/troubleshoot-resource-health.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes troubleshooting and health-check procedures using the Azure Portal web interface, which is platform-agnostic but implicitly assumes a GUI workflow common to Windows users. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor are there references to Linux-specific tools or workflows. The absence of CLI or cross-platform instructions may disadvantage Linux users or those preferring non-GUI automation.
Recommendations
- Add examples for checking resource health using the Azure CLI, which is cross-platform and widely used on Linux.
- If mentioning PowerShell, also provide equivalent Bash/Azure CLI commands.
- Explicitly state that the Azure Portal is web-based and accessible from any OS, to clarify platform neutrality.
- Include links or references to documentation on using Azure Resource Health and Service Health from the command line (Azure CLI, Bash, etc.).
- Consider adding a section on automating health checks using scripts suitable for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/session-recording.md
...-docs/blob/main//articles/bastion/session-recording.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page focuses exclusively on Azure portal GUI steps and does not provide any OS-specific examples. However, there is a subtle Windows bias in that it omits any mention of Linux-specific considerations, tools, or command-line alternatives (such as Azure CLI or Bash), which are commonly used by Linux administrators. Additionally, the documentation uses patterns and terminology (e.g., 'left pane', 'Configuration page') that are more familiar to Windows/GUI users, and does not mention or prioritize Linux or cross-platform command-line workflows.
Recommendations
- Add Azure CLI and/or PowerShell command examples for all configuration steps, ensuring parity for both Windows and Linux users.
- Explicitly mention that all steps can be performed from any OS via the Azure portal, and provide links to CLI/Bash alternatives.
- Include a section or note for Linux administrators, highlighting any OS-agnostic or Linux-specific considerations (such as using Bash scripts or az CLI).
- Where GUI navigation is described, supplement with equivalent command-line instructions to support non-GUI environments.
- Review terminology to ensure it is inclusive of both Windows and Linux users (e.g., avoid assuming familiarity with Windows-style navigation).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/quickstart-host-arm-template.md
...main//articles/bastion/quickstart-host-arm-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows virtual machines in the 'Next steps' section, with links and guidance only for creating and connecting to Windows VMs via Azure Bastion. There are no examples, links, or instructions for deploying or connecting to Linux VMs, nor are Linux-specific tools or scenarios mentioned.
Recommendations
- Add parallel 'Next steps' links and instructions for creating a Linux virtual machine in the Azure portal.
- Include a quickstart or guide for connecting to a Linux VM using Azure Bastion (e.g., SSH connection).
- Ensure that examples and screenshots are inclusive of both Windows and Linux scenarios where applicable.
- Explicitly mention that Azure Bastion supports both Windows (RDP) and Linux (SSH) connections, and provide links to relevant documentation for each.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/troubleshoot.md
...azure-docs/blob/main//articles/bastion/troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation shows mild Windows bias by prioritizing Windows scenarios (such as domain-joined VM sign-in) and referencing Windows-specific concepts (like RDP and domain credentials) before or instead of Linux equivalents. However, there is at least one Linux/Unix example (ssh-keygen) and mention of SSH clients. There are no PowerShell-heavy examples or exclusive use of Windows tools, but the focus on Windows domain-joined VMs and RDP is more prominent than Linux-specific troubleshooting.
Recommendations
- Add explicit troubleshooting steps and examples for connecting to Linux VMs, such as common SSH login issues, file transfer with SCP/SFTP, and handling Linux user credentials.
- Balance the 'Unable to sign in to my Windows domain-joined virtual machine' section with a parallel section for Linux VMs, e.g., 'Unable to sign in to my Linux virtual machine', including common causes and solutions.
- When mentioning file transfer, provide Linux-native client examples (e.g., scp, sftp) alongside RDP and SSH.
- In sections referencing RDP or domain credentials, also mention Linux authentication mechanisms and tools where applicable.
- Ensure that all troubleshooting steps are platform-agnostic or provide both Windows and Linux variants where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/accounts.md
...tDocs/azure-docs/blob/main//articles/batch/accounts.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page focuses on Azure Batch and Storage accounts without providing any OS-specific command-line examples. However, when mentioning programmatic creation of Batch accounts, it only references the Azure portal and the Batch Management .NET library (which is Windows-centric), with no mention of cross-platform tools like Azure CLI, Azure PowerShell, or SDKs for other languages. This may give the impression that Windows or .NET is the primary or preferred environment, and omits guidance for Linux or cross-platform users.
Recommendations
- Add examples for creating and managing Batch accounts using Azure CLI, which is cross-platform and widely used on Linux.
- Mention other SDKs (such as Python, Java, or Node.js) for programmatic management of Batch accounts, not just .NET.
- If referencing PowerShell, also provide Bash or CLI equivalents.
- Ensure that all tooling and workflow recommendations are inclusive of both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/vnet-peering.md
...azure-docs/blob/main//articles/bastion/vnet-peering.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a 'windows_first' bias by linking only to the Windows VM creation quickstart and the Windows RDP connection guide, without mentioning or linking to Linux VM equivalents or SSH connection instructions. There are no Linux-specific examples or references, which may lead Linux users to feel unsupported or unclear about the process.
Recommendations
- Include links to both Windows and Linux VM creation guides in the deployment overview step (e.g., link to /azure/virtual-machines/linux/quick-create-portal alongside the Windows link).
- Add instructions or references for connecting to Linux VMs via SSH using Azure Bastion, and link to the relevant documentation (e.g., bastion-connect-vm-ssh-linux.md).
- Ensure that examples and terminology are platform-neutral or provide parallel instructions for both Windows and Linux scenarios.
- Review all steps and FAQs to confirm that Linux users are equally supported and that no steps are Windows-specific unless absolutely necessary.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-aad-auth.md
...azure-docs/blob/main//articles/batch/batch-aad-auth.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page provides detailed instructions and code samples for authenticating Azure Batch services with Microsoft Entra ID, but it exhibits bias by omitting any Linux- or cross-platform-specific command-line examples. All portal navigation and setup instructions reference the Azure Portal UI, which is platform-agnostic, but there are no CLI (e.g., Azure CLI, Bash) examples for registration or configuration steps. Additionally, there are no PowerShell examples, but the absence of Linux/Bash/CLI alternatives means Windows users (who may be more familiar with .NET and the Azure Portal) are implicitly prioritized. The code samples are in .NET (C#) and Python, which are cross-platform, but the setup and registration steps lack parity for Linux users who may prefer CLI-based workflows.
Recommendations
- Add Azure CLI examples for application registration, permission assignment, and service principal creation, alongside the Azure Portal steps.
- Include Bash shell snippets for common setup tasks, such as retrieving tenant IDs, application IDs, and secrets.
- Explicitly mention that all code and configuration steps can be performed on Linux, macOS, or Windows, and provide links to cross-platform tooling.
- Where possible, provide both portal and CLI alternatives for each configuration step to ensure Linux users are equally supported.
- Consider including a table or section summarizing equivalent commands for Windows (PowerShell), Linux (Bash/Azure CLI), and macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/account-move.md
...s/azure-docs/blob/main//articles/batch/account-move.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes using the Azure portal (a web interface) and does not provide any command-line examples. While this avoids explicit Windows-only tools like PowerShell, it implicitly favors Windows users by omitting CLI-based instructions (such as Azure CLI or Bash scripts) that are commonly used on Linux and macOS. There are no examples or mentions of Linux-specific workflows or tools, nor is there guidance for users who prefer automation via command line, which is a common pattern in Linux environments.
Recommendations
- Add Azure CLI examples for exporting, modifying, and deploying ARM templates, including commands for downloading, editing, and deploying templates from the command line.
- Include Bash script snippets for common tasks, such as unzipping files and editing JSON, to demonstrate Linux-friendly workflows.
- Mention that all steps can be performed via the Azure CLI or PowerShell, and provide links or references to relevant documentation for both Windows and Linux users.
- Ensure that any downloadable scripts or automation tools are cross-platform or provide alternatives for Linux users.
- Explicitly state that the Azure portal is platform-agnostic, but highlight command-line alternatives for users who prefer or require them.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/vm-about.md
...ocs/azure-docs/blob/main//articles/bastion/vm-about.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing only Windows VMs in the copy/paste section and linking exclusively to a 'Copy and paste - Windows VMs' guide. There is no mention of Linux VMs or equivalent Linux instructions for copy/paste functionality, which may lead Linux users to believe the feature is unsupported or undocumented for their use case.
Recommendations
- Add explicit references to Linux VM support (or lack thereof) for features like copy/paste, and provide a separate guide or section for 'Copy and paste - Linux VMs' if supported.
- Ensure that all feature descriptions and linked guides mention both Windows and Linux platforms where applicable, or clearly state platform limitations.
- Review other linked articles (such as upload/download and audio) to ensure Linux parity is addressed and not just implied.
- Adopt a neutral ordering (e.g., 'Windows and Linux VMs') or alternate which platform is mentioned first to avoid implicit prioritization.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/quickstart-deploy-terraform.md
.../main//articles/bastion/quickstart-deploy-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but consistently lists Azure CLI (which is cross-platform) before Azure PowerShell. However, the PowerShell section uses Windows-style variable assignment syntax (with $), which may be confusing for Linux/macOS users. There are no explicit Linux-specific instructions, but the use of Azure CLI as the primary example helps maintain some parity. No Windows-only tools or patterns are mentioned, but the presence of PowerShell examples and syntax could be seen as a subtle Windows bias.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend it as the default for cross-platform users.
- Explicitly state that PowerShell Core is available on Linux/macOS if PowerShell examples are included, or clarify that the PowerShell examples are for users who prefer that shell.
- Consider adding a Bash shell tab or section for variable assignment and command usage to make Linux/macOS users feel more directly supported.
- If possible, avoid Windows-specific syntax in variable assignments in the PowerShell section, or provide equivalent Bash examples.
- In the prerequisites, mention that all steps work on Windows, Linux, and macOS, and link to installation instructions for each platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-cli-templates.md
...-docs/blob/main//articles/batch/batch-cli-templates.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally presents Azure CLI commands that are cross-platform, and the main pool template example uses Linux VMs and apt for package installation. However, in the section on file upload/download, only Windows-style paths (e.g., c:\source_videos\*.mp4) are shown, with no Linux/macOS equivalents. This prioritizes Windows usage patterns and omits guidance for Linux users.
Recommendations
- For every CLI command that includes a file path, provide both Windows and Linux/macOS examples (e.g., c:\source_videos\*.mp4 and ~/source_videos/*.mp4).
- Explicitly mention that the Azure CLI and Batch CLI extension are cross-platform, and highlight any OS-specific considerations.
- Where file paths or shell patterns are referenced, clarify syntax differences between Windows and Linux/macOS.
- Consider including a table or note summarizing common path and shell differences for users on different platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/delegate-subdomain.md
...ure-docs/blob/main//articles/dns/delegate-subdomain.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily provides instructions and examples using the Azure Portal and references Azure PowerShell for automation, but does not mention or provide examples for Linux users or cross-platform command-line tools (such as Azure CLI or Bash). The testing section instructs users to 'open a command prompt' and use 'nslookup', implicitly assuming a Windows environment and omitting Linux terminal or macOS alternatives.
Recommendations
- Include Azure CLI examples alongside or instead of PowerShell references, as Azure CLI is cross-platform and widely used on Linux and macOS.
- When instructing users to open a command prompt, clarify that this can be a Windows Command Prompt, Linux terminal, or macOS Terminal, and provide equivalent commands for each.
- Explicitly mention that 'nslookup' is available on Linux and macOS, or suggest alternative tools like 'dig' for those platforms.
- If screenshots or UI steps are platform-agnostic (as with the Azure Portal), clarify that the steps apply equally to all operating systems.
- Add a section or callout for Linux/macOS users, ensuring parity in automation and testing instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-certificate-migration-guide.md
...n//articles/batch/batch-certificate-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally addresses both Windows and Linux, but there is a subtle Windows-first bias. In the FAQ, links to Windows documentation are listed before Linux, and there are no explicit, step-by-step Linux command examples or code snippets, especially for certificate installation or access. Linux-specific guidance is limited to descriptive text, lacking parity with potential Windows-focused examples.
Recommendations
- Provide explicit Linux command-line examples (e.g., bash scripts or CLI commands) for common tasks such as installing certificates, adjusting permissions, or accessing certificate files.
- When referencing documentation for both Windows and Linux, alternate the order or present them side-by-side to avoid a Windows-first impression.
- Include sample configuration files or scripts for Linux environments, especially for tasks like copying certificates, setting file modes, or using the Key Vault VM extension.
- Ensure that all instructions and examples are available for both Windows and Linux, not just described in prose for Linux.
- Consider adding a dedicated section or table comparing steps for Windows and Linux to highlight parity and differences.