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 1376-1400 of 1657 flagged pages
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 any Linux or macOS path examples. While there are notes about quoting differences between shells, the actual command examples and syntax always show Windows paths, and Linux/Unix-style paths are never demonstrated. This may make the documentation less approachable for Linux/macOS users.
Recommendations
- For each example using a Windows path (e.g., 'C:\myDirectory'), provide a parallel example using a Linux/macOS path (e.g., '/home/user/myDirectory').
- In the syntax sections, show both Windows and Linux/macOS variants, or use a placeholder like '<local-directory-path>' in the example and clarify with both path styles below.
- Consider alternating which platform is shown first, or present both at the same time, to avoid the appearance of Windows-first bias.
- Explicitly mention that AzCopy is cross-platform and provide links or notes about shell-specific behaviors for Linux/macOS users.
Create Pull Request
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/disable/restore soft delete). However, PowerShell examples are always presented before Azure CLI, and there are no explicit Linux shell (bash) or scripting examples outside of Azure CLI. The documentation assumes familiarity with PowerShell, which is more common on Windows, and does not mention or link to Linux-specific tools or workflows (e.g., Bash scripting, Cloud Shell usage on Linux).
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first, as it is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash).
- Add a short section or note for Linux users, highlighting that all Azure CLI commands can be run from Bash or other Linux shells, and provide links to Azure CLI installation instructions for Linux.
- Where possible, provide Bash script snippets or usage patterns (e.g., using environment variables, piping output) to demonstrate Linux-native workflows.
- Consider referencing Azure Cloud Shell, which provides a cross-platform, browser-based CLI experience, and is accessible from both Windows and Linux.
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 examples or guidance for Linux users, such as using Azure CLI, PowerShell Core (cross-platform), or REST APIs to accomplish the same tasks. The documentation also omits any mention of Linux-specific considerations or tools for integrating Commvault with Azure, and does not provide command-line alternatives that would be relevant for Linux administrators.
Recommendations
- Add parallel instructions and examples for Linux users, such as using the Azure CLI (az commands) to create storage accounts, containers, and manage access keys.
- Include sample scripts or command-line steps for both Windows (PowerShell) and Linux (Bash/Azure CLI) environments.
- Mention and link to REST API documentation for users who may wish to automate tasks in a platform-agnostic way.
- Explicitly state that the Azure Portal is accessible from any OS, but provide alternatives for users who prefer or require CLI-based workflows.
- Highlight any Linux-specific considerations for Commvault MediaAgent deployment or integration with Azure Storage.
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 PowerShell examples before Azure CLI, and the PowerShell tab is more detailed and prominent. There is no explicit mention of Linux or cross-platform considerations, and the use of PowerShell as the first and primary example may signal a Windows-centric approach. However, Azure CLI (which is cross-platform) is also covered, and no Windows-only tools or patterns are exclusively required.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to reflect its cross-platform nature.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
- Add a note clarifying that PowerShell Core is available cross-platform, if relevant, or recommend Azure CLI for Linux/macOS users.
- Ensure parity in detail and explanation between PowerShell and Azure CLI sections.
- Consider adding Bash shell examples or clarifying that Azure CLI commands can be run in Bash on Linux/macOS.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/snapshots-overview.md
...blob/main/articles/storage/blobs/snapshots-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page on Azure Blob snapshots does not provide any OS-specific command-line examples, but in the 'Next steps' section, it links only to a Windows-specific guide for backing up Azure unmanaged VM disks with incremental snapshots. There are no Linux or cross-platform equivalents mentioned or linked. Additionally, the mention of VHD files and VM disk detachment is presented in a way that implicitly assumes a Windows-centric context, as VHD is a format primarily associated with Windows environments.
Recommendations
- Add links to Linux-focused or cross-platform guides for managing blob snapshots and backing up VM disks, such as documentation for Azure Linux VMs or using AzCopy/CLI tools on Linux.
- When referencing VM disk formats, clarify support for both Windows (VHD) and Linux (VHD, VHDX, or other formats as appropriate), and provide examples relevant to both environments.
- In the 'Next steps' section, include parallel documentation for Linux users, such as 'Back up Azure unmanaged VM disks with incremental snapshots (Linux)' if available.
- Ensure that any best practices or operational guidance is not implicitly Windows-centric, and explicitly mention cross-platform tools (e.g., Azure CLI, AzCopy) with usage examples for both Windows and Linux.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-storage-monitoring-scenarios.md
...les/storage/blobs/blob-storage-monitoring-scenarios.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is generally cross-platform and avoids explicit Windows bias in most areas. However, in the section on decoding SAS token signatures, the PowerShell example is presented first, with the Linux/bash/python alternative only mentioned after. This ordering and inclusion of PowerShell as the primary example demonstrates a subtle 'windows_first' and 'powershell_heavy' bias.
Recommendations
- When providing code examples for tasks like decoding or hashing, present both Windows (PowerShell) and Linux (bash/python) examples together, or explicitly state that both are supported.
- Consider presenting the Linux/bash example first, or in parallel with the PowerShell example, to avoid the perception of Windows being the default environment.
- Where possible, use platform-agnostic tools or SDKs in examples (e.g., Azure CLI, Python scripts) that work equally well on Windows, Linux, and macOS.
- Add a note clarifying that all tasks can be performed on both Windows and Linux, and provide links to relevant cross-platform tooling documentation.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-storage-estimate-costs.md
.../articles/storage/blobs/blob-storage-estimate-costs.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page references AzCopy as the primary example utility for data transfer cost estimation, but does not mention or provide examples for Linux-native tools or cross-platform command-line usage. There are no PowerShell-specific examples, but the exclusive focus on AzCopy (which is cross-platform but often associated with Windows) and lack of explicit Linux/Unix tool references or examples (such as Azure CLI, REST API with curl, or scripting in bash) indicates a subtle Windows bias.
Recommendations
- Explicitly mention that AzCopy is available on Windows, Linux, and macOS, and provide installation instructions or links for all platforms.
- Include examples using Azure CLI (az storage blob ...), which is widely used on Linux and macOS, alongside AzCopy examples.
- Provide sample commands for common Linux tools (e.g., curl for REST API calls) to estimate or interact with Blob Storage.
- Clarify in each example that the commands and tools are cross-platform, and where relevant, show both Windows (cmd/PowerShell) and Linux (bash) command syntax.
- Add a section or note highlighting cross-platform options for cost estimation and data transfer, ensuring Linux users are equally supported.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-use-databricks-spark.md
...torage/blobs/data-lake-storage-use-databricks-spark.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation instructs users to 'open a command prompt window' and provides AzCopy CLI commands without specifying or illustrating that these commands work identically on Linux/macOS terminals. There are no explicit Linux (bash) or macOS terminal references, nor are there alternative instructions or screenshots for non-Windows environments. The phrase 'command prompt window' is a Windows-centric term, and the lack of cross-platform clarification may lead Linux/macOS users to feel excluded or uncertain.
Recommendations
- Replace 'command prompt window' with 'terminal window' or specify 'open a command prompt (Windows) or terminal (Linux/macOS) window'.
- Explicitly state that AzCopy is cross-platform and works on Windows, Linux, and macOS.
- Add a note or section confirming that the provided AzCopy commands are valid in bash/zsh shells on Linux/macOS, and that no syntax changes are required.
- If there are any platform-specific differences (e.g., path formats), highlight them with examples for both Windows and Linux/macOS.
- Consider including screenshots or terminal prompts (e.g., C:\> for Windows, $ for bash) to visually reinforce cross-platform support.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-static-website-terraform.md
...e/blobs/storage-quickstart-static-website-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell example is given equal prominence to the CLI, and there is no explicit mention of Linux or Bash shell usage. The CLI example uses generic shell syntax, but the PowerShell example is specifically called out, which may suggest a slight Windows bias. However, there are no overtly Windows-specific tools or missing Linux examples, as Terraform and Azure CLI are cross-platform.
Recommendations
- Explicitly mention that the Azure CLI example works on Linux, macOS, and Windows (in Bash or compatible shells), to reassure non-Windows users.
- Consider labeling the CLI tab as 'Bash or Azure CLI' to clarify its cross-platform nature.
- If possible, add a short note or example for macOS/Linux users to highlight parity and inclusivity.
- Ensure that any references to PowerShell are balanced by references to Bash or other common Linux shells, especially in multi-tabbed instruction sections.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/videos-azure-files-and-file-sync.md
...les/storage/common/videos-azure-files-and-file-sync.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by featuring a video specifically about mounting Azure file shares in Windows, while lacking any equivalent video or mention for mounting on Linux or macOS. Additionally, SMB workloads (commonly associated with Windows) are highlighted, but there is only a brief mention of NFS 4.1 (a Linux/UNIX protocol) without a corresponding 'how-to' video for Linux users. There are no explicit Linux examples or parity in the video topics.
Recommendations
- Add videos or documentation links that demonstrate how to mount Azure file shares on Linux and macOS, using both SMB and NFS protocols.
- Ensure that for every Windows-specific instructional video (e.g., mounting in Windows), there is a Linux (and optionally macOS) equivalent.
- Highlight Linux tools and command-line examples (such as mount.cifs, mount.nfs, or Azure CLI usage on Linux) alongside Windows/PowerShell examples.
- Balance the focus on SMB (Windows-centric) with more content on NFS and Linux/UNIX integration scenarios.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/last-sync-time-get.md
...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, the PowerShell example is presented first, which may suggest a Windows-first or PowerShell-preferred workflow. There are no explicit Linux-specific examples or notes, and the CLI example is generic but not tailored for Linux environments.
Recommendations
- Alternate the order of examples, sometimes presenting Azure CLI first, especially since Azure CLI is cross-platform and commonly used on Linux.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any Linux-specific notes if relevant (e.g., shell syntax differences).
- Consider adding a Bash shell example or clarifying that the Azure CLI example is suitable for Linux/macOS terminals.
- If PowerShell is included, clarify that PowerShell Core is also available on Linux and macOS, or provide a note about cross-platform compatibility.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/classic-account-migration-process.md
...es/storage/common/classic-account-migration-process.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation references both PowerShell and Azure CLI for migration, but consistently lists PowerShell (a Windows-centric tool) before Azure CLI in both the main migration options and in the links to further instructions. There are no explicit Linux-specific examples, and the documentation does not mention Bash, shell scripts, or Linux-native tools. This ordering and emphasis subtly prioritizes Windows/PowerShell users, which may make Linux users feel secondary.
Recommendations
- Alternate the order of PowerShell and Azure CLI references, or list Azure CLI first in some sections to balance perceived priority.
- Explicitly mention that both PowerShell and Azure CLI are cross-platform, and provide examples or links for both Windows and Linux environments.
- Include at least one example command or workflow using Azure CLI (preferably in Bash syntax) directly in the documentation, not just as a link.
- Add a note or section clarifying that all migration steps can be performed from Linux, macOS, or Windows, and provide any OS-specific caveats if relevant.
- Where possible, avoid phrasing that implies PowerShell is the default or primary method for migration.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/use-azurite-to-run-automated-tests.md
...es/storage/blobs/use-azurite-to-run-automated-tests.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows a Windows-first bias, particularly in the local Azurite setup instructions. The npm installation example uses Windows-style paths (e.g., c:\azurite) and does not provide equivalent Linux/macOS commands or path examples. There is no explicit Linux/macOS example for creating directories or launching Azurite with appropriate paths. While the Docker example is cross-platform, the primary non-Docker instructions assume a Windows environment. The Azure Pipelines section does use bash and Linux-style commands, but the local setup is Windows-centric.
Recommendations
- Provide parallel Linux/macOS command examples for installing and running Azurite, including directory creation and path usage (e.g., mkdir ~/azurite and --location ~/azurite).
- Clearly label which code blocks are for Windows and which are for Linux/macOS, or present both side by side.
- Avoid using only Windows-style paths in documentation; include POSIX-style paths where appropriate.
- Mention that Azure Storage Explorer is available on multiple platforms, and clarify any platform-specific steps if necessary.
- Ensure all steps (such as creating virtual environments and running commands) are shown with both Windows and Linux/macOS syntax where they differ.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/customer-managed-keys-configure-cross-tenant-existing-account.md
...r-managed-keys-configure-cross-tenant-existing-account.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples, but presents PowerShell (a Windows-centric tool) before Azure CLI, which is cross-platform. There are no explicit Linux shell or scripting examples, and the CLI example uses Bash syntax but is not labeled as such. There is a slight preference for Windows tooling and ordering.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux users.
- Explicitly label the CLI example as Bash/Linux compatible, and consider providing a Windows Command Prompt/Batch variant if needed.
- Add a note clarifying that Azure CLI commands work natively on Linux, macOS, and Windows.
- Where possible, include examples using native Linux tools or scripting (e.g., Bash), or clarify that the steps are platform-agnostic.
- Review all screenshots and UI instructions to ensure they are not Windows-specific, or provide Linux/macOS equivalents if applicable.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-explorer-sign-in.md
...in/articles/storage/common/storage-explorer-sign-in.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by listing Windows-specific authentication mechanisms (authentication broker) before Linux/macOS equivalents and recommending them primarily for Windows users. The 'authentication broker' is described as the default and recommended for Windows, while Linux and macOS are grouped together as using the default web browser. No Linux-specific troubleshooting or examples are provided, and the language and ordering subtly prioritize Windows patterns.
Recommendations
- Present sign-in methods for all platforms in parallel, rather than listing Windows first.
- Provide Linux-specific troubleshooting steps or notes if there are known issues or differences.
- Clarify whether all features (such as 'authentication broker' or 'integrated sign-in') are equally available and supported on Linux, and note any limitations.
- Include explicit Linux examples or screenshots where relevant to ensure parity.
- Avoid language that recommends or defaults to Windows-specific tools unless there is a technical requirement, and always provide Linux alternatives with equal prominence.
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, which is only supported on Windows servers, and all monitoring instructions reference the Azure portal or Azure Monitor without any mention of Linux-based tools or environments. There are no Linux-specific examples or guidance, and the documentation implicitly assumes a Windows Server environment.
Recommendations
- Explicitly state that Azure File Sync and its monitoring features are only supported on Windows Server, to clarify the platform limitation.
- If any monitoring or reporting can be done from Linux (e.g., via Azure CLI, REST API, or cross-platform tools), provide equivalent Linux command-line examples.
- Where possible, reference cross-platform Azure management tools (such as Azure CLI or REST API) alongside portal instructions.
- If Linux support is not available, add a clear note about the Windows-only nature of the feature to set expectations for Linux users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-encryption-manage-customer-keys.md
...tic-san/elastic-san-encryption-manage-customer-keys.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for all operations, but consistently lists PowerShell (a Windows-centric tool) before Azure CLI in every code tab and example. There are no Linux-specific shell examples (e.g., Bash scripts), and the CLI examples are generic, but the ordering and emphasis may suggest a preference for Windows/PowerShell users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or place Azure CLI first, as it is cross-platform and widely used on Linux.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific variable syntax in CLI examples where appropriate.
- Consider adding Bash script examples or notes for Linux users, especially for variable assignment and scripting differences.
- Clarify in introductory sections that both PowerShell and Azure CLI are supported on all major platforms, but that PowerShell examples use Windows-style syntax.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-explorers.md
...blob/main/articles/storage/common/storage-explorers.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page lists Microsoft client tools for Azure Storage, but it prioritizes Windows-specific tools (e.g., Visual Studio Cloud Explorer is Windows-only) and does not provide Linux-specific examples or mention Linux-native tools. While Azure Storage Explorer is cross-platform, the only other detailed client tool (Visual Studio Cloud Explorer) is exclusive to Windows, and there is no discussion of command-line or native Linux alternatives.
Recommendations
- Include command-line tools such as Azure CLI and AzCopy, both of which are cross-platform and widely used on Linux.
- Add explicit Linux usage examples or screenshots where possible.
- Mention Linux-native or open-source tools (even if third-party) that are commonly used to interact with Azure Storage.
- Reorder the presentation so that cross-platform tools are highlighted first, and Windows-only tools are clearly marked as such.
- Provide parity in documentation by including instructions or references for Linux users alongside Windows instructions.
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
Missing Linux Example
Windows First
Summary
The documentation does not provide any OS-specific proxy configuration examples or guidance, but implicitly assumes a Windows-centric perspective by referencing 'system proxy' and OS proxy settings without clarifying differences across platforms. There are no examples or instructions for configuring proxies on Linux or macOS, nor are there references to Linux-specific tools or patterns. The recommendation to use 'system proxy' is made without noting that proxy configuration methods differ significantly between Windows, Linux, and macOS.
Recommendations
- Add explicit instructions or references for configuring system proxy settings on Linux (e.g., using environment variables, GNOME/KDE network settings, or /etc/environment) and macOS (e.g., System Preferences > Network > Proxies).
- Include example commands or screenshots for setting environment variables on Linux and macOS, not just Windows.
- Clarify that the method for setting system proxy varies by OS, and provide links to relevant documentation for each platform.
- If mentioning NTLM or Negotiate authentication, note that these are primarily Windows technologies and may not be available or work differently on Linux/macOS.
- Ensure parity in troubleshooting steps and proxy authentication support notes for all supported platforms.
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 by referencing Windows-specific tools and patterns, such as comparing Azure Storage encryption to BitLocker (a Windows technology) and linking to the Windows Cryptography API: Next Generation (CNG) documentation. These references are made without mentioning Linux equivalents or cross-platform alternatives. However, the rest of the content is largely platform-neutral and does not provide command-line or code examples that are Windows- or PowerShell-specific.
Recommendations
- When drawing analogies, include Linux equivalents (e.g., compare Azure Storage encryption to both BitLocker on Windows and LUKS/dm-crypt on Linux).
- When referencing cryptographic APIs, mention cross-platform standards or Linux alternatives (e.g., OpenSSL, GnuPG, or Linux kernel crypto modules) alongside Windows CNG.
- Ensure that any future code or command-line examples are provided for both Windows (PowerShell/Command Prompt) and Linux (Bash/CLI), or use platform-agnostic Azure CLI examples.
- Explicitly state that Azure Storage encryption is platform-agnostic and does not require specific OS-level tools, to reassure Linux users.
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 page exhibits a subtle Windows bias, particularly in its use of Windows-style file paths (e.g., 'C:/path/to/directory') in code examples and the absence of explicit Linux/macOS examples or notes. While the Data Movement library is cross-platform and the .NET SDK is available for multiple operating systems, the documentation does not provide Linux or macOS-specific guidance, examples, or file path conventions. There is also no mention of platform-specific considerations or differences, which may leave Linux users without clear guidance.
Recommendations
- Provide code examples that use Linux/macOS-style file paths (e.g., '/home/user/path/to/directory') alongside or instead of Windows paths.
- Explicitly state that the Data Movement library and examples work on Linux and macOS, and mention any platform-specific considerations if applicable.
- Add a note or section in 'Set up your environment' clarifying cross-platform compatibility and how to adapt file paths for different operating systems.
- Wherever file paths are shown, use a variable or placeholder (e.g., '<local-directory-path>') and provide both Windows and Linux/macOS examples.
- If there are any known issues or differences in behavior on Linux/macOS, document them or link to relevant resources.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-files.md
...in/articles/storage/common/storage-use-azcopy-files.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, with no Linux or macOS path examples provided. While there are repeated notes about quoting differences between shells, every example defaults to Windows paths and syntax, and there are no explicit Linux (e.g., '/home/user/myDirectory/myTextFile.txt') or macOS examples. This may make the documentation less accessible or immediately usable for Linux/macOS users.
Recommendations
- For each example using a Windows path, provide a parallel example using a Linux/macOS path (e.g., '/home/user/myDirectory/myTextFile.txt').
- In each section, alternate the order of examples or explicitly show both Windows and Linux/macOS command lines.
- Add a dedicated section or callout early in the document that summarizes path and quoting differences, with concrete Linux/macOS examples.
- Where relevant, mention any OS-specific considerations (such as file permissions or environment variables) that may differ between Windows and Linux/macOS.
- Consider using environment variables or placeholders (e.g., <local-directory-path>) in examples, and then show both a Windows and a Linux/macOS instantiation.
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 page demonstrates a Windows-first bias in its examples and guidance for mounting and accessing Azure Files with .NET. While it mentions both Windows and Linux in the context of mounting SMB/NFS shares, all code examples and file path conventions use Windows-style paths (e.g., Z:\file-share), and there are no Linux-specific examples or file path formats. The mounting section references both OSes, but the practical, step-by-step code and usage scenarios are exclusively Windows-centric.
Recommendations
- Provide parallel Linux examples alongside Windows examples, especially for mounting file shares and accessing them via System.IO.
- Include Linux-style file paths (e.g., "/mnt/file-share") in code samples and explanations.
- Explicitly show how to enumerate directories, write files, and handle file locks on Linux-mounted shares, noting any differences or caveats.
- When referencing mounting instructions, give equal prominence to Linux and Windows, or present them in a neutral order.
- Add notes or callouts about cross-platform differences in file system permissions, locking, and path handling.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-download.md
...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 examples and does not provide any Linux/macOS path examples (e.g., '/home/user/myDirectory/myTextFile.txt'). While there are notes about quoting differences between shells, all concrete examples use Windows paths, which may confuse or alienate Linux/macOS users. No PowerShell-specific commands are present, but the documentation implicitly prioritizes Windows environments.
Recommendations
- For each example, provide both Windows and Linux/macOS path variants (e.g., show both 'C:\myDirectory\myTextFile.txt' and '/home/user/myDirectory/myTextFile.txt').
- Alternate or parallelize examples so that Linux/macOS paths are shown first in some sections, or at least equally.
- Add a section or table summarizing path and quoting conventions for Windows cmd, PowerShell, Linux bash, and macOS zsh.
- Explicitly state that AzCopy is cross-platform and provide links or tips for Linux/macOS installation and usage.
- Ensure that any references to file locations (such as the list-of-versions.txt) include both Windows and Linux-style paths.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-change-redundancy-configuration.md
...storage/files/files-change-redundancy-configuration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently lists the Azure portal, PowerShell, and Azure CLI as the primary methods for changing redundancy, always in that order. PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some cases, appears before it. While Azure CLI is cross-platform, the ordering and emphasis may suggest a Windows-first approach. There are no Linux-specific examples, nor is there mention of Linux-native tools or shell scripting patterns. The documentation does not provide parity for Linux users beyond the Azure CLI, and PowerShell is not explicitly marked as cross-platform (even though it can be).
Recommendations
- Alternate the order of PowerShell and Azure CLI in instructions and tables, or list Azure CLI first to reflect its cross-platform nature.
- Explicitly note that PowerShell Core is available cross-platform, or clarify when instructions are Windows-specific.
- Add Bash shell scripting examples or highlight Linux-native usage patterns where appropriate.
- Where possible, include references to Linux-native tools (e.g., AzCopy usage from Bash) or provide sample scripts for Linux environments.
- Ensure screenshots and UI walkthroughs are not Windows-centric (e.g., avoid only showing Windows-style UI elements if possible).