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 1176-1200 of 1657 flagged pages
Storage
Quickstart: Azure Blob Storage client library for Python
...icles/storage/blobs/storage-quickstart-blobs-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation exhibits mild Windows bias in several areas. In authentication instructions, PowerShell is listed as a primary method for signing in, with a dedicated tab and example, while Linux shell alternatives are not equivalently highlighted. In environment variable setup, Windows instructions (setx) are presented before Linux (export), and the Windows method is described with more detail (e.g., note about restarting the command window). The initial project setup mentions both PowerShell and Bash, but does not provide platform-specific examples beyond that. Overall, Windows tools and patterns are mentioned first or with greater emphasis, and PowerShell is given a dedicated authentication section, while Linux equivalents (e.g., Bash, zsh) are not.
Recommendations
- Ensure equal prominence for Linux and macOS tools in authentication instructions, such as including Bash/zsh examples and tabs alongside PowerShell.
- Present environment variable setup instructions for Linux/macOS before or alongside Windows, with equal detail (e.g., note about shell session requirements).
- Where platform-specific instructions are needed, provide parallel examples for both Windows (PowerShell/CMD) and Linux/macOS (Bash/zsh), and avoid listing Windows first by default.
- Add explicit notes or tabs for Linux/macOS authentication via Azure CLI and shell, matching the detail given to PowerShell.
- Review all command-line instructions to ensure terminology and examples are inclusive of all major platforms.
Create Pull Request
Storage
Apply an Azure Resource Manager lock to a storage account
.../main/articles/storage/common/lock-account-resource.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides step-by-step instructions for applying a Resource Manager lock using the Azure Portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, which may suggest a Windows-first approach. PowerShell is a Windows-centric tool, and its prominence can be interpreted as bias toward Windows users. However, the inclusion of Azure CLI (which is cross-platform) mitigates some of this bias. There are no Linux-specific shell examples (e.g., Bash), nor are Linux tools or workflows mentioned.
Recommendations
- Present Azure CLI examples before PowerShell examples to prioritize cross-platform tools.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide guidance for Linux users where relevant.
- Add Bash shell usage notes or examples for Linux users, such as installation or environment setup tips.
- Consider including links or references to Linux-specific documentation or troubleshooting guides.
Storage
Check the Last Sync Time property for a storage account
...lob/main/articles/storage/common/last-sync-time-get.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for checking the Last Sync Time property. However, PowerShell is presented first, which may suggest a Windows-centric approach. There is no explicit mention of Linux or macOS environments, nor are there examples tailored to those platforms (e.g., Bash scripting, native Linux tools). The CLI example is generic but does not clarify cross-platform usage, and the PowerShell example is specific to Windows environments.
Recommendations
- Alternate the order of examples, sometimes presenting Azure CLI (which is cross-platform) before PowerShell to avoid implicit Windows-first bias.
- Explicitly mention that Azure CLI works on Windows, Linux, and macOS, and provide example commands in Bash or shell script format.
- Include a note or section for Linux/macOS users, clarifying installation and usage differences for Azure CLI and PowerShell.
- If relevant, provide examples using other cross-platform tools or SDKs (e.g., Python, REST API) to further increase parity.
Storage
Configure an expiration policy for shared access signatures (SAS)
.../main/articles/storage/common/sas-expiration-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents configuration steps for SAS expiration policy in the Azure portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, which may suggest a Windows-first bias. The PowerShell section is detailed and includes verification steps, while the Azure CLI section is similar but appears after PowerShell. No Linux-specific tools or shell examples (e.g., Bash) are provided, and there are no explicit Linux instructions or screenshots. The documentation does not mention Linux or cross-platform considerations, and the use of PowerShell may be less familiar to Linux users.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more commonly used on Linux.
- Include Bash shell examples for Azure CLI commands to demonstrate usage in Linux environments.
- Add notes or sections highlighting cross-platform compatibility, especially for Azure CLI.
- Include screenshots or terminal output from Linux environments to show parity.
- Explicitly mention that Azure CLI works on Windows, Linux, and macOS, and provide links to installation guides for each platform.
Storage
Network Connections in Azure Storage Explorer
...in/articles/storage/common/storage-explorer-network.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page describes proxy configuration options for Azure Storage Explorer, but lacks explicit examples or instructions for Linux environments. The guidance on 'system proxy' refers to OS proxy settings and Chromium documentation, but does not clarify how to configure these on Linux or macOS. The recommendation order ('system proxy' first) implicitly favors Windows, where proxy configuration is more commonly GUI-driven. There are no references to Linux-specific tools, environment variables, or configuration patterns, nor are there examples for Linux users.
Recommendations
- Add explicit instructions or examples for configuring system proxy settings on Linux (e.g., using GNOME/KDE network settings, environment variables, or CLI tools like 'gsettings' or 'network-manager').
- Include a section or table comparing proxy configuration steps across Windows, macOS, and Linux.
- Reference Linux-specific proxy management tools (such as 'cntlm' for NTLM proxies, or mention how to set environment variables in bash/zsh profiles).
- Clarify how Chromium networking stack interacts with system proxy settings on Linux and macOS.
- Ensure troubleshooting steps and next steps include Linux/macOS-specific guidance.
Storage
Choose an Azure solution for data transfer
...torage/common/storage-choose-data-transfer-solution.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by listing Azure PowerShell before Azure CLI in the scriptable tools section and by featuring a PowerShell quickstart before the Azure CLI quickstart in the 'Next steps' section. While Linux-compatible tools (AzCopy, Azure CLI, SDKs) are mentioned, examples and guidance do not prioritize or equally highlight Linux usage, and there is no explicit mention of Linux-specific patterns or shell examples.
Recommendations
- Alternate the order of PowerShell and CLI examples to avoid consistently listing Windows tools first.
- Include explicit Linux shell (bash) examples alongside PowerShell, especially in sections discussing scriptable/programmatic transfers.
- Add references to Linux-native tools and usage patterns where relevant (e.g., AzCopy usage in bash scripts).
- Ensure that quickstart links for CLI and PowerShell are presented with equal prominence, or provide a combined quickstart that covers both platforms.
- Mention platform compatibility for each tool to clarify cross-platform support.
Storage
Create a resource instance network rule for Azure Storage
.../common/storage-network-security-resource-instances.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed PowerShell examples for managing Azure Storage resource instance network rules, with PowerShell presented before Azure CLI. PowerShell is primarily a Windows tool, and its prominence may disadvantage Linux users. While Azure CLI examples are included, there are no Bash or Linux-specific workflow notes, and PowerShell is given precedence in the ordering and detail.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and widely used on Linux.
- Add explicit Bash/Linux shell examples or notes about running Azure CLI on Linux/macOS.
- Include a brief section explaining tool parity and recommending Azure CLI for Linux/macOS users.
- Ensure that any advanced scenarios covered in PowerShell are also shown with Azure CLI commands.
- Avoid implying PowerShell is the default or preferred method unless justified by functionality.
Storage
Set the default public network access rule: Azure Storage
.../common/storage-network-security-set-default-access.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed instructions for configuring Azure Storage public network access using the Azure Portal, PowerShell, and Azure CLI. The PowerShell section appears before the Azure CLI section, and PowerShell is a Windows-centric tool, which may suggest a Windows-first bias. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux tools or patterns. However, the Azure CLI instructions are cross-platform and do provide parity for Linux users.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Add Bash shell example blocks for Azure CLI usage to reinforce Linux parity.
- Include a note that PowerShell Core is available on Linux, if relevant, or clarify platform compatibility for each tool.
- Consider referencing Linux-specific package managers or installation steps for Azure CLI and PowerShell.
Storage
Require secure transfer to ensure secure connections
...cles/storage/common/storage-require-secure-transfer.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents PowerShell (a Windows-centric tool) examples before Azure CLI, and provides detailed PowerShell instructions, including module installation and usage, without equivalent detail for Linux-native tools or environments. There is no mention of Bash, shell scripting, or Linux-specific workflows, and the CLI section is less detailed than the PowerShell section.
Recommendations
- Provide Bash or shell script examples for Linux users, especially for checking and setting the 'enableHttpsTrafficOnly' property using Azure CLI.
- Ensure that Azure CLI instructions are as detailed as PowerShell instructions, including installation and authentication steps for Linux/macOS.
- Explicitly mention cross-platform compatibility for Azure CLI and other SDKs, clarifying usage on Linux and macOS.
- Add a section or note on using REST API calls via curl or similar Linux tools.
- Balance the order of examples so that CLI or cross-platform tools are presented before or alongside PowerShell.
Storage
Azure Storage encryption for data at rest
.../articles/storage/common/storage-service-encryption.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing BitLocker encryption as an analogy for Azure Storage encryption and linking to the Windows-specific Cryptography API: Next Generation (CNG) documentation. No Linux equivalents or cross-platform cryptographic modules are mentioned, and Windows tools are referenced before any mention of platform-neutral or Linux tools. However, the rest of the page is generally platform-agnostic and does not provide OS-specific command-line examples.
Recommendations
- When referencing encryption technologies, provide analogies or examples relevant to both Windows and Linux users (e.g., compare Azure Storage encryption to Linux dm-crypt/LUKS as well as BitLocker).
- Include links to documentation about cross-platform or Linux cryptographic modules (e.g., OpenSSL, dm-crypt, LUKS) alongside Windows CNG.
- Ensure that any tool or API references are balanced between Windows and Linux, or clarify their platform specificity.
- Consider adding a brief section or note on how Azure Storage encryption compares to common Linux encryption practices to improve parity.
Storage
Azure data transfer options for small datasets with low to moderate network bandwidth
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-small-dataset-low-moderate-network.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists scripting/programmatic tools as 'AzCopy/PowerShell/Azure CLI', placing PowerShell before Azure CLI, despite CLI being more cross-platform. PowerShell is highlighted as a recommended option for users comfortable with system administration, but there is no mention of Bash, shell scripting, or Linux-native patterns. Examples and tool recommendations do not provide parity for Linux users, and the only scripting example outside PowerShell is Azure CLI, which is mentioned after PowerShell.
Recommendations
- List Azure CLI before PowerShell when recommending scripting/programmatic tools, as CLI is cross-platform and more familiar to Linux users.
- Explicitly mention Bash/shell scripting as a viable option for Linux users, possibly with sample commands.
- Provide example commands for both PowerShell and Bash/Azure CLI to ensure parity.
- Highlight that AzCopy and Azure CLI are fully supported on Linux, and provide links to Linux installation guides.
- Avoid implying PowerShell is the default or primary scripting tool for Azure unless contextually justified.
Storage
Get started with the Azure Storage management library for .NET
...icles/storage/common/storage-srp-dotnet-get-started.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Azure PowerShell as a primary tool for resource provider registration, and by omitting explicit Linux-specific instructions or examples. While the .NET SDK is cross-platform, the documentation does not provide parity in examples or guidance for Linux users, such as shell commands, environment variable setup, or Linux-specific authentication patterns.
Recommendations
- Include explicit Linux and macOS instructions for environment variable setup and authentication, such as showing how to set environment variables in Bash/zsh.
- Provide CLI examples using Bash or other Linux shells alongside PowerShell examples, especially for resource provider registration and credential configuration.
- Clarify that the .NET SDK and Azure CLI are cross-platform, and provide links or notes for Linux/macOS installation and usage.
- Ensure that references to Azure PowerShell are balanced with Azure CLI examples, and present both options equally (not listing PowerShell first).
- Add troubleshooting tips or notes for common Linux-specific issues (e.g., file permissions, credential storage locations).
Storage
Authorize access for AzCopy with a user identity
...e/common/storage-use-azcopy-authorize-user-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for environment variable setup, but Windows (PowerShell) examples are consistently presented alongside or immediately after Linux (bash) examples. The Azure PowerShell method is described in detail and given its own section, while no equivalent Linux-native automation tool (e.g., bash scripting or shell integration) is discussed. Azure CLI is presented in a cross-platform way, but PowerShell receives more prominence, and Windows-specific instructions (PowerShell syntax) are always included, sometimes before Linux equivalents.
Recommendations
- Ensure Linux examples are presented first or equally alongside Windows examples, not as secondary.
- Include Linux-native automation/scripting alternatives where Azure PowerShell is discussed (e.g., bash scripts for token retrieval).
- Add explicit notes about cross-platform compatibility for all commands, clarifying which work on Linux, macOS, and Windows.
- Where PowerShell is mentioned, also mention bash or other Linux-native shells for parity.
- Review the order of tabs and sections to avoid implicit prioritization of Windows tools or workflows.
Storage
Synchronize with Azure Blob storage by using AzCopy v10
...storage/common/storage-use-azcopy-blobs-synchronize.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in its examples and guidance. All local path examples use Windows-style paths (e.g., 'C:\myDirectory'), and there are no explicit Linux or macOS path examples (e.g., '/home/user/myDirectory'). The guidance for quoting paths prioritizes Windows Command Shell (cmd.exe) and only mentions Linux/Unix shells in passing, without providing concrete Linux examples. No Linux-specific tools or shell patterns are discussed.
Recommendations
- Add explicit Linux/macOS examples using POSIX-style paths (e.g., '/home/user/myDirectory') alongside Windows examples.
- Include sample commands for both Windows and Linux/macOS environments, showing differences in quoting and path syntax.
- Expand tips to mention common Linux shells (bash, zsh) and their quoting conventions, not just Windows Command Shell.
- Where relevant, mention platform-specific considerations (e.g., file permissions, case sensitivity) for Linux/macOS users.
- Ensure parity in screenshots, tool recommendations, and troubleshooting steps for both Windows and Linux/macOS platforms.
Storage
Download blobs from Azure Blob Storage by using AzCopy v10
...es/storage/common/storage-use-azcopy-blobs-download.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently uses Windows-style paths (e.g., 'C:\myDirectory\myTextFile.txt') in all command examples and does not provide any Linux or macOS path examples (e.g., '/home/user/myTextFile.txt'). Windows paths are presented as the default, and there are no Linux-specific examples or notes beyond quoting conventions. This may make the documentation less accessible or immediately useful to Linux users.
Recommendations
- Add Linux/macOS path examples alongside Windows examples for each command (e.g., '/home/user/myTextFile.txt').
- Explicitly mention that AzCopy works cross-platform and provide guidance for Linux/macOS users, including common local path conventions.
- Where quoting conventions are discussed, provide concrete Linux/macOS shell examples (e.g., Bash, Zsh) to illustrate usage.
- Consider alternating the order of examples so that Linux/macOS examples are not always secondary to Windows examples.
- Add a section or note highlighting any Linux/macOS-specific considerations for AzCopy usage, such as permissions or environment variables.
Storage
Upload files to Azure Blob storage by using AzCopy v10
...cles/storage/common/storage-use-azcopy-blobs-upload.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page consistently uses Windows-style paths (e.g., 'C:\myDirectory\myTextFile.txt') in all examples and does not provide any Linux or macOS equivalents (such as '/home/user/myDirectory/myTextFile.txt'). While there are tips about quoting conventions for different shells, all actual command examples use Windows paths and directory separators, implicitly prioritizing Windows users and omitting Linux-specific patterns.
Recommendations
- For each example, provide both Windows and Linux/macOS versions side by side, showing appropriate path formats and quoting conventions.
- Include notes or tables summarizing differences in path separators, wildcards, and quoting for major platforms (Windows, Linux, macOS).
- Add at least one complete example using Linux-style paths (e.g., '/home/user/myDirectory/myTextFile.txt') for each command section.
- Consider alternating the order of examples so that Linux/macOS is not always secondary to Windows.
- Explicitly mention that AzCopy is cross-platform and highlight any platform-specific considerations.
Storage
Copy data from Amazon S3 to Azure Storage by using AzCopy
.../main/articles/storage/common/storage-use-azcopy-s3.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. In the section on setting AWS credentials, Windows (PowerShell and Command Prompt) commands are listed first, with Linux and macOS equivalents following. There is a specific note about quoting conventions that prioritizes Windows (cmd.exe) behavior. No Linux-specific tools or shell patterns are discussed, and all command examples use generic AzCopy syntax that works cross-platform. However, Windows-specific instructions and conventions are mentioned before Linux/macOS equivalents, and PowerShell is referenced explicitly.
Recommendations
- Present environment variable commands in alphabetical OS order (Linux, macOS, Windows) or group Linux/macOS together before Windows, to avoid Windows-first bias.
- Include Bash and zsh shell examples where relevant, especially for Linux/macOS users.
- Add a note clarifying that AzCopy works identically across platforms and highlight any platform-specific caveats equally.
- When discussing quoting conventions, lead with the cross-platform (single quotes) approach, then mention Windows (cmd.exe) as an exception.
- Consider providing a table or section that summarizes platform differences in usage, rather than embedding Windows-first notes.
Storage
Optimize the performance of AzCopy v10 with Azure Storage
...articles/storage/common/storage-use-azcopy-optimize.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally provides parity between Windows and Linux, especially in environment variable examples, but there is a subtle Windows bias. Windows-specific instructions (such as quoting conventions) are mentioned first and in more detail, and Windows Command Shell (cmd.exe) and PowerShell examples are given alongside Linux/bash, sometimes with Windows listed before Linux. The tip about quoting prioritizes Windows behavior, and Windows tools (cmd.exe, PowerShell) are referenced explicitly, while Linux equivalents are referenced generically as 'command shells'.
Recommendations
- Ensure Linux examples and instructions are presented before or alongside Windows examples, not after.
- Provide explicit Linux shell references (e.g., bash, zsh) rather than generic 'command shells'.
- Balance tips and notes so that Linux-specific behaviors are described with equal detail and prominence as Windows-specific ones.
- Where quoting conventions are discussed, start with the most common cross-platform convention (single quotes for bash/zsh, double quotes for Windows), and clarify both equally.
- Consider adding troubleshooting or usage notes specific to Linux environments (e.g., permissions, file system case sensitivity) to match the Windows-specific guidance.
Storage
Copy or move data to Azure Storage by using AzCopy v10
...main/articles/storage/common/storage-use-azcopy-v10.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows paths and examples are used exclusively in command samples (e.g., 'C:\local\path'), and the only concrete example command uses a Windows-style path. Linux equivalents (e.g., '/home/user/path') are not provided. Additionally, when describing how to run AzCopy, the documentation mentions Windows command shell conventions (e.g., '.\azcopy') before Linux/macOS equivalents, and the decompression instructions for Linux are less detailed than for Windows. Overall, Windows is prioritized in examples and instructions, while Linux-specific guidance is minimal or missing.
Recommendations
- Include Linux/macOS command examples alongside Windows examples, using appropriate path formats (e.g., '/home/user/path').
- When showing example commands, provide both Windows and Linux/macOS variants, or use generic placeholders.
- Mention Linux/macOS command shell conventions (e.g., './azcopy') equally and clearly alongside Windows conventions.
- Provide explicit instructions for decompressing tar files on Linux, similar to the detail given for Windows zip files.
- Ensure that installation, usage, and scripting guidance is platform-neutral or includes parity for all supported OSes.
Storage
Configure private endpoints for Azure Elastic SAN
...elastic-san/elastic-san-configure-private-endpoints.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for configuring private endpoints, but PowerShell (commonly used on Windows) is presented before CLI (more cross-platform). There are no Linux-specific shell (bash) examples, and no mention of Linux-native tools or workflows. The prerequisites and instructions reference PowerShell before CLI, which may suggest a Windows-centric approach.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Add bash script examples for Linux users, demonstrating environment variable usage and command chaining.
- Include notes or links to Linux-specific considerations, such as package managers for installing Azure CLI.
- Ensure parity in troubleshooting and approval steps for both PowerShell and CLI, and highlight CLI as the recommended approach for non-Windows environments.
Storage
Connect Azure Elastic SAN to Azure Kubernetes over iSCSI
...rticles/storage/elastic-san/elastic-san-connect-aks.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI commands for retrieving volume information, but lists PowerShell first and refers to it as a primary option. The prerequisites mention both Azure CLI and PowerShell, but PowerShell is listed second. There are no Linux-specific examples, but the use of Azure CLI (which is cross-platform) helps mitigate bias. No Windows-only tools or patterns are used elsewhere, and all Kubernetes commands are platform-neutral.
Recommendations
- List Azure CLI commands before Azure PowerShell commands, as CLI is more commonly used on Linux and is cross-platform.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, while PowerShell is primarily used on Windows.
- Add a note or example showing how to install and use Azure CLI on Linux, to encourage parity.
- If mentioning PowerShell, clarify its platform support and recommend CLI for Linux users.
- Ensure future documentation includes Linux-specific troubleshooting or usage notes if relevant.
Storage
Configure Service Endpoints for Azure Elastic SAN
...elastic-san/elastic-san-configure-service-endpoints.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for all major configuration steps, but PowerShell (which is most commonly used on Windows) is consistently listed before CLI, and the variable syntax in CLI examples uses Windows-style ($Var) rather than Linux-style (Var=). There are no explicit Linux shell examples (e.g., bash), and no mention of Linux-specific tools or patterns. The documentation assumes familiarity with PowerShell, which can be a barrier for Linux users. There is no explicit bias in terms of missing Linux functionality, but the ordering and example style favor Windows users.
Recommendations
- Alternate the order of PowerShell and CLI examples, or list CLI first to improve parity for Linux users.
- Use Linux shell variable syntax (e.g., Var="value") in CLI examples, or provide both Windows and Linux syntax.
- Add explicit bash shell examples for CLI commands, showing how to run them on Linux.
- Clarify that Azure CLI works cross-platform and provide guidance for Linux users where appropriate.
- Avoid assuming PowerShell as the default scripting environment; mention bash/zsh as alternatives for Linux.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation displays mild Windows bias by presenting Windows-specific instructions and scripts before Linux equivalents in the 'Disconnect volumes from clients' section. PowerShell examples are consistently shown before Azure CLI examples in all deletion operations, reinforcing a Windows-centric approach. However, Linux instructions and Azure CLI examples are present, providing reasonable parity.
Recommendations
- Alternate the order of Windows and Linux instructions to avoid implicit prioritization.
- Present Azure CLI examples before or alongside PowerShell examples to better support cross-platform users.
- Explicitly state that both Windows and Linux are equally supported, and highlight any platform-specific considerations.
- Ensure script descriptions and parameters are equally detailed for both platforms.
Storage
Use clustered applications on Azure Elastic SAN
...cles/storage/elastic-san/elastic-san-shared-volumes.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page references Windows Server Failover Cluster (WSFC) before Pacemaker when discussing cluster managers, and does not provide any concrete examples, scripts, or tooling for either Windows or Linux. However, the ordering and naming of Windows technologies first suggests a subtle Windows-first bias. There are no PowerShell-heavy sections or exclusive mentions of Windows tools, but Linux parity is lacking in terms of practical examples or guidance.
Recommendations
- Present cluster manager options in a neutral or alternating order (e.g., 'Pacemaker or Windows Server Failover Cluster (WSFC)').
- Add concrete examples or walkthroughs for both Windows (WSFC) and Linux (Pacemaker) cluster setups using Elastic SAN volumes.
- Include references to Linux-specific tools and commands for managing SCSI-3 Persistent Reservations.
- Provide sample scripts for both PowerShell (Windows) and Bash (Linux) to demonstrate attaching and managing shared volumes.
- Explicitly mention any differences or considerations for Linux environments, such as required packages or configuration steps.
Storage
Modify your Azure File Sync topology
...es/storage/file-sync/file-sync-modify-sync-topology.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation implicitly assumes a Windows environment throughout. It references Windows-specific concepts (such as drive letters and the D: drive), and does not provide any Linux-specific examples, guidance, or mention of Linux server endpoints. There are no PowerShell commands or Windows tools shown directly, but the only referenced VM guidance is for Windows. The lack of Linux parity may confuse or exclude users managing Azure File Sync on Linux servers.
Recommendations
- Add explicit guidance and examples for Linux server endpoints, including file path conventions and any differences in deprovisioning or reprovisioning steps.
- Include links to Linux VM documentation where relevant, similar to the Windows D: drive reference.
- Clarify whether all instructions apply equally to Linux servers, and note any platform-specific caveats.
- Provide sample commands or screenshots for Linux environments (e.g., using bash, Linux file system paths) alongside Windows examples.