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 1326-1350 of 1657 flagged pages
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/monitor-blob-storage-reference.md
...ticles/storage/blobs/monitor-blob-storage-reference.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page contains subtle Windows bias, notably in the sample 'userAgentHeader' field which references a Windows-based browser (Windows NT 10.0; Win64; x64) and Microsoft Edge. There are no explicit Linux or cross-platform examples, nor are Linux tools or patterns mentioned. No PowerShell or CLI examples are present, but the only concrete client example is Windows-centric. No Linux equivalents or parity are shown or referenced.
Recommendations
- Include sample user agent strings from Linux-based clients (e.g., curl on Ubuntu, Firefox on Linux) alongside or instead of Windows-based examples.
- Add explicit references to cross-platform tools (such as Azure CLI, Bash, curl) in examples and explanations.
- Ensure any example field values (e.g., userAgentHeader) rotate between Windows and Linux clients, or use generic values.
- If discussing SMB fields, clarify cross-platform SMB support and note Linux SMB client compatibility.
- Where authentication or logging examples are given, show how they would appear for Linux-based service accounts or applications.
Create Pull Request
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/secure-file-transfer-protocol-known-issues.md
...ge/blobs/secure-file-transfer-protocol-known-issues.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing a client configuration example only for WinSCP, a popular Windows SFTP client, without mentioning or giving equivalent instructions for common Linux SFTP clients (such as OpenSSH's sftp, lftp, or FileZilla). No Linux-specific tools, commands, or troubleshooting patterns are referenced, and Windows tooling is mentioned first and exclusively in the client settings section.
Recommendations
- Add configuration and troubleshooting examples for popular Linux SFTP clients (e.g., OpenSSH sftp, lftp, FileZilla).
- Include Linux command-line usage patterns for connecting to Azure Blob Storage via SFTP.
- Mention Linux-specific considerations (such as file permissions, symbolic link handling, and error messages) where relevant.
- Present client examples in a cross-platform manner, listing both Windows and Linux tools side-by-side.
- Avoid assuming WinSCP as the default client; provide parity for Linux and macOS environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/secure-file-transfer-protocol-support-how-to.md
.../blobs/secure-file-transfer-protocol-support-how-to.md
Medium 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 using the Azure Portal, PowerShell, and Azure CLI. PowerShell examples are given equal prominence to Azure CLI, and are presented before CLI examples in each section. This ordering and inclusion of PowerShell may indicate a slight Windows bias, as PowerShell is primarily a Windows tool (though cross-platform now), and Windows administrators are more likely to use it. There are no Linux-specific shell or tool examples (e.g., Bash scripts, native Linux commands), nor is there mention of Linux-specific patterns or considerations.
Recommendations
- Consider providing Bash script examples alongside PowerShell, especially for tasks that can be performed via Azure CLI, to better serve Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any relevant platform-specific notes (e.g., installation, authentication differences).
- If PowerShell is included, clarify that it is available cross-platform, but also highlight native Linux alternatives where appropriate.
- Review related content and next steps to ensure Linux users are equally supported (e.g., connecting from Linux SFTP clients, troubleshooting on Linux).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/secure-file-transfer-protocol-performance.md
...age/blobs/secure-file-transfer-protocol-performance.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by mentioning Windows tools (WinSCP) first and providing configuration details for them before referencing alternatives. In the section on optimizing message size, Windows/OpenSSH is described before Linux/OpenSSH, and the example for Windows uses a smaller buffer size than Linux, which could be confusing. There are no Linux-specific SFTP clients (such as lftp or Nautilus) mentioned, nor are Linux GUI tools discussed. The documentation does not provide parity in examples or tool recommendations for Linux users.
Recommendations
- Present Linux and Windows examples in parallel, or alternate which platform is mentioned first.
- Include examples and configuration details for popular Linux SFTP clients (e.g., lftp, Nautilus, GNOME Files, or command-line sftp).
- Clarify why buffer sizes differ between Windows and Linux OpenSSH examples, or provide guidance for both platforms.
- Mention cross-platform SFTP clients (e.g., FileZilla) with configuration instructions for both Windows and Linux.
- Avoid assuming the reader is using Windows-only tools; provide equal detail for Linux workflows.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/quickstart-blobs-javascript-browser.md
...s/storage/blobs/quickstart-blobs-javascript-browser.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by listing Windows-specific consoles (cmd, PowerShell) before Bash when instructing users to create project directories. Additionally, the prerequisites mention Visual Studio Code and Node.js, which are cross-platform, but do not reference any Linux-specific tools or editors. There are no explicit Linux or macOS command-line examples, nor are platform differences discussed. The instructions for running the app and opening the project in Visual Studio Code assume the 'code' command is available, which may not be the case by default on Linux/macOS. No Linux-specific troubleshooting or alternative workflows are provided.
Recommendations
- List Bash first or equally alongside cmd and PowerShell when referencing console windows.
- Explicitly mention that all commands work on Linux/macOS terminals, and provide notes for any platform-specific differences (e.g., installing Visual Studio Code or enabling the 'code' command).
- Include Linux/macOS-specific instructions or screenshots where relevant, such as file creation, directory navigation, and launching editors.
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, installing Node.js via package managers).
- Reference alternative editors (e.g., Vim, Sublime Text) or clarify that Visual Studio Code is optional.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/security-recommendations.md
...ain/articles/storage/blobs/security-recommendations.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page provides security recommendations for Azure Blob storage but does not include any platform-specific examples or instructions. There is no mention of Windows, PowerShell, Linux, Bash, or CLI tools. However, the absence of any command-line examples or platform-specific guidance means Linux users do not see parity with Windows users, who are often provided with PowerShell or GUI instructions in other Azure docs. The documentation implicitly assumes use of Azure Portal or generic Azure tools, which are more familiar to Windows users, and does not reference Linux-friendly tools or workflows.
Recommendations
- Add example commands using Azure CLI (az), which is cross-platform and commonly used on Linux.
- Include Bash script snippets for automating security configurations.
- Explicitly mention that all recommendations can be implemented from Linux, macOS, or Windows using Azure CLI or REST API.
- Where relevant, provide both PowerShell and Bash/CLI examples for configuration steps.
- Reference Linux-native tools (such as curl for REST API calls) where appropriate.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/simulate-primary-region-failure.md
...icles/storage/blobs/simulate-primary-region-failure.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates a moderate Windows bias. Fiddler, a Windows-only tool, is presented as a primary method for simulating failures, with no Linux equivalent suggested. In command-line instructions, Windows commands and terminology (elevated command prompt, ipconfig) are mentioned first or alongside Linux equivalents, but Linux is not prioritized. The tutorial assumes access to Windows-specific tooling and patterns, which may disadvantage Linux users.
Recommendations
- Provide Linux alternatives to Fiddler, such as mitmproxy or similar proxy tools, with equivalent step-by-step instructions.
- When listing command-line instructions, alternate the order or present Linux commands first in some sections to balance visibility.
- Explicitly mention Linux-specific prerequisites and tools where appropriate, ensuring parity in guidance and troubleshooting.
- Include screenshots or examples using Linux desktop environments and terminal applications.
- Add notes clarifying platform-specific differences, and link to external resources for Linux users where Windows-only tools are referenced.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-event-overview.md
.../articles/storage/blobs/storage-blob-event-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page lists quickstart articles for Azure portal, PowerShell, and Azure CLI, with PowerShell (a Windows-centric tool) featured prominently. PowerShell is mentioned before Azure CLI, which is more cross-platform and commonly used on Linux/macOS. No Linux-specific shell examples (e.g., Bash) are provided, and there is no mention of Linux tools or patterns. The documentation does not provide parity in examples or guidance for Linux users.
Recommendations
- List Azure CLI examples before PowerShell, as CLI is cross-platform and widely used on Linux.
- Add explicit Bash or Linux shell examples for common tasks, such as subscribing to events or filtering.
- Include references to Linux-native tools or workflows where relevant.
- Clarify that all Azure CLI commands work on Linux, macOS, and Windows, and provide platform-specific notes if needed.
- Consider adding a section or note for Linux users, highlighting any differences or best practices.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/customer-managed-keys-overview.md
...icles/storage/common/customer-managed-keys-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias. It references PowerShell as a tool for revoking access to customer-managed keys, listing it before Azure CLI, and does not mention Linux-specific tools or shell environments. Additionally, in the section about managed disk encryption, the link for Windows is listed before Linux, suggesting a Windows-first ordering. There are no explicit Linux examples, nor is there mention of Linux command-line patterns (e.g., Bash), and no guidance for Linux users on using Azure CLI or other cross-platform tools.
Recommendations
- Provide explicit examples using Azure CLI and Bash, especially for key management and revocation operations.
- List Azure CLI before PowerShell when referencing cross-platform command-line tools, or mention both together with equal prominence.
- Add notes or sections clarifying that all operations can be performed from Linux environments using Azure CLI.
- Ensure parity in documentation links and ordering for Windows and Linux, such as listing Linux and Windows managed disk encryption documentation together or in alphabetical order.
- Where PowerShell is referenced, clarify its availability on Linux, or provide equivalent Bash/CLI commands.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-performance-checklist.md
...rticles/storage/blobs/storage-performance-checklist.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by recommending network monitoring tools (WireShark or NetMon) where NetMon is a Windows-only tool, and by referencing AzCopy without clarifying its cross-platform availability or providing Linux-specific alternatives or usage examples. There are no explicit Linux examples or mentions of Linux-native tools for network monitoring or data transfer.
Recommendations
- When listing network monitoring tools, include Linux-native options such as tcpdump or iftop alongside WireShark.
- Clarify that AzCopy is available for both Windows and Linux, and provide example commands for both platforms.
- Avoid mentioning Windows-only tools (NetMon) without Linux equivalents, or at least provide parity by listing comparable Linux tools.
- Where relevant, include platform-specific guidance or troubleshooting tips for both Windows and Linux environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-choose-data-transfer-solution.md
...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 as a primary scriptable tool and referencing a PowerShell quickstart before the Azure CLI equivalent in the 'Next steps' section. While both Windows and Linux tools (PowerShell and CLI) are mentioned, PowerShell is given precedence, and there is no explicit mention of Linux-specific patterns or tools (e.g., Bash scripting, rsync, etc.).
Recommendations
- Ensure that Azure CLI examples and quickstarts are presented alongside or before PowerShell examples, as CLI is cross-platform and widely used on Linux.
- Explicitly mention Linux compatibility and usage patterns for tools like AzCopy and Azure CLI.
- Include references to Linux-native scripting (e.g., Bash) and data transfer utilities when discussing programmatic or scripted transfers.
- Add links to Linux-specific documentation or tutorials where appropriate.
- Clarify that Azure CLI and AzCopy are fully supported on Linux and macOS, not just Windows.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-explorer-network.md
...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 in Azure Storage Explorer but does not provide any OS-specific examples or guidance. The 'system proxy' option is recommended first, but there is no mention of how to configure system proxy settings on different platforms (Windows, Linux, macOS). The authentication methods listed include NTLM and Negotiate, which are Windows-centric, and there is no discussion of Linux/macOS equivalents or limitations. No Linux-specific tools, commands, or environment variable patterns are mentioned.
Recommendations
- Add explicit examples for configuring system proxy settings on Windows, Linux, and macOS (e.g., Windows Internet Options, Linux environment variables or GNOME/KDE network settings, macOS Network Preferences).
- Clarify which authentication methods are supported on each OS, especially noting that NTLM and Negotiate are Windows-specific and may not work on Linux/macOS.
- Provide troubleshooting steps or links for proxy and certificate issues on Linux and macOS, not just generic guidance.
- Include screenshots or step-by-step instructions for proxy configuration on non-Windows platforms.
- Mention any platform-specific limitations or differences in proxy and certificate handling.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/sas-expiration-policy.md
.../main/articles/storage/common/sas-expiration-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents configuration instructions in the order: Azure portal, PowerShell, then Azure CLI. PowerShell is a Windows-centric tool, and its example is given before the cross-platform Azure CLI. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux tools or patterns. The CLI example is present, but PowerShell is prioritized, which may signal a Windows bias.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux and macOS.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Add Bash shell script examples for common operations, especially for verification steps.
- Include notes or links for Linux users regarding installation and usage of Azure CLI.
- Avoid implying PowerShell is the default or preferred automation tool; clarify parity between CLI and PowerShell.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-srp-dotnet-get-started.md
...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 management tool alongside Azure CLI and Azure Portal, but does not provide any Linux-specific examples or mention Linux shell commands (e.g., Bash) for project setup or authentication. All code examples are in C# and use .NET CLI commands, which are cross-platform, but there is no explicit guidance or reassurance for Linux users regarding environment setup or parity of experience. The documentation does not mention platform-specific differences or provide Linux-centric instructions, which may leave Linux users uncertain about compatibility or best practices.
Recommendations
- Explicitly state that .NET SDK and CLI commands work on Linux, macOS, and Windows.
- Provide example commands for common Linux shells (e.g., Bash, zsh) when discussing environment variable setup for authentication.
- Include links or notes about installing .NET SDK on Linux distributions.
- When referencing management tools, clarify that Azure CLI is cross-platform and provide example usage in Bash or other Linux shells.
- Add a section or note reassuring Linux users that all steps and code samples are fully supported on Linux.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-optimize.md
...articles/storage/common/storage-use-azcopy-optimize.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for setting environment variables, but Windows-specific guidance (such as quoting conventions for cmd.exe) is given before Linux equivalents. Windows tools (cmd.exe, PowerShell) are mentioned explicitly, and instructions for quoting are presented with Windows first. The environment variable examples use PowerShell syntax for Windows, which may not be the most common shell for all Windows users. There are no missing Linux examples, and Linux-specific optimization (concurrent scanning) is included, but overall, Windows is prioritized in explanations and examples.
Recommendations
- Present Linux and Windows instructions in parallel tabs or sections, ensuring neither is prioritized in order or detail.
- When discussing quoting conventions, mention Linux and Windows shells together, or start with Linux if usage statistics favor it.
- Provide examples for both bash (Linux/macOS) and cmd.exe (Windows), not just PowerShell, as cmd.exe is still widely used.
- Ensure that any Windows-specific advice is matched with equivalent Linux/macOS advice where applicable.
- Consider adding macOS-specific notes if relevant, as AzCopy is cross-platform.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-properties-metadata.md
...common/storage-use-azcopy-blobs-properties-metadata.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates mild Windows bias by referencing Windows Command Shell (cmd.exe) specifically and providing quoting guidance for Windows before Linux/macOS shells. There are no Linux-specific examples, nor is there mention of Linux tools or shell patterns beyond quoting. All examples use generic AzCopy commands, which are cross-platform, but the only shell-specific advice is for Windows users.
Recommendations
- Add explicit Linux/macOS example commands, showing usage in Bash or other common shells.
- Provide shell-specific notes for Linux/macOS users, such as handling environment variables, escaping, or piping output.
- Mention Linux installation instructions or troubleshooting steps alongside Windows guidance.
- Ensure that any shell or OS-specific advice is presented in parallel (e.g., 'For Windows, do X; for Linux/macOS, do Y') rather than Windows-first.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-authorize-user-identity.md
...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 and Azure CLI usage, but Windows (PowerShell) examples are consistently listed after Linux (bash) examples. However, the Azure PowerShell section is presented as a distinct method, with no Linux equivalent or mention of cross-platform alternatives, which may suggest a slight bias toward Windows tooling. The documentation does not exclusively use Windows tools, but does give PowerShell its own section and does not mention Linux-native equivalents for PowerShell scenarios.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, or provide guidance for Linux users who may not use PowerShell.
- Where PowerShell is referenced, mention alternatives for Linux users (e.g., using Azure CLI or bash scripting).
- Ensure parity in examples by explicitly stating that all methods are available on both Windows and Linux, or by providing platform-specific notes.
- Consider listing Linux and Windows examples side-by-side or in a more balanced manner, rather than always listing Linux first.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-s3.md
.../main/articles/storage/common/storage-use-azcopy-s3.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. In the section on setting AWS credentials, Windows (PowerShell and Command Prompt) instructions are listed first and in greater detail, while Linux and macOS are grouped together and presented after Windows. There is also a specific note about quoting conventions in Windows Command Shell (cmd.exe), which is called out separately from other shells. No Linux-specific tools or patterns are missing, but the ordering and specificity favor Windows users.
Recommendations
- Present operating system instructions in alphabetical order (Linux, macOS, Windows) or group Linux/macOS together and Windows separately, but avoid listing Windows first by default.
- Provide equal detail for Linux and macOS instructions as for Windows (e.g., mention shell differences if relevant).
- Where shell quoting conventions are discussed, consider a table or a more neutral phrasing that covers all platforms equally, rather than focusing on Windows exceptions.
- Add explicit notes or examples for common Linux/macOS shell environments (e.g., bash, zsh) if any platform-specific behavior is relevant.
- Ensure that troubleshooting and optimization sections include platform-agnostic advice or highlight any platform-specific steps for Linux/macOS as well as Windows.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-synchronize.md
...storage/common/storage-use-azcopy-blobs-synchronize.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') in all examples and does not provide Linux/macOS equivalents (e.g., '/home/user/myDirectory'). The guidance for quoting paths prioritizes Windows Command Shell (cmd.exe) in every tip, but does not show Linux-specific command examples or mention Linux shells (bash, zsh) explicitly. There are no Linux or macOS sample commands or screenshots, and the documentation does not demonstrate AzCopy usage in a cross-platform manner.
Recommendations
- Provide parallel examples using Linux/macOS-style paths (e.g., '/home/user/myDirectory') alongside Windows examples.
- Explicitly mention Linux/macOS shells (bash, zsh) in tips about quoting and command syntax.
- Add notes or sections describing any platform-specific considerations for AzCopy usage (e.g., installation, permissions, environment variables) on Linux/macOS.
- Include screenshots or terminal output from Linux/macOS environments to demonstrate parity.
- Ensure that all flags and options are described in a way that is platform-neutral, or clarify any differences.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-service-encryption.md
.../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. It references BitLocker encryption on Windows as a comparison for Azure Storage encryption and links to the Windows-specific Cryptography API: Next Generation (CNG) documentation for more information about cryptographic modules. No equivalent Linux tools or APIs (such as LUKS or dm-crypt) are mentioned, nor are Linux-specific cryptography resources provided. The examples and SDKs listed are cross-platform (mentioning .NET, Java, Python), and there are no PowerShell-only instructions or examples, but the conceptual framing and external references favor Windows technologies.
Recommendations
- Include references to equivalent Linux disk encryption technologies (e.g., LUKS, dm-crypt) when making comparisons to BitLocker.
- Provide links to cross-platform or Linux-specific cryptography documentation (such as OpenSSL or Linux kernel cryptography modules) alongside Windows CNG.
- Ensure that conceptual explanations and external references are balanced between Windows and Linux, especially when discussing underlying cryptographic technologies.
- If mentioning Windows tools or APIs, add brief notes or links about how similar functionality is achieved on Linux.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-upload.md
...cles/storage/common/storage-use-azcopy-blobs-upload.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/macOS equivalents (e.g., '/home/user/myTextFile.txt'). While there are tips about quoting conventions for different shells, all concrete examples are Windows-centric, and Linux paths or shell usage are never shown. This can make the documentation less accessible or immediately useful for Linux/macOS users.
Recommendations
- For each example, provide both Windows and Linux/macOS versions, using appropriate path formats (e.g., 'C:\myDirectory\myTextFile.txt' and '/home/user/myTextFile.txt').
- Explicitly show command examples for Linux/macOS shells (bash/zsh), including correct quoting and wildcard usage.
- Add a section or table summarizing differences in path formats and shell quoting between Windows (cmd.exe, PowerShell) and Linux/macOS (bash/zsh).
- Ensure parity in instructions and examples for all supported platforms, not just Windows.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-v10.md
...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 shows mild Windows bias. The only example command for copying data uses a Windows-style path (C:\local\path), with no Linux/macOS equivalent. In the 'Download a portable binary' section, Windows download links are listed before Linux and macOS. There are no explicit Linux shell command examples (e.g., using /home/user/path or tar extraction commands), and instructions for decompressing the tar file on Linux are deferred to external documentation. The guidance for adding AzCopy to the system path mentions Windows conventions (e.g., .\azcopy) but does not provide Linux-specific equivalents (e.g., ./azcopy or export PATH).
Recommendations
- Provide parallel Linux/macOS command examples alongside Windows examples, especially for file paths (e.g., '/home/user/path').
- Include explicit Linux/macOS instructions for decompressing tar files and adding AzCopy to the PATH (e.g., 'export PATH=$PATH:/path/to/azcopy').
- List download links in a neutral or rotating order, or group them by OS rather than listing Windows first.
- Where shell usage is mentioned, clarify differences in invocation (e.g., './azcopy' for Linux/macOS, '.\azcopy' for Windows).
- Ensure that all examples and instructions are provided for both Windows and Linux/macOS users to achieve parity.
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 both Azure PowerShell and Azure CLI examples for configuring private endpoints, but the PowerShell example is listed before the CLI example. This ordering can subtly favor Windows users, as PowerShell is more commonly used on Windows. There is no explicit mention or example of Linux-specific tools or shell environments (e.g., bash), nor is there any reference to Linux command-line patterns. The CLI example is generic and cross-platform, but the documentation does not clarify that CLI commands work natively on Linux/macOS. The prerequisites mention PowerShell before CLI, and there is no explicit parity statement for Linux users.
Recommendations
- List Azure CLI examples before PowerShell to avoid implicit Windows-first bias.
- Explicitly state that Azure CLI commands work natively on Linux and macOS, and provide example shell environments (e.g., bash).
- Add a note clarifying that PowerShell is available cross-platform, but is most commonly used on Windows, while Azure CLI is natively supported on Linux/macOS.
- Include Linux-specific context or troubleshooting notes where relevant.
- Ensure that any screenshots or UI references do not assume a Windows environment.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-scale-targets.md
.../articles/storage/file-sync/file-sync-scale-targets.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page for Azure File Sync is heavily focused on Windows Server, with all examples and explanations assuming deployment on Windows. There is no mention of Linux support, Linux equivalents, or cross-platform considerations. The product itself is described as extending Azure Files to Windows Server, and all performance metrics and deployment guidance are Windows-centric.
Recommendations
- Explicitly state platform limitations or support, including whether Linux is supported or not.
- If Linux support exists or is planned, provide equivalent examples, deployment guidance, and performance metrics for Linux environments.
- Include a comparison table or section that highlights differences between Windows and Linux deployments, if applicable.
- If Azure File Sync is Windows-only, clarify this early in the documentation to set user expectations and avoid confusion.
- Reference any alternative solutions for Linux users who need similar functionality.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists both Azure PowerShell and Azure CLI as prerequisites, but consistently presents the Azure PowerShell command before the Azure CLI equivalent when showing how to retrieve volume information. This ordering and explicit mention of PowerShell may suggest a subtle Windows-first bias, as PowerShell is primarily associated with Windows environments. No Linux-specific tools or shell examples (e.g., bash scripting, Linux package installation) are provided, though the core workflow is cross-platform.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is more commonly used on Linux and macOS.
- Explicitly mention that all commands (except PowerShell) are cross-platform and runnable on Linux, macOS, and Windows.
- Add a note or section highlighting Linux-specific considerations, such as iSCSI package installation (e.g., open-iscsi) on AKS nodes if manual setup is needed.
- Where possible, provide bash script snippets or Linux shell commands for common tasks.
- Clarify that PowerShell is optional and primarily for Windows users, while Azure CLI is recommended for Linux/macOS.