Storage
688
Total Pages
395
Linux-Friendly Pages
293
Pages with Bias
42.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
1657 issues found
Showing 1651-1657 of 1657 flagged pages
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-connect-aks.md
...rticles/storage/elastic-san/elastic-san-connect-aks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists both Azure PowerShell and Azure CLI for retrieving volume information, but PowerShell is mentioned first in both the prerequisites and the example commands. No exclusive Windows tools or patterns are present, and Linux parity is generally maintained, but the ordering subtly prioritizes Windows/PowerShell.
Recommendations
- List Azure CLI before Azure PowerShell in both prerequisites and example commands, as Azure CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS to reinforce cross-platform parity.
- Where possible, provide example commands in a neutral order or group them together under a 'Choose one' heading.
- Consider adding a note that all kubectl and YAML examples are platform-agnostic, reinforcing that the workflow is not Windows-specific.
Create Pull Request
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/container-storage/volume-snapshot-restore.md
...s/storage/container-storage/volume-snapshot-restore.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation uses the phrase 'use your favorite text editor to create a YAML manifest file such as code acstor-volumesnapshotclass.yaml', where 'code' refers to Visual Studio Code. This subtly prioritizes a tool (VS Code) that is most commonly associated with Windows, and the guidance to run commands with 'administrative privileges' is a Windows-centric pattern. However, all command-line examples use kubectl and Azure CLI, which are cross-platform, and there are no PowerShell-specific commands or Windows-only tools. There are no explicit Linux examples or mentions of Linux-native editors (e.g., nano, vim), and the documentation does not mention sudo for privilege escalation on Linux.
Recommendations
- When suggesting text editors, mention cross-platform or Linux-native editors alongside VS Code, e.g., 'such as nano, vim, or code'.
- When referencing administrative privileges, clarify for both platforms, e.g., 'run with administrative privileges (use sudo on Linux/macOS)'.
- Add a note that all commands are cross-platform and provide any necessary platform-specific instructions (e.g., using sudo for Azure CLI on Linux).
- Consider providing at least one example of using a Linux-native editor or shell pattern to ensure parity.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-shared-volumes.md
...cles/storage/elastic-san/elastic-san-shared-volumes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows Server Failover Cluster (WSFC) before Pacemaker when listing cluster managers, which may suggest a Windows-first bias. However, no command-line examples, scripts, or tooling are provided for either Windows or Linux, and both Windows and Linux cluster managers are referenced. No exclusive use of Windows tools or missing Linux examples are present.
Recommendations
- List cluster managers in a neutral or alternating order (e.g., 'such as Pacemaker or Windows Server Failover Cluster (WSFC)') or mention both simultaneously without preference.
- Provide example workflows or scripts for both Windows (e.g., PowerShell/WSFC) and Linux (e.g., Pacemaker, systemd) environments to ensure parity.
- Explicitly mention that both Windows and Linux are supported and, if possible, link to relevant setup guides for each platform.
- If referencing tools or patterns, ensure Linux equivalents are always mentioned alongside Windows ones.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-queues-introduction.md
...articles/storage/queues/storage-queues-introduction.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a subtle Windows bias in the 'Next steps' section, where the quickstart links for .NET, Java, Python, and Node.js all include 'environment-variable-windows' as a tab or default, and in the Java quickstart, 'powershell' is also specified as a tab. There are no explicit Linux or cross-platform command-line examples or tabs mentioned, and Windows-specific patterns are prioritized in the quickstart links.
Recommendations
- Ensure that quickstart links and code samples include Linux/macOS tabs or examples alongside Windows, not just as an afterthought or omitted.
- Avoid defaulting to 'environment-variable-windows' in tabbed code samples; provide parity for Linux and macOS environments.
- If referencing command-line tools (e.g., PowerShell), also provide Bash or cross-platform CLI equivalents.
- Review the quickstart guides linked to ensure Linux users are equally supported and that instructions are not Windows-centric.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-quickstart-queues-java.md
...icles/storage/queues/storage-quickstart-queues-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild 'windows_first' bias in the project creation step, where Windows shells (cmd, PowerShell) are mentioned before Bash, and the PowerShell example is presented before the Bash example. However, both Windows and Linux (Bash) command examples are provided, and the rest of the documentation is platform-neutral, focusing on Java code and Maven commands that work cross-platform.
Recommendations
- Present Bash (Linux/macOS) and PowerShell (Windows) examples in parallel tabs, or list Bash first to avoid implicit prioritization of Windows.
- Explicitly mention that all Maven and Java commands work identically on Windows, Linux, and macOS.
- Where file paths or environment variables are referenced (e.g., project directory paths, environment variable setup), provide both Windows and Linux/macOS syntax or clarify any differences.
- Ensure that any references to console windows or shells use inclusive language (e.g., 'such as Bash, PowerShell, or cmd') and avoid listing Windows shells first by default.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-quickstart-queues-dotnet.md
...les/storage/queues/storage-quickstart-queues-dotnet.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a subtle Windows bias by listing Windows-specific shells ('cmd', 'PowerShell') before 'Bash' when describing how to create a .NET project. However, all command-line examples use the cross-platform 'dotnet' CLI and do not rely on Windows-only tools or PowerShell-specific syntax. No Linux-specific instructions or examples are missing, but the ordering and mention of Windows shells first may give the impression of prioritizing Windows environments.
Recommendations
- List cross-platform shells (e.g., Bash) before or alongside Windows shells when describing console instructions, e.g., 'In a console window (such as Bash, cmd, or PowerShell)...'
- Explicitly state that all instructions and commands work on Windows, Linux, and macOS to reinforce cross-platform support.
- Where appropriate, provide example commands for setting environment variables on both Windows (setx, $env:) and Linux/macOS (export), especially when referencing environment variables like AZURE_STORAGE_CONNECTION_STRING.
- Consider including a brief note or section confirming that the .NET SDK and Azure Storage client libraries are fully supported on Linux and macOS, not just Windows.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-quickstart-queues-python.md
...les/storage/queues/storage-quickstart-queues-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a mild 'windows_first' bias in its initial project setup instructions. When instructing users to open a console window, it lists 'cmd, PowerShell, or Bash' in that order, placing Windows shells before Bash (commonly used on Linux/macOS). However, all command-line and environment variable instructions are cross-platform and do not rely on Windows-specific tools or patterns. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present.
Recommendations
- List Bash (or 'Bash, cmd, or PowerShell') first when mentioning console windows, or clarify that any terminal (on Windows, Linux, or macOS) can be used.
- Explicitly state that all commands are cross-platform and work on Windows, Linux, and macOS.
- If referencing environment variables, briefly mention how to set them on both Windows (set/export) and Linux/macOS for completeness.
- Continue to avoid Windows-only tools or patterns in future updates to maintain parity.