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 1201-1225 of 1657 flagged pages
Storage
Monitor Azure File Sync Cloud Tiering
...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 implicitly assumes a Windows environment by referencing 'server endpoints' and on-premises servers in the context of Azure File Sync, which is a Windows-only feature. There are no Linux-specific instructions, examples, or clarifications, and all operational guidance is inherently Windows-centric. No Linux tools, commands, or monitoring approaches are mentioned, and the documentation does not clarify the lack of Linux support.
Recommendations
- Explicitly state that Azure File Sync and its cloud tiering features are only supported on Windows Server, and clarify that Linux is not supported.
- If any Linux support is planned or available (e.g., via SMB clients or alternative monitoring), provide equivalent Linux instructions or examples.
- Where possible, use neutral language (e.g., 'on-premises server' vs. 'Windows server') and clarify platform requirements.
- If monitoring via Azure Monitor is cross-platform, provide examples or notes relevant to Linux-based clients or environments.
- Add a section or note addressing Linux users, explaining the current limitations and suggesting alternative solutions if applicable.
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows Server as the platform for Azure File Sync, with no mention of Linux or cross-platform alternatives. All performance and scalability guidance is framed around Windows Server, and there are no Linux examples, tools, or deployment patterns discussed.
Recommendations
- Explicitly state platform support and limitations (e.g., clarify if Azure File Sync is Windows-only or provide Linux alternatives if available).
- If Linux support exists or is planned, include equivalent Linux deployment instructions, examples, and performance considerations.
- Reference cross-platform tools or patterns where applicable, or suggest alternatives for Linux environments (such as using Azure Files directly with SMB/NFS on Linux).
- Add a section comparing Windows and Linux support for Azure Files and Azure File Sync, including any differences in scale targets or performance.
- If Azure File Sync is inherently Windows-only, make this clear early in the documentation to set expectations for Linux users.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation consistently provides examples for the Azure portal, Azure PowerShell, and Azure CLI, but PowerShell is always presented before CLI, and there are no Linux-specific shell or tool examples (e.g., Bash scripts, Linux utilities, or references to Linux desktop workflows). The use of PowerShell as the primary scripting language in examples may be more familiar to Windows users, while Linux users may prefer Bash or other shells. However, the CLI examples are cross-platform, and no Windows-only tools are mentioned.
Recommendations
- Add explicit Bash shell examples for Linux users, including variable assignment and command usage in typical Linux shell style.
- Include notes or sections highlighting cross-platform compatibility of Azure CLI, and clarify that CLI commands work natively on Linux and macOS.
- Where PowerShell is used, mention that PowerShell Core is available on Linux and macOS, or provide Bash alternatives.
- Consider reordering examples so that Azure CLI (which is cross-platform) appears before PowerShell, or alternate the order to avoid implicit prioritization.
- Add troubleshooting notes or tips relevant to Linux environments (e.g., permissions, environment variables, package installation).
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. In the 'Work with Azure Files using System.IO' section, all code examples use Windows-style paths (e.g., Z:\file-share) and reference mounting SMB shares on Windows first, with Linux mounting links provided but not exemplified. There are no Linux-specific code samples (e.g., using /mnt/file-share paths), nor any mention of Linux-specific behaviors or caveats. The initial example for mounting and accessing shares is Windows-centric, and Linux is only referenced as a secondary option via links.
Recommendations
- Provide Linux-specific code examples using Linux file paths (e.g., '/mnt/file-share') alongside Windows examples.
- Explicitly mention and demonstrate mounting Azure Files shares on Linux, including sample commands and code usage.
- Ensure parity in documentation order: present Windows and Linux instructions/examples together, or alternate which comes first.
- Discuss any platform-specific differences in file locking, ACLs, and other behaviors between Windows and Linux.
- Include troubleshooting or caveats for Linux environments, such as permissions, SELinux, or NFS-specific issues.
Storage
Use Kerberos authentication for Linux clients with Azure Files
...s/storage-files-identity-auth-linux-kerberos-enable.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is focused on Linux clients and provides detailed Linux-specific instructions. However, there is evidence of Windows bias: Windows Active Directory Domain Services (AD DS) is mentioned as the primary authentication source, and the documentation repeatedly refers to updating NT ACLs through Windows, stating that Linux tools for this are minimal. Windows tools and patterns (such as NT ACLs and AD DS) are referenced as the standard, with Linux alternatives described as limited or secondary. There are no Linux-first approaches to ACL management, and the guidance assumes a Windows-centric infrastructure.
Recommendations
- Provide more information about Linux-native tools for managing NT ACLs, even if limited, and reference any ongoing development or community projects.
- Explicitly mention and compare Linux alternatives to Windows AD DS, such as Samba AD or FreeIPA, where relevant.
- Offer guidance or workarounds for Linux users who need to manage ACLs without access to Windows tools.
- Clarify which steps are strictly required for Windows-based AD DS and which can be adapted for Linux-based domain controllers.
- Highlight any open-source or cross-platform utilities that can help bridge gaps in ACL management from Linux.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias, primarily through repeated references to Windows-specific concepts and tools, such as Volume Shadow Copy Service (VSS) and Azure File Sync (which is Windows-only). Windows is mentioned first and in more detail in the section on storage unit labeling, and Windows-centric terminology is used throughout. However, there are no command-line examples (PowerShell or otherwise) and the technical content is generally OS-neutral, focusing on Azure resource models and billing. Linux equivalents (e.g., Linux file sync, Linux snapshot tools) are not discussed, and the documentation does not address Linux-specific usage patterns or integration points.
Recommendations
- Add references to Linux tools and patterns where relevant, such as Linux snapshot mechanisms or third-party sync solutions.
- When discussing snapshots, mention Linux alternatives (e.g., LVM snapshots, rsync-based backups) and clarify how Azure Files integrates with Linux systems.
- Include examples or guidance for both Windows and Linux users, especially in sections that reference Windows-specific technologies (e.g., VSS, Azure File Sync).
- Balance OS mentions by listing Linux and macOS alongside Windows when discussing operating system behaviors or integration.
- If possible, provide parity in value-added services or note the lack of Linux equivalents, and suggest best practices for Linux environments.
Storage
Assign an Azure role for access to queue data
...ticles/storage/queues/assign-azure-role-data-access.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for assigning Azure roles using the Azure portal, PowerShell, Azure CLI, and ARM templates. However, the PowerShell example is given before the Azure CLI example, and PowerShell is a Windows-centric tool. There is no mention of Linux-specific tools or shell environments (e.g., Bash), nor are there any explicit Linux command-line examples or notes about cross-platform usage. The documentation implicitly assumes familiarity with PowerShell, which may disadvantage Linux users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
- Add explicit notes that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily a Windows tool (with cross-platform support, but less common on Linux).
- Include Bash shell examples or instructions for Linux users, especially for authentication and environment setup.
- Mention that Azure CLI can be installed and used natively on Linux, and provide links or references to installation guides for Linux.
- Avoid assuming PowerShell as the default scripting environment; clarify tool parity and usage scenarios for both Windows and Linux users.
Storage
Introduction to Azure Queue Storage
...articles/storage/queues/storage-queues-introduction.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Next steps' section, where all quickstart links reference tabs or environment variables specific to Windows (e.g., 'environment-variable-windows'). There is no mention of Linux or cross-platform equivalents, nor are Linux-specific instructions or examples provided. This may make it harder for Linux users to follow the documentation or feel equally supported.
Recommendations
- Add Linux-specific tabs and instructions to all quickstart guides, including environment variable setup and CLI usage.
- Ensure examples and screenshots reflect both Windows and Linux environments where applicable.
- Explicitly mention cross-platform compatibility and provide parity in tooling and setup steps.
- Review referenced quickstart pages to ensure Linux users are not excluded or forced to adapt Windows-centric instructions.
Storage
Quickstart: Azure Queue Storage client library for Java
...icles/storage/queues/storage-quickstart-queues-java.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. In the project creation section, Windows consoles (cmd, PowerShell) are mentioned before Bash, and the sample output uses Windows-style paths (e.g., C:\quickstarts\queues\queues-quickstart). There is no explicit Linux bias or missing Linux examples, but Windows tools and conventions are presented first and more prominently.
Recommendations
- Present Bash and Linux shell instructions before or alongside Windows cmd/PowerShell, or randomize the order.
- Include sample output using both Windows and Linux path formats, or use generic/universal paths.
- Explicitly mention cross-platform compatibility for all commands and outputs.
- Avoid referencing Visual Studio or Windows-specific tooling unless alternatives for Linux/macOS are also provided.
- Clarify that environment variable setup and usage applies equally to Linux/macOS shells (e.g., export AZURE_STORAGE_CONNECTION_STRING), and provide those commands where relevant.
Storage
Quickstart: Azure Queue Storage client library for JavaScript
...les/storage/queues/storage-quickstart-queues-nodejs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates mild Windows bias in the 'Setting up' section, where Windows consoles (cmd, PowerShell) are mentioned before Bash, and Visual Studio Code ('code .') is suggested as the editor without alternatives. No Linux-specific instructions or examples are provided, and the general workflow assumes familiarity with Windows tooling. However, most commands (npm, node) are cross-platform, and there are no PowerShell-specific scripts or Windows-only tools used.
Recommendations
- List Bash (Linux/macOS) before or alongside Windows consoles (cmd, PowerShell) when suggesting terminal options.
- Explicitly mention that all commands work on Linux/macOS and Windows, and provide any OS-specific caveats if needed.
- Suggest alternative editors (e.g., 'Open the project in your preferred editor, such as Visual Studio Code, Sublime Text, or Vim') rather than only 'code .'.
- Include a note or section confirming Linux/macOS compatibility and pointing to any relevant platform-specific documentation.
- If environment variable setup is discussed, clarify how to set them on Linux/macOS (e.g., 'export AZURE_STORAGE_CONNECTION_STRING=...') as well as on Windows.
Storage
Tutorial: Work with Azure Queue Storage queues in .NET
...ain/articles/storage/queues/storage-tutorial-queues.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently using Windows-specific command-line environments (cmd, PowerShell) in instructions and output examples, and by showing Windows-style file paths (e.g., C:\Tutorials). There are no explicit Linux or macOS terminal examples, nor any mention of platform-specific differences in commands, file paths, or environment setup. The tutorial assumes a Windows environment for running commands and viewing output, which may confuse or exclude Linux/macOS users.
Recommendations
- Include Linux/macOS terminal examples alongside Windows (e.g., show bash/zsh commands and output).
- Use platform-neutral file paths (e.g., ~/Tutorials/QueueApp instead of C:\Tutorials\QueueApp) or provide both Windows and Linux/macOS path formats.
- Explicitly mention that the .NET CLI and Visual Studio Code are cross-platform, and provide guidance for installing and running them on Linux/macOS.
- Add notes or sections highlighting any platform-specific differences in running the app, such as environment variables, authentication, or file system behavior.
- When referencing 'console window', clarify that this could be Command Prompt, PowerShell, Terminal (macOS), or Bash (Linux), and provide equivalent instructions for each.
Storage
Back up your data to Azure with Commvault
...isaster-recovery/commvault/commvault-solution-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently references the Azure portal and Commvault Command Center GUIs for configuration and management, which are platform-agnostic but typically accessed from Windows environments. There are no CLI or script-based examples for Linux users (e.g., Bash, Azure CLI, REST API, or Linux-specific Commvault tools). All operational guidance, troubleshooting, and setup instructions assume GUI access, with no mention of Linux command-line workflows or tools. No PowerShell bias is present, but the lack of Linux parity is notable.
Recommendations
- Add Linux-specific instructions for key steps, such as using the Azure CLI or REST API to create storage accounts, containers, and manage access keys.
- Include examples of integrating Commvault with Azure from Linux servers, such as using Commvault's CLI tools or scripts.
- Provide guidance for monitoring and troubleshooting using Linux-native tools (e.g., curl, jq, Azure CLI) alongside GUI methods.
- Explicitly mention platform compatibility for Commvault Command Center and Azure portal, and clarify any limitations or requirements for Linux users.
- Offer parity in operational guidance, such as opening support cases or configuring alerts, using Linux-based workflows.
Storage
Migrate your block data to Azure with Cirrus Data
...artners/data-management/cirrus-data-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific Azure VM guides and documentation links before Linux equivalents, and by omitting explicit Linux-focused step-by-step examples or links. While the main migration example uses a Linux source host, the supporting links and references prioritize Windows resources, and there is a lack of parity in Linux-specific guidance or troubleshooting.
Recommendations
- Include links to both Windows and Linux Azure VM quick start guides, ensuring Linux is represented equally.
- Add explicit step-by-step migration examples for both Windows and Linux hosts, or clarify that the process applies to both with relevant OS-specific details.
- Provide troubleshooting tips and verification steps for both Windows (e.g., using PowerShell or Windows tools) and Linux (e.g., using shell commands like iostat, lsblk, etc.).
- Ensure that references to Azure VM documentation and best practices are balanced between Windows and Linux, or use neutral, cross-platform documentation where possible.
Storage
Back up your data to Azure with DobiProtect
...-disaster-recovery/datadobi/datadobi-solution-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and screenshots for the Azure portal, which is most commonly accessed from Windows environments. There are no examples or guidance for Linux users, such as using Azure CLI, REST API, or Powershell Core on Linux. All operational and implementation steps assume use of the graphical Azure portal, with no mention of command-line alternatives or Linux-native tools. No Linux-specific considerations or parity examples are provided.
Recommendations
- Add equivalent instructions for using Azure CLI to create and manage storage accounts, containers, and access keys, including sample commands.
- Include examples of configuring DobiSync with Azure Blob Storage using Linux environments, such as referencing CLI or API usage.
- Mention cross-platform tools (e.g., Azure CLI, Powershell Core) and clarify their availability on Linux and macOS.
- Provide screenshots or terminal output for Linux workflows, not just Azure portal GUI.
- Reference Linux-native network monitoring tools (e.g., iftop, nload, vnstat) alongside Windows/GUI tools.
- Explicitly state that all steps can be performed from Linux systems and provide links to relevant Linux documentation.
Storage
Migrate data to Azure with Atempo Miria
...d-partners/data-management/atempo-quick-start-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed instructions and examples focused on migrating data from a Windows file server using SMB/CIFS shares, with explicit references to Windows Data Movers and Windows protocols. There are no equivalent examples or guidance for Linux-based sources (e.g., NFS shares, Linux Data Movers), nor are Linux tools or workflows mentioned. The documentation implicitly assumes a Windows-centric environment for migration tasks.
Recommendations
- Add equivalent examples and step-by-step instructions for migrating data from Linux file servers, such as using NFS shares as source storage.
- Include guidance on configuring Miria Data Movers on Linux platforms, with screenshots and configuration steps.
- Mention Linux-compatible network monitoring tools (e.g., iftop, nload, Netdata) alongside or before Windows-centric tools.
- Ensure protocol selection instructions cover both Windows (CIFS/SMB) and Linux (NFS) options, with parity in detail and screenshots.
- Clarify platform support in prerequisites, explicitly listing supported Linux distributions and versions.
Storage
Assign an Azure role for access to table data
...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 section is more detailed, which may indicate a Windows-first and PowerShell-heavy bias. While Azure CLI is cross-platform and included, there are no explicit Linux-specific instructions, nor are Linux shell patterns (e.g., bash, environment variables) mentioned. The documentation does not reference Windows-only tools, but the ordering and emphasis favor Windows users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to emphasize cross-platform parity.
- Add explicit notes or examples for Linux/macOS users, such as bash shell usage, environment variable substitution, or installation instructions for Azure CLI on Linux.
- Ensure that CLI examples use syntax and conventions familiar to Linux users (e.g., single quotes, environment variables).
- Clarify that both PowerShell and Azure CLI are available on Windows, Linux, and macOS, and provide links to installation guides for each platform.
- Consider adding a table comparing usage across platforms, or a section highlighting platform-agnostic approaches.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through the use of Windows-style file paths (e.g., C:\temp\) in all code samples and instructions. There are no Linux or macOS path examples, nor any mention of Linux-specific considerations for file paths, permissions, or environment setup. The XML sample also instructs users to place files in a Windows directory. Although the CLI commands themselves are cross-platform and Bash is used for scripting, the documentation implicitly assumes a Windows filesystem layout, which may confuse or inconvenience Linux/macOS users.
Recommendations
- Provide Linux/macOS path examples (e.g., /tmp/, ~/temp/) alongside Windows paths in all code samples and instructions.
- Explicitly mention that file paths should be adapted to the user's operating system, and clarify how to do so.
- Include a note or section on cross-platform usage, highlighting differences in file system conventions and shell environments.
- Where XML or other files are referenced, suggest both Windows and Linux/macOS locations.
- Consider providing example scripts for both Bash (Linux/macOS) and PowerShell (Windows) where relevant.
Storage
Quickstart: Deploy a static website on Azure Storage using Terraform
...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 examples for verifying results, but PowerShell is given equal prominence despite being primarily a Windows tool. There are no explicit Linux shell examples (e.g., bash), and PowerShell is presented as a main option, which may imply a Windows-centric approach. No Linux-specific tools or patterns are mentioned, and there is no guidance for Linux users beyond the Azure CLI.
Recommendations
- Add explicit bash/Linux shell examples alongside Azure CLI and PowerShell, especially for commands that involve environment variables or scripting.
- Clarify that Azure CLI commands work cross-platform and provide sample terminal output for both Windows and Linux.
- If PowerShell is included, note its availability on Linux and macOS, or clarify its typical usage context.
- Ensure that any instructions for opening files, directories, or browsers include both Windows and Linux/macOS approaches.
- Consider the order of tabs/examples: present Azure CLI (cross-platform) first, then bash, then PowerShell, to avoid Windows-first bias.
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 an Azure Resource Manager lock via the Azure portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, which may suggest a Windows-first approach. The PowerShell instructions reference the Az PowerShell module, a Windows-centric tool, and provide a detailed command example. While the Azure CLI example is present and cross-platform, there are no explicit Linux shell or scripting examples, nor is there mention of Linux-specific considerations. No Linux tools or patterns are discussed.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implicit Windows-first bias.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide example commands in bash/zsh syntax where appropriate.
- Consider adding Linux shell scripting examples or notes for users managing resources from Linux environments.
- Reference cross-platform tools and avoid assuming PowerShell as the default scripting environment.
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 refers to 'system proxy' and OS proxy settings without specifying or providing examples for Linux or macOS platforms. The authentication methods listed (NTLM, Negotiate) are Windows-centric, and there are no explicit instructions or examples for configuring proxies or certificates on Linux. The guidance prioritizes 'system proxy' (typically associated with Windows environments) as the recommended approach, with no mention of Linux-specific tools or patterns.
Recommendations
- Add explicit instructions and examples for configuring system proxy settings on Linux and macOS, including references to relevant desktop environments (e.g., GNOME, KDE) and CLI tools.
- Clarify how Storage Explorer interacts with system proxy settings on non-Windows platforms.
- Include Linux/macOS-specific authentication method support and limitations.
- Provide troubleshooting steps and certificate management guidance for Linux and macOS users.
- List Linux/macOS equivalents for proxy configuration, such as environment variable setup in shell profiles (.bashrc, .zshrc), and system-wide proxy configuration tools.
Storage
Customer-managed keys for account encryption
...icles/storage/common/customer-managed-keys-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally platform-neutral, focusing on Azure concepts and APIs. However, there are subtle signs of Windows bias: (1) PowerShell is mentioned as a tool to revoke customer-managed keys before Azure CLI, and (2) in the section about managed disk encryption, the link for Windows appears before the link for Linux. No Linux-specific examples, tools, or command-line patterns are provided, and there is no mention of Linux shell usage or parity in examples.
Recommendations
- When listing tools or command-line interfaces, mention Azure CLI before or alongside PowerShell, and provide example commands for both.
- Ensure that links to platform-specific documentation (e.g., disk encryption for Windows and Linux) are presented in a neutral order or grouped together.
- Include examples using Linux shell commands (bash) where relevant, especially for operations that can be performed via CLI.
- Explicitly state platform parity for all procedures, clarifying that steps apply equally to Windows, Linux, and macOS unless otherwise noted.
- Where PowerShell is referenced, add equivalent Azure CLI or bash examples to ensure Linux users are equally supported.
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 'Scripted or programmatic transfer' section and by featuring a PowerShell quickstart before the CLI quickstart in the 'Next steps'. While Linux-compatible tools like AzCopy and Azure CLI are mentioned, PowerShell is given prominence, and there are no explicit Linux-specific examples or references to Linux shell usage.
Recommendations
- Ensure equal prominence for Azure CLI and PowerShell by listing them together or alternating their order.
- Include explicit Linux shell (bash) examples alongside PowerShell examples where applicable.
- Add references to Linux tools and workflows, such as scripting with bash or using AzCopy on Linux.
- Clarify platform compatibility for each tool, noting which are cross-platform and which are Windows-specific.
- Provide links to Linux-specific quickstarts or documentation pages, especially for common data transfer scenarios.
Storage
Use Azure CLI to manage data (Azure Data Lake Storage)
...rage/blobs/data-lake-storage-directory-file-acl-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exhibits a mild Windows bias. In the prerequisites and setup sections, Windows PowerShell is mentioned explicitly as the example console application for running Azure CLI locally, with no mention of Linux or macOS terminal equivalents. Additionally, file path examples for upload and download operations use Windows-style paths (e.g., 'C:\myFolder\upload.txt') exclusively, with no Linux/macOS path examples provided. There are no references to Linux-specific tools, shells, or patterns, and no parity in file path examples.
Recommendations
- Mention Linux/macOS terminal applications (e.g., Bash, Terminal) alongside Windows PowerShell when instructing users to open a command console.
- Provide Linux/macOS file path examples (e.g., '/home/user/myFolder/upload.txt') alongside Windows paths in upload/download commands.
- Add a note clarifying that Azure CLI works equally well on Linux, macOS, and Windows, and link to platform-specific installation instructions.
- Where relevant, mention cross-platform considerations (e.g., path separators, shell differences) to help users on non-Windows systems.
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 (cross-platform), and provides detailed PowerShell instructions, including module installation and usage, while the Azure CLI section is less detailed. There are no Linux shell or Bash examples, nor is there mention of Linux-specific tools or workflows. This ordering and emphasis may unintentionally favor Windows users and workflows.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and widely used on Linux and macOS.
- Add Bash or shell script examples for Linux users, demonstrating how to use Azure CLI in typical Linux environments.
- Include notes or links for installing and using Azure CLI on Linux and macOS.
- Balance the level of detail between PowerShell and CLI sections, ensuring Linux users receive equally comprehensive guidance.
- Explicitly mention that Azure CLI works on Windows, Linux, and macOS to reinforce cross-platform parity.
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 mild Windows bias. In the section on setting AWS credentials, Windows (PowerShell and Command Prompt) instructions are listed first and in more detail, with Linux/macOS grouped together and presented after. There is a specific note about quoting conventions that prioritizes Windows Command Shell (cmd.exe) behavior, mentioning it before other shells. No Linux-specific tools or patterns are omitted, but Windows instructions are more prominent and detailed.
Recommendations
- Present operating system instructions in alphabetical order (e.g., Linux, macOS, Windows) or group Windows, Linux, and macOS equally.
- Provide equal detail for Linux and macOS shell instructions as for Windows (e.g., mention bash/zsh nuances if relevant).
- In notes about quoting conventions, mention Linux/macOS shell behavior first or equally, rather than focusing on Windows cmd.exe.
- Consider adding troubleshooting tips or examples for Linux/macOS environments, not just Windows.
- Ensure that all examples and syntax are tested and presented for bash/zsh as well as PowerShell/cmd.exe where differences exist.