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 1451-1475 of 1657 flagged pages
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-data-movement-library.md
...es/storage/common/storage-use-data-movement-library.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exhibits a subtle Windows bias by using Windows-style file paths (e.g., 'C:/path/to/directory') in all code examples and never showing Linux/macOS equivalents. There are no explicit Linux or cross-platform file path examples, and no mention of platform-specific considerations for file paths or shell commands. While the Data Movement library itself is cross-platform, the documentation implicitly prioritizes Windows conventions, which may confuse or alienate Linux/macOS users.
Recommendations
- Provide file path examples using both Windows (e.g., 'C:/path/to/directory') and Linux/macOS (e.g., '/home/user/path/to/directory') formats in code samples.
- Explicitly state that the Data Movement library and its CLI commands are cross-platform, and clarify any platform-specific behaviors or requirements.
- Where shell commands are shown (e.g., 'dotnet add package'), mention that these work on all supported platforms, and note any differences if they exist.
- Add a section or note about handling file paths in a cross-platform way in .NET (e.g., using Path.Combine or Path.DirectorySeparatorChar).
- Review all examples and documentation text to ensure that Linux/macOS users are equally represented and that no assumptions are made about the user's operating system.
Create Pull Request
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-configure-private-endpoints.md
...elastic-san/elastic-san-configure-private-endpoints.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents PowerShell (a Windows-centric tool) instructions before Azure CLI examples, and the PowerShell section is more detailed and prominent. While Azure CLI is cross-platform, the order and emphasis may suggest a Windows-first bias. There are no Linux shell-specific examples (e.g., bash), and no explicit mention of Linux tools or patterns in the main configuration steps.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux users.
- Add explicit bash shell examples or clarify that Azure CLI commands are intended for bash/zsh users as well.
- Balance the detail and prominence of PowerShell and CLI sections, ensuring both are equally comprehensive.
- Explicitly mention Linux compatibility in the prerequisites and example sections.
- Consider adding a 'Linux' tab or section for common Linux shell usage patterns, especially for environment variable handling and scripting.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-delete.md
...ain/articles/storage/elastic-san/elastic-san-delete.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by consistently presenting Windows/PowerShell instructions and examples before their Linux/Azure CLI counterparts. PowerShell is given prominence in command examples, and the structure often leads with Windows tools/scripts, even when Linux equivalents are provided.
Recommendations
- Alternate the order of Windows/PowerShell and Linux/CLI examples to avoid always presenting Windows first.
- Where possible, present Azure CLI (cross-platform) examples before or alongside PowerShell to emphasize platform neutrality.
- Ensure parity in detail and clarity between Windows and Linux sections, including parameter explanations and example usage.
- Consider a unified tabbed interface for scripts and commands, so users can easily select their preferred platform without implicit prioritization.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-monitor-cloud-tiering.md
...s/storage/file-sync/file-sync-monitor-cloud-tiering.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation assumes the use of Azure File Sync on Windows servers and does not mention Linux at all. All monitoring instructions are based on the Azure portal or Azure Monitor, which are platform-agnostic, but the context and terminology (e.g., 'server endpoint', 'local volume', 'on-premises server') implicitly refer to Windows environments. There are no examples, instructions, or notes for Linux users, nor any mention of Linux compatibility or alternatives.
Recommendations
- Explicitly state platform requirements or limitations (e.g., if Azure File Sync is Windows-only, clarify this early in the documentation).
- If Linux support is available or planned, provide equivalent instructions, terminology, and screenshots for Linux environments.
- If Azure File Sync is not supported on Linux, add a clear note to inform users and suggest alternative solutions for Linux file synchronization and monitoring.
- Where possible, use platform-neutral language and clarify when instructions are specific to Windows.
- Include command-line or scripting examples for both Windows (PowerShell) and Linux (Bash/CLI) if applicable.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/tables/assign-azure-role-data-access.md
...ticles/storage/tables/assign-azure-role-data-access.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation presents both PowerShell and Azure CLI examples for assigning Azure roles, but PowerShell (a Windows-centric tool) is presented first and in more detail. There are no explicit Linux shell or cross-platform scripting examples, and the PowerShell example is more prominent, which may subtly favor Windows users.
Recommendations
- Alternate the order of PowerShell and Azure CLI sections or present Azure CLI first, as it is cross-platform and widely used on Linux.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
- Where possible, provide bash/zsh shell script snippets for common tasks, especially for automation scenarios.
- Clarify that PowerShell Core is available cross-platform, if relevant, and provide installation links for Linux/macOS.
- Ensure parity in detail and explanation between PowerShell and Azure CLI sections.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-redundancy.md
...s/blob/main/articles/storage/files/files-redundancy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a subtle Windows bias. In the 'Geo-redundancy for SSD file shares' section, only Windows-based solutions (Azure File Sync with on-premises Windows file server) are described for achieving geo-redundancy, with no mention of Linux-based alternatives. Additionally, the use of SMB (a protocol more commonly associated with Windows environments) is emphasized throughout, and NFS support is shown as limited. However, in the scripting examples for region supportability, both PowerShell (Windows) and Azure CLI (cross-platform) are provided, showing some parity.
Recommendations
- Include Linux-based alternatives for geo-redundancy, such as using rsync or other Linux-native tools to sync data between regions.
- When discussing Azure File Sync, clarify whether Linux file servers or third-party sync tools can be used for similar disaster recovery scenarios.
- Expand on NFS support and provide guidance/examples for Linux clients where possible.
- Ensure that any mention of tools or workflows (e.g., scripting, file sync) includes both Windows and Linux perspectives, or explicitly states platform limitations.
- Consider adding a section or callout for Linux administrators outlining best practices for redundancy and disaster recovery with Azure Files.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-dotnet-how-to-use-files.md
...icles/storage/files/storage-dotnet-how-to-use-files.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the 'Work with Azure Files using System.IO' section. While it mentions both Windows and Linux mounting guides, all code examples use Windows-style paths (e.g., Z:\file-share) and reference only the Windows SMB mount point. There are no examples or code snippets showing how to use System.IO with a Linux-mounted file share (e.g., /mnt/file-share). This may make Linux developers feel less supported or unsure about parity.
Recommendations
- Add parallel Linux examples for mounting and accessing Azure Files, including code snippets using Linux file paths (e.g., '/mnt/file-share').
- In all System.IO code examples, provide both Windows and Linux path variants, or use a variable to indicate the path can be platform-specific.
- When referencing mounting instructions, list Linux and Windows equally (not always Windows first), or group them together neutrally.
- Explicitly state that all System.IO examples work identically on Linux, and demonstrate this with at least one Linux-specific example.
- Consider including a table or note summarizing any OS-specific considerations for .NET developers using Azure Files.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-configure-s2s-vpn.md
...icles/storage/files/storage-files-configure-s2s-vpn.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias. In the prerequisites, Windows Server's RRAS is the only on-premises VPN appliance called out by name, with a direct link to its documentation, while no Linux-based VPN solutions (such as strongSwan, Libreswan, or OpenSwan) are mentioned or linked. Additionally, the Windows tool is mentioned before the general statement about device agnosticism, and before any Linux alternatives. However, the rest of the documentation is largely cross-platform, with Azure Portal, PowerShell, and CLI instructions, and explicit links to mounting instructions for Windows, macOS, and Linux. There are no PowerShell-heavy or missing Linux example issues in the Azure resource configuration steps.
Recommendations
- In the prerequisites section, add explicit mention of popular Linux-based VPN solutions (e.g., strongSwan, Libreswan, OpenSwan) as supported on-premises VPN appliances, and provide links to their configuration guides.
- Where Windows RRAS is mentioned, add a parallel sentence and link for Linux VPN solutions, e.g., 'If you don't have an existing network appliance, you can use strongSwan on Linux. See [strongSwan documentation](https://wiki.strongswan.org/) for configuration guidance.'
- Consider including a brief example or reference for obtaining the public IP address of the Azure VPN gateway using Azure CLI, not just PowerShell, in the 'Configure on-premises network appliance' section.
- Ensure that any references to on-premises configuration are balanced between Windows and Linux, especially in sections where specific tools or roles are named.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-scale-targets.md
.../articles/storage/files/storage-files-scale-targets.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the Azure File Sync sections, which exclusively reference Windows Server as the supported platform for the sync agent. There are no Linux equivalents or examples provided, and the performance guidance is tailored to Windows environments. No PowerShell commands or Windows-specific tools are mentioned, but the absence of Linux parity in Azure File Sync is notable.
Recommendations
- Explicitly state platform support for Azure File Sync at the beginning of relevant sections, clarifying if Linux is unsupported or if alternatives exist.
- If Linux support is available or planned, provide equivalent guidance, examples, and performance metrics for Linux-based sync agents.
- For general Azure Files usage, consider including both Windows (SMB) and Linux (NFS) client configuration and performance tuning examples.
- Reference or link to documentation for Linux-based file synchronization solutions that can be used with Azure Files, if Azure File Sync is Windows-only.
- Ensure future updates include parity in examples, troubleshooting, and best practices for both Windows and Linux environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/assign-azure-role-data-access.md
...ticles/storage/queues/assign-azure-role-data-access.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed instructions and examples for both PowerShell and Azure CLI, but PowerShell (a Windows-centric tool) is presented before Azure CLI. There are no Linux-specific command-line examples or explicit mention of Linux environments, and the PowerShell example is more prominent. The Azure CLI example is cross-platform, but the ordering and emphasis may suggest a Windows-first approach.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Consider adding a Bash shell example or clarifying that the Azure CLI example is suitable for Linux users.
- If referencing PowerShell, clarify that PowerShell Core is available cross-platform, or provide a note for Linux/macOS users.
- Ensure parity in detail and prominence between PowerShell and Azure CLI sections.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-prevent-file-share-deletion.md
...age/files/storage-files-prevent-file-share-deletion.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity between Azure Portal, PowerShell, and Azure CLI for all major operations (enable, restore, disable soft delete). However, PowerShell examples are always presented before Azure CLI, which may suggest a Windows-first approach. There are no explicit Linux-specific examples or references to Linux tools, but the CLI examples are cross-platform. There is a mild bias toward Windows/PowerShell by order of presentation and lack of explicit Linux context.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI examples first to reflect cross-platform usage.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and are suitable for Linux users.
- Consider adding Bash shell context or example scripts for Linux users, especially for automation scenarios.
- Where possible, provide notes or links for Linux-specific guidance (e.g., installing Azure CLI on Linux, using CLI in Bash scripts).
- If PowerShell is mentioned, clarify that PowerShell Core is available cross-platform, or provide a note for Linux users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-quickstart-queues-nodejs.md
...les/storage/queues/storage-quickstart-queues-nodejs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates mild Windows bias by listing Windows shells (cmd, PowerShell) before Bash when referring to the console, and by recommending Visual Studio Code (a Microsoft tool) for editing without mentioning alternatives. However, all commands and code samples are cross-platform and do not rely on Windows-specific tools or patterns. Linux users are not excluded, but Windows is subtly prioritized in phrasing and tool suggestions.
Recommendations
- When mentioning console windows, list Bash (or 'terminal') first, or use neutral phrasing such as 'In a terminal (such as Bash, PowerShell, or cmd)'.
- When suggesting code editors, mention alternatives to Visual Studio Code, or use generic language like 'Open the project in your preferred code editor'.
- Explicitly state that all commands are cross-platform and work on Windows, Linux, and macOS.
- Where environment variables are discussed, note any OS-specific differences (e.g., how to set environment variables in Bash vs. PowerShell/cmd).
- Consider including a brief section or note confirming that the quickstart is fully supported on Linux and macOS, not just Windows.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-python-how-to-use-file-storage.md
...torage/files/storage-python-how-to-use-file-storage.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in its file I/O section by exclusively using Windows-style file paths (e.g., 'Z:\\file-share') in all code examples and omitting equivalent Linux or cross-platform examples. While it does link to both Windows and Linux mounting guides, the code and usage patterns shown are only for Windows, with no Linux or POSIX path examples or notes on cross-platform compatibility.
Recommendations
- Provide parallel Linux examples for mounting and accessing Azure Files, using Linux-style paths (e.g., '/mnt/file-share').
- Use cross-platform code examples that detect the OS and set file paths accordingly, or explicitly show both Windows and Linux variants.
- Add notes or code comments explaining differences in file path syntax and permissions handling between Windows and Linux.
- Ensure that any references to tools, commands, or patterns (such as drive letters or backslashes) are balanced with Linux equivalents (such as mount points and forward slashes).
- Where possible, use Python's os.path or pathlib modules to demonstrate cross-platform path handling.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-java-how-to-use-file-storage.md
.../storage/files/storage-java-how-to-use-file-storage.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in the Java file I/O section: all code examples use a Windows-style SMB path (e.g., 'Z:\\file-share'), and no Linux or NFS path examples are provided. While links to both Windows and Linux mounting guides are included, the practical code and variable naming exclusively reference Windows conventions, omitting Linux equivalents.
Recommendations
- Provide parallel code examples using Linux/NFS-style paths (e.g., '/mnt/file-share') alongside Windows examples.
- When introducing file share paths, show both Windows and Linux/NFS variants, and explain any differences in mounting or path handling.
- In code snippets and variable naming, use neutral or dual examples (e.g., 'String fileSharePath = "Z:\\file-share" // Windows' and 'String fileSharePath = "/mnt/file-share" // Linux').
- Explicitly mention that the Java file I/O approach works identically on Linux, and provide at least one end-to-end example for Linux users.
- Ensure that any references to file system features (such as ACLs or locking) clarify OS-specific behaviors and limitations.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/backup-archive-disaster-recovery/datadobi/datadobi-solution-guide.md
...-disaster-recovery/datadobi/datadobi-solution-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows/Azure portal-centric bias. All procedural steps and screenshots focus exclusively on the Azure Portal GUI, with no mention of command-line alternatives (such as Azure CLI, PowerShell, or REST APIs) that are commonly used on Linux or cross-platform environments. There are no Linux-specific instructions, tools, or examples, nor is there any reference to how Linux administrators might perform equivalent tasks. The documentation assumes users will interact with Azure resources via the portal, which is more common in Windows-centric workflows.
Recommendations
- Add equivalent instructions for performing all Azure Storage setup and management tasks using the Azure CLI and/or Azure PowerShell, and clearly indicate which commands are cross-platform.
- Include at least one example of configuring DobiSync with Azure Blob Storage using command-line tools on Linux (e.g., az storage commands).
- Mention and link to documentation for REST API or SDK-based approaches for users who automate deployments from Linux systems.
- Balance the order of presentation: when introducing tools or methods, mention cross-platform or Linux-native options before or alongside Windows/portal-based approaches.
- Explicitly state that all steps can be performed from Linux, macOS, or Windows, and provide guidance for users on non-Windows platforms.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-tutorial-queues.md
...ain/articles/storage/queues/storage-tutorial-queues.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by referencing Windows-specific command-line environments (cmd, PowerShell) first, and by using Windows-style file paths and output in examples. While the tutorial is largely cross-platform (using .NET Core and Visual Studio Code), it does not provide explicit Linux/macOS terminal examples or outputs, and the command-line instructions and sample outputs are tailored to a Windows environment.
Recommendations
- Explicitly mention that all dotnet CLI commands work on Linux/macOS as well as Windows.
- When referring to command-line environments, list Bash/Terminal alongside cmd and PowerShell (e.g., 'In a console window (such as cmd, PowerShell, Bash, or Azure CLI)').
- Provide example outputs using Linux/macOS file paths and terminal prompts (e.g., '/home/user/Tutorials/QueueApp$') in addition to or instead of Windows paths.
- Avoid using only Windows-style paths (e.g., 'C:\Tutorials>') in code/output samples; consider using generic or platform-neutral paths.
- Add a note clarifying that Visual Studio Code and .NET Core SDK are fully cross-platform, and that all steps apply equally to Linux and macOS.
- If there are any platform-specific considerations (such as authentication or environment variables), call them out explicitly for Linux/macOS users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/backup-archive-disaster-recovery/commvault/commvault-solution-guide.md
...isaster-recovery/commvault/commvault-solution-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by exclusively providing instructions and screenshots for the Azure Portal GUI, which is most commonly accessed from Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux-specific tools or workflows. The documentation omits any Linux or cross-platform command-line guidance for integrating Commvault with Azure, focusing solely on GUI-based steps that are platform-agnostic but implicitly favor Windows users. There is also no mention of how to perform these tasks from a Linux environment or using automation scripts, which are common in Linux-centric workflows.
Recommendations
- Add equivalent command-line instructions using Azure CLI and/or Bash scripts for all Azure resource creation and configuration steps, ensuring Linux users can follow along without relying on the Azure Portal GUI.
- Include explicit references to cross-platform tools (e.g., Azure CLI, REST API) and provide example commands for both Windows (PowerShell) and Linux (Bash) environments.
- Mention how to install and use Commvault MediaAgent and Command Center on Linux, if supported, and provide Linux-specific configuration guidance.
- Where screenshots are used, supplement them with text-based step-by-step instructions that can be followed in any environment.
- Highlight any platform-specific considerations (e.g., file system permissions, service account setup) for Linux deployments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/storage-explorer/vs-azure-tools-storage-explorer-accessibility.md
...lorer/vs-azure-tools-storage-explorer-accessibility.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation demonstrates bias by explicitly stating that screen readers are not supported on Linux, while recommending specific screen readers for Windows and Mac. Additionally, all keyboard shortcuts are presented in a Windows-centric format (e.g., 'Control', 'Alt', 'F4'), with no mention of Linux or Mac equivalents, even though Storage Explorer is cross-platform. The ordering of platforms in the screen reader section also places Windows first.
Recommendations
- Investigate and document any available or partially supported screen readers on Linux, or provide guidance/workarounds for Linux users.
- Include Linux-specific keyboard shortcut variations if they differ from Windows, or explicitly state if they are the same.
- Present platform information in a neutral order (e.g., alphabetical: Linux, Mac, Windows) or rotate the order in different sections.
- For all accessibility features (zoom, high contrast, shortcuts), clarify any platform-specific differences, especially for Linux.
- If Linux support is limited, acknowledge this and provide a roadmap or links to community discussions about improving Linux accessibility.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/data-management/migration-tools-comparison.md
...partners/data-management/migration-tools-comparison.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Azure File Sync, a Windows-only tool, is highlighted in the opening tip as a recommended migration approach, with no Linux equivalent or alternative mentioned. Additionally, the 'Other features' section for AzCopy lists Windows support before Linux and macOS, and the overall narrative and tool selection (such as Azure File Sync) are more familiar to Windows administrators. However, the main comparison tables do include cross-platform tools and mention Linux support for AzCopy.
Recommendations
- When mentioning Azure File Sync as a migration tool, explicitly note that it is Windows-only and suggest Linux-friendly alternatives (such as rsync, Robocopy for Windows, or third-party tools) for non-Windows environments.
- In the 'Other features' section for AzCopy, list supported platforms in a neutral or alphabetical order (e.g., Linux, macOS, Windows) to avoid the perception of Windows primacy.
- Add a short section or tip highlighting migration strategies and tools for Linux/NFS environments, ensuring parity with the attention given to Windows/SMB solutions.
- Where possible, provide example workflows or links for both Windows and Linux users, especially in introductory or recommendation sections.
Storage
Use Azure Files for Azure Kubernetes Workloads
...es/storage/files/azure-kubernetes-service-workloads.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides examples and guidance for both Linux and Windows node pools, but there is a slight tendency to mention Windows support and SMB protocol before Linux/NFS equivalents. Most YAML and CLI examples are generic and work for both platforms, but NFS (Linux-only) is less emphasized and lacks dedicated YAML examples. Windows-specific tools or PowerShell are not directly referenced, but SMB (Windows-centric) is often the default protocol shown. Linux mount options are documented in detail, but Windows mount options are not, which may be a minor friction for Windows users, but the overall impact is low for Linux users.
Recommendations
- Add explicit YAML examples for NFS protocol and Linux-only scenarios, especially for dynamic and static provisioning.
- Where protocols are discussed, present Linux/NFS and Windows/SMB options equally, or start with Linux/NFS when describing Linux node pool scenarios.
- Include a brief section or link for Windows-specific mount options or troubleshooting for parity.
- Clarify in each example which platforms (Linux/Windows) are supported, and provide guidance for Linux-first deployments where appropriate.
Storage
Connect Azure Elastic SAN to Azure Kubernetes over iSCSI
...rticles/storage/elastic-san/elastic-san-connect-aks.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation lists both Azure PowerShell and Azure CLI as prerequisites, but mentions PowerShell first and provides PowerShell examples before CLI equivalents. This ordering and inclusion of PowerShell may subtly favor Windows users, though CLI examples are present and all core steps use cross-platform tools (kubectl, bash, YAML).
Recommendations
- List Azure CLI before Azure PowerShell in prerequisites and examples, as CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly note that Azure CLI is available on all platforms, while PowerShell may require additional setup on Linux/macOS.
- Where possible, provide CLI examples as the primary/default, with PowerShell as an alternative.
- Add a brief note clarifying that all kubectl/bash/YAML steps are platform-agnostic.
Storage
Azure Elastic SAN configuration best practices
...cles/storage/elastic-san/elastic-san-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally presents Windows examples and tools before Linux equivalents, especially in sections on enabling Accelerated Networking and configuring MPIO/iSCSI. Windows-specific tools (PowerShell, Registry Editor, iSCSI Initiator app) are mentioned by name and with screenshots, while Linux instructions are present but sometimes less detailed or shown after Windows. The overall structure and flow tend to favor Windows, though Linux guidance is included for all major configuration steps.
Recommendations
- Alternate the order of Windows and Linux examples so that Linux is shown first in some sections.
- Provide equivalent CLI examples for Linux where PowerShell is used for Windows, and link to Linux-specific documentation as prominently as Windows links.
- Include screenshots for Linux configuration steps where possible, matching the detail given to Windows.
- Explicitly state parity between Windows and Linux support at the start of each section to reassure non-Windows users.
- Ensure that all configuration steps (such as enabling Accelerated Networking) have clear Linux instructions and links.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux-specific instructions for disconnecting volumes, with scripts tailored for each platform. However, Windows/PowerShell examples and instructions are consistently presented before their Linux/Azure CLI counterparts throughout the page. PowerShell is emphasized as the first option for resource deletion, which may subtly signal a Windows-first approach.
Recommendations
- Alternate the order of examples so that Linux/Azure CLI instructions are sometimes presented first, or present both platforms side-by-side.
- Explicitly state that both PowerShell and Azure CLI are fully supported and equivalent for these operations.
- Consider adding macOS-specific notes if relevant, or clarify that CLI instructions apply to both Linux and macOS.
- Ensure parity in detail and clarity between Windows and Linux instructions/scripts.
Storage
Using the HDFS CLI with Azure Data Lake Storage
.../blobs/data-lake-storage-use-hdfs-data-lake-storage.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation includes a PowerShell example for initiating SSH to a Linux-based HDInsight cluster, which may imply a Windows-first approach. The SSH connection example is provided in PowerShell syntax, without a corresponding Linux/macOS shell example. However, the rest of the HDFS CLI usage is platform-agnostic and appropriate for Linux environments.
Recommendations
- Provide both Windows (PowerShell) and Linux/macOS (bash) examples for SSH connections to HDInsight clusters.
- Clarify that the HDFS CLI commands are identical across platforms, but the method for initiating SSH may differ.
- Add a note or section for Linux/macOS users showing the equivalent SSH command in bash (e.g., 'ssh sshuser@clustername-ssh.azurehdinsight.net').
Storage
Enable or disable SFTP support in Azure Blob Storage
.../blobs/secure-file-transfer-protocol-support-how-to.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides step-by-step instructions for enabling/disabling SFTP support in Azure Blob Storage via the Azure Portal, PowerShell, and Azure CLI. PowerShell examples are given equal prominence to Azure CLI, but PowerShell is listed before CLI in both enable and disable sections. This ordering may subtly favor Windows users, as PowerShell is primarily a Windows tool (though available cross-platform). No Linux/macOS-specific tools or shell examples are provided, but the Azure CLI instructions are fully cross-platform and sufficient for Linux/macOS users.
Recommendations
- Consider listing Azure CLI examples before PowerShell, as CLI is natively cross-platform and widely used on Linux/macOS.
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide a brief note for Linux/macOS users to use Azure CLI in their terminal.
- Optionally, add a Bash example using Azure CLI to reinforce Linux parity.
- If PowerShell is shown, clarify that PowerShell Core is available on Linux/macOS, or link to installation instructions for non-Windows users.