Storage
1359
Total Pages
1162
Linux-Friendly Pages
197
Pages with Bias
14.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
392 issues found
Showing 201-225 of 392 flagged pages
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides extensive PowerShell examples and instructions, which are most commonly used on Windows. PowerShell is presented as a primary automation method alongside Azure CLI, but file path examples and instructions (e.g., 'C:\temp\json.txt') are Windows-centric. There is a lack of explicit parity for Linux/macOS users in PowerShell sections, and Windows-style file paths are used before mentioning cross-platform alternatives. However, Azure CLI examples are present and generally cross-platform, reducing the overall severity.
Recommendations
- Explicitly state that PowerShell Core is available on Linux/macOS and provide equivalent Linux/macOS instructions (e.g., file paths like '/tmp/json.txt').
- Add notes or examples for Linux/macOS users in PowerShell sections, including installation instructions for PowerShell Core.
- When showing file paths, use both Windows and Linux/macOS formats, or use environment variables to indicate cross-platform compatibility.
- Consider listing Azure CLI examples before PowerShell, as CLI is more universally available across platforms.
- Add troubleshooting or FAQ sections for common Linux/macOS issues (e.g., authentication, file permissions).
Create Pull Request
Storage
Limitations & known issues with SFTP in Azure Blob Storage
...ge/blobs/secure-file-transfer-protocol-known-issues.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by exclusively mentioning WinSCP (a Windows SFTP client) in the client settings section, with no reference to Linux/macOS SFTP clients or their settings. No Linux or cross-platform client configuration examples are provided, which may leave Linux/macOS users without guidance for optimal configuration or troubleshooting.
Recommendations
- Add configuration guidance for popular Linux/macOS SFTP clients (e.g., OpenSSH's sftp, FileZilla, Cyberduck).
- Include troubleshooting tips or known issues for Linux/macOS clients.
- Present client examples for both Windows and Linux/macOS platforms to ensure parity.
- List any Linux/macOS-specific limitations or workarounds if applicable.
Storage
Quickstart: Azure Blob Storage library - C++
...articles/storage/blobs/quickstart-blobs-c-plus-plus.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The project setup instructions focus on Visual Studio and Windows-specific project files (.sln), with screenshots and steps for creating a Windows console app. The initial example for installing packages uses the Windows executable (vcpkg.exe), and environment variable instructions list Windows first. There is no guidance for Linux/macOS IDEs or project creation, and the workflow assumes a Windows development environment throughout.
Recommendations
- Add explicit instructions for setting up a C++ project on Linux/macOS, including using CMake or other cross-platform build systems.
- Provide screenshots and steps for popular Linux/macOS IDEs (e.g., CLion, VS Code) or command-line workflows.
- Show vcpkg usage with cross-platform commands (e.g., './vcpkg install ...') and clarify platform differences.
- Present environment variable setup for Linux/macOS before or alongside Windows, rather than after.
- Remove or supplement Visual Studio-specific instructions with cross-platform alternatives.
- Clarify that the SDK and examples work on Linux/macOS and provide troubleshooting tips for those platforms.
Storage
Connect to Azure Blob Storage from an SFTP client
...blobs/secure-file-transfer-protocol-support-connect.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing only a Windows PowerShell example for connecting to Azure Blob Storage via SFTP, referencing Windows-specific OpenSSH documentation, and omitting explicit Linux/macOS terminal examples. The initial connection instructions are Windows-centric, which may cause friction for Linux/macOS users.
Recommendations
- Add explicit Linux/macOS terminal examples (e.g., using the 'sftp' command in bash/zsh).
- Reference Linux/macOS OpenSSH documentation alongside Windows.
- Present connection examples for multiple platforms in parallel, or use platform-neutral syntax first.
- Clarify that the instructions apply to all platforms and highlight any platform-specific considerations.
Storage
Tutorial - Simulate a failure in reading data from the primary region
...icles/storage/blobs/simulate-primary-region-failure.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation demonstrates notable Windows bias by recommending Fiddler—a Windows-only tool—for simulating failures, and by presenting Windows command-line examples and terminology first or equally, even when Linux alternatives exist. The static route method does provide both Linux and Windows commands, but Fiddler is described as a primary method without mentioning Linux/macOS equivalents. The instructions for launching Fiddler and customizing its rules are Windows-centric, with no guidance for Linux/macOS users.
Recommendations
- Provide equivalent instructions for Linux/macOS users for the Fiddler method, or recommend cross-platform tools such as mitmproxy or Charles Proxy.
- Explicitly mention platform compatibility for each tool and method.
- Present Linux/macOS examples before or alongside Windows examples to avoid implicit prioritization.
- Include screenshots or steps for Linux/macOS alternatives where applicable.
- Clarify any limitations or required adaptations for non-Windows platforms.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is featured prominently as a primary automation method, and instructions for using the Azure CLI reference Windows PowerShell as the example console application. In several places, Windows tools and terminology (e.g., PowerShell, Windows PowerShell) are mentioned before or instead of Linux/macOS equivalents. However, Azure CLI and template methods are also provided, which are cross-platform, and most steps can be completed on Linux/macOS with minor adjustments.
Recommendations
- When referencing command consoles for Azure CLI, mention cross-platform options such as Bash, zsh, or Terminal on macOS and Linux, not just Windows PowerShell.
- Provide explicit examples or notes for running CLI commands on Linux/macOS, including any differences in syntax or prerequisites.
- Balance PowerShell and CLI coverage by ensuring CLI examples are as detailed and prominent as PowerShell examples.
- Avoid language that implies PowerShell is the default or preferred method for automation; clarify that both CLI and PowerShell are supported on all platforms.
- Where PowerShell modules are discussed, note their availability and usage on Linux/macOS (e.g., via PowerShell Core).
Storage
Example Azure role assignment conditions for Blob Storage
...n/articles/storage/blobs/storage-auth-abac-examples.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed Azure PowerShell examples for every scenario, including setup, condition assignment, and testing, but does not offer equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or cross-platform scripting). All command-line examples are PowerShell-centric, and there is no mention of Azure CLI or Bash alternatives. This creates friction for users on non-Windows platforms who may not have PowerShell installed or prefer native tools.
Recommendations
- Add Azure CLI examples for each scenario alongside PowerShell, showing equivalent commands for condition assignment and testing.
- Explicitly mention that Azure PowerShell is available cross-platform, but provide Bash or shell scripting examples for Linux/macOS users.
- Include notes or links to installing and using Azure PowerShell on Linux/macOS, or recommend Azure CLI as a first-class alternative.
- Where possible, show both PowerShell and CLI/Bash examples in tabs, allowing users to select their preferred environment.
- Review and update testing instructions to use cross-platform tools (e.g., az storage blob commands) in addition to PowerShell.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation exhibits a moderate Windows bias in the 'Enable and disable the change feed' section. PowerShell instructions are given in detail, including installation steps, while Linux/macOS equivalents (such as Bash or Azure CLI on Linux) are not mentioned in the PowerShell section. The Azure CLI example is present, but PowerShell is listed as a top-level tab and receives more step-by-step attention. References to Azure Storage Explorer and the Azure portal are platform-neutral, but no explicit Linux/macOS command-line alternatives (e.g., Bash, shell scripts) are provided.
Recommendations
- Add explicit Linux/macOS instructions for enabling/disabling change feed, such as Bash scripts or guidance for using Azure CLI on Linux/macOS.
- In the PowerShell section, mention that Azure CLI works cross-platform and provide links or notes for Linux/macOS users.
- Balance the detail level between PowerShell and Azure CLI instructions, ensuring parity for non-Windows users.
- Consider adding examples for automation via Bash or other Linux-native tools where appropriate.
Storage
Tutorial: Analyze blob inventory reports - Azure Storage
...orage/blobs/storage-blob-inventory-report-analytics.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias primarily through exclusive references to Power BI Desktop, a Windows-only tool, for data visualization. There are no examples or instructions for Linux/macOS users regarding alternative visualization tools or how to use Power BI on non-Windows platforms. Additionally, installation guidance is only provided for Power BI Desktop, with no mention of cross-platform options. The ordering and examples assume a Windows environment by default.
Recommendations
- Provide instructions for visualizing data using cross-platform tools such as Power BI Service (web), Jupyter Notebooks, or open-source alternatives (e.g., Apache Superset, Grafana).
- Explicitly mention the platform limitations of Power BI Desktop and suggest alternatives for Linux/macOS users.
- Include installation and usage guidance for visualization tools available on Linux/macOS.
- Reorder or clarify steps to avoid assuming a Windows-first workflow.
Storage
Host a static website in Azure Storage
...es/storage/blobs/storage-blob-static-website-how-to.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. Windows tools and terminology (e.g., PowerShell, Windows command window, C:\ paths) are mentioned first or exclusively in several sections. PowerShell is presented as a primary automation method, and Windows-centric instructions (such as opening Windows PowerShell) are given without equivalent Linux/macOS alternatives. While Azure CLI is cross-platform, examples and notes often reference Windows environments first. There is little explicit guidance for Linux/macOS users regarding shell choices, file paths, or PowerShell alternatives.
Recommendations
- Explicitly mention that Azure CLI works on Linux/macOS and provide example commands using typical Linux/macOS paths (e.g., /home/user/site).
- In PowerShell sections, clarify that Azure PowerShell can be used on Linux/macOS via pwsh, and provide instructions for installing and running it on those platforms.
- Avoid phrases like 'Open a Windows PowerShell command window'; instead, use 'Open a PowerShell command window' and specify cross-platform compatibility.
- Where file paths are shown (e.g., C:\temp\index.html), also show Linux/macOS equivalents (e.g., /tmp/index.html).
- Add notes or tabs for Bash or other common Linux/macOS shells where relevant.
- Ensure that all references to tools (AzCopy, CLI, PowerShell) include installation/use instructions for Linux/macOS.
Storage
Use the Azure Storage resource provider to access management resources
...cles/storage/common/authorization-resource-provider.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation references Windows-centric tools (PowerShell, Azure classic CLI) for assigning Azure roles, and lists them before mentioning REST API or platform-neutral options. There are no explicit Linux/macOS command-line examples or mentions of cross-platform tools like Azure CLI (az). This may create friction for Linux/macOS users seeking parity.
Recommendations
- Include explicit instructions and examples using Azure CLI (az), which is cross-platform.
- List platform-neutral tools (Azure CLI, REST API) before Windows-specific tools (PowerShell, classic CLI).
- Add Linux/macOS-specific notes or examples where relevant.
- Clarify which tools are available cross-platform and provide links to installation guides for each OS.
Storage
How to migrate your classic storage accounts to Azure Resource Manager
...ain/articles/storage/common/classic-account-migrate.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed instructions and examples for migrating classic storage accounts using the Azure portal and PowerShell, but omits equivalent examples for Linux/macOS users, such as Azure CLI or Bash scripts. PowerShell is featured exclusively for command-line operations, and there are no CLI commands or shell script examples. This creates friction for users on Linux or macOS who may not have access to PowerShell or prefer Azure CLI.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line operations, including listing, deleting, and migrating storage accounts.
- Explicitly mention that Azure CLI is cross-platform and provide links to relevant CLI documentation.
- Ensure that Linux/macOS users are not required to install PowerShell to complete migration tasks.
- Consider including Bash script snippets or guidance for automation on Linux/macOS.
Storage
We're retiring classic storage accounts on August 31, 2024
...s/storage/common/classic-account-migration-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation page references PowerShell cmdlets multiple times, including legacy and modern Azure PowerShell, as the primary example for managing and migrating storage accounts. There is no mention of Linux/macOS equivalents such as Azure CLI, Bash, or REST API usage for these operations. The focus on PowerShell and lack of cross-platform examples creates friction for non-Windows users.
Recommendations
- Add Azure CLI examples for all migration and management operations, alongside PowerShell.
- Explicitly mention that Azure CLI and REST API can be used from Linux/macOS for all steps.
- Provide Bash script snippets or links to cross-platform automation guides.
- Clarify parity between PowerShell and CLI tools in terms of supported operations.
Storage
GPv1 ZRS standard account retirement FAQ
...-zone-redundant-storage-migration-freq-asked-questions.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references PowerShell and Azure CLI as upgrade methods, but does not provide any platform-specific examples or guidance. PowerShell is a Windows-centric tool, and its mention alongside CLI without clarifying Linux/macOS compatibility or providing Bash examples may create friction for non-Windows users. There are no explicit Linux/macOS instructions or examples, and the documentation does not mention Bash, shell, or platform-specific nuances.
Recommendations
- Clarify that Azure CLI is cross-platform and provide explicit Bash/shell command examples for Linux/macOS users.
- Add notes on how to install and use Azure CLI and PowerShell on Linux/macOS, or link to relevant documentation.
- Where PowerShell is mentioned, also mention Bash or shell equivalents for Linux/macOS users.
- Consider listing CLI/Bash examples before or alongside PowerShell to avoid implicit Windows-first bias.
Storage
Understand storage account migration from classic to Azure Resource Manager
...es/storage/common/classic-account-migration-process.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page references migration using the Azure portal, PowerShell, or Azure CLI, but in the 'See also' and 'Validation' sections, PowerShell is consistently mentioned before Azure CLI. There are links to PowerShell-specific migration guides, but no explicit Linux/macOS shell or Bash examples, nor direct mention of Linux/macOS tools or workflows. The documentation does not provide parity in example commands or guidance for Linux users, and the ordering of tools subtly prioritizes Windows-centric approaches.
Recommendations
- Provide explicit Bash or shell examples for Linux/macOS users alongside PowerShell examples.
- Mention Azure CLI as a cross-platform tool first, or at least equally with PowerShell.
- Include links to Linux/macOS-specific migration guides or troubleshooting resources.
- Clarify that Azure CLI works natively on Linux/macOS and provide example commands.
- Avoid ordering PowerShell before CLI unless there is a technical reason.
Storage
Enable infrastructure encryption for double encryption of data
...les/storage/common/infrastructure-encryption-enable.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page displays a moderate Windows bias. PowerShell examples are given a dedicated section before Azure CLI, and Windows-centric tools (PowerShell) are emphasized with installation instructions and module references. The Azure portal instructions are platform-neutral, but PowerShell is presented before Azure CLI, which is more cross-platform. No Linux/macOS-specific examples or notes are provided, and there is no mention of Bash scripting or Linux shell usage.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
- Add explicit notes that Azure CLI commands work on Linux/macOS, and provide Bash-specific usage tips if relevant.
- Include troubleshooting or installation notes for Linux/macOS users (e.g., how to install Azure CLI on Ubuntu, macOS).
- Consider adding Bash script examples for automation alongside PowerShell scripts.
- Clarify that PowerShell Core is available on Linux/macOS, or link to cross-platform PowerShell installation guides.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits moderate Windows bias. PowerShell is the only command-line example given for filtering log blobs, with no equivalent shown for Azure CLI, Bash, or Linux shell scripting. References to tools and user agents in log samples are predominantly Windows-centric (e.g., 'win32', 'Windows_NT'), and Windows tools (PowerShell, AzCopy) are mentioned without Linux alternatives. While Azure CLI is mentioned as an option for enabling logging, no CLI examples are provided, and Windows patterns/tools are presented first or exclusively.
Recommendations
- Add equivalent Azure CLI and Bash examples for listing and filtering log blobs, including metadata queries.
- Include references to Linux/macOS-compatible tools (e.g., AzCopy for Linux, Azure CLI, REST API usage via curl/jq).
- Provide sample log entries and user agent strings for Linux/macOS environments.
- When listing options for enabling logging, present Azure CLI and REST API before or alongside PowerShell.
- Explicitly mention cross-platform compatibility for all tools and commands.
Storage
Enable and manage Azure Storage Analytics logs (classic)
...ticles/storage/common/manage-storage-analytics-logs.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the only CLI example provided, and instructions explicitly reference opening a 'Windows PowerShell command window.' There are no Bash, Azure CLI, or Linux/macOS shell examples. File paths in AzCopy examples use Windows-style (C:\Logs\Storage) and do not mention Linux/macOS equivalents. Windows tools and patterns (PowerShell, Windows file paths) are mentioned exclusively and/or before any cross-platform alternatives.
Recommendations
- Add Azure CLI (az) examples for enabling and managing Storage Analytics logs, as Azure CLI is cross-platform.
- Include Bash or shell script examples for Linux/macOS users.
- When referencing AzCopy, provide both Windows and Linux/macOS file path examples (e.g., C:\Logs\Storage and ~/logs/storage).
- Clarify that AzCopy and Azure Storage Explorer are cross-platform, and provide installation/use instructions for Linux/macOS.
- Avoid language like 'Open a Windows PowerShell command window'; use 'Open a command-line interface' and specify platform options.
- Ensure parity in example ordering: present cross-platform options first or side-by-side with Windows-specific tools.
Storage
Configure an expiration policy for shared access signatures (SAS)
.../main/articles/storage/common/sas-expiration-policy.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page displays moderate Windows bias by providing detailed PowerShell examples and referencing PowerShell commands before Azure CLI. The PowerShell section is more verbose, and screenshots and instructions for the Azure portal (which is platform-agnostic but often associated with Windows environments) are prominent. There is no explicit mention of Linux/macOS-specific considerations, nor are there Bash or shell script examples. However, Azure CLI commands are included, which are cross-platform.
Recommendations
- Add Bash or shell script examples for configuring SAS expiration policy using Azure CLI to demonstrate Linux/macOS workflows.
- Explicitly state that Azure CLI commands work on Linux/macOS and provide any platform-specific notes if applicable.
- Consider presenting Azure CLI examples before PowerShell to avoid implicit prioritization of Windows tools.
- Include troubleshooting tips or notes for Linux/macOS users, especially for authentication or environment setup.
- Mention that the Azure portal is accessible from any OS/browser to reinforce cross-platform parity.
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 discusses proxy configuration in Azure Storage Explorer but does not provide OS-specific instructions or examples for Linux or macOS. The 'system proxy' section references Chromium's use of system network settings but does not clarify how to configure these settings on Linux or macOS. The guidance to 'try system proxy first' implicitly assumes users know how to manage OS proxy settings, which are very different across platforms. No Linux/macOS-specific tools, commands, or UI screenshots are mentioned, and authentication methods like NTLM/Negotiate are Windows-centric.
Recommendations
- Add explicit instructions or links for configuring system proxy settings on Linux and macOS (e.g., GNOME/KDE network settings, environment variables, or command-line tools).
- Include examples or screenshots for proxy configuration on non-Windows platforms.
- Clarify which authentication methods are supported on Linux/macOS, especially for system proxy (NTLM/Negotiate are typically Windows-only).
- Mention any platform-specific limitations or differences in proxy and certificate handling.
Storage
Upgrade to a general-purpose v2 storage account
...ain/articles/storage/common/storage-account-upgrade.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents upgrade instructions for Azure Storage accounts using the Azure portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, and PowerShell is a Windows-centric tool. There are no explicit Linux/macOS examples or mentions of Bash, nor are there instructions for Linux-specific environments or shell patterns. The CLI example is cross-platform, but the ordering and emphasis on PowerShell may create friction for Linux/macOS users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Provide Bash or shell script examples where relevant.
- Add a note or section for Linux/macOS users, including installation instructions for Azure CLI on those platforms.
- Consider removing or de-emphasizing PowerShell unless there is a Windows-specific need.
Storage
Azure storage disaster recovery planning and failover
...s/storage/common/storage-disaster-recovery-guidance.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Windows-centric tools (AzCopy, Azure PowerShell) as primary options for copying data and managing failover, with no mention of Linux/macOS equivalents or CLI usage. Windows tools are listed first and exclusively in several sections, potentially creating friction for Linux/macOS users.
Recommendations
- Include Azure CLI examples for all operations where Azure PowerShell is mentioned, as Azure CLI is cross-platform.
- Explicitly mention that AzCopy is available for Linux/macOS and provide installation and usage examples for those platforms.
- When listing tools, present cross-platform options first or together (e.g., 'AzCopy (Windows, Linux, macOS), Azure CLI, Azure PowerShell').
- Add links or examples for scripting and automation on Linux/macOS, such as Bash scripts using Azure CLI.
- Review all references to PowerShell and ensure parity with CLI commands and documentation.
Storage
Initiate a storage account failover
...es/storage/common/storage-initiate-account-failover.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides detailed instructions for initiating and monitoring Azure Storage account failover using the Azure portal, PowerShell, and Azure CLI. PowerShell is given extensive coverage, including installation steps, troubleshooting, and advanced usage, which is inherently Windows-centric. The CLI section is present and functional, but PowerShell instructions are more elaborate and appear before CLI instructions. There is no mention of Linux/macOS-specific shell environments or alternative tooling, and the PowerShell module installation steps assume a Windows environment.
Recommendations
- Add explicit Bash and/or shell examples for Linux/macOS users, especially for tasks like authentication and environment setup.
- Clarify that Azure CLI is cross-platform and provide parity in example depth and troubleshooting steps for CLI as given for PowerShell.
- Mention that PowerShell Core is available on Linux/macOS and provide installation instructions for those platforms.
- Reorder sections so that Azure CLI instructions appear before PowerShell, or present both side-by-side to avoid Windows-first perception.
- Include troubleshooting tips for CLI extension installation on Linux/macOS (e.g., permissions, PATH issues).
Storage
Install and run the Azurite emulator for Azure Storage
...ain/articles/storage/common/storage-install-azurite.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a notable Windows bias, especially in sections describing how to run Azurite via Visual Studio and command-line examples. Windows-specific tools (Visual Studio, Visual Studio Code) are emphasized, and file paths in examples use Windows conventions (e.g., c:\azurite). There are no explicit Linux/macOS examples for running Azurite, setting workspace paths, or configuring persistent storage, and Linux file path conventions are absent. The location of the Azurite executable is only described for Windows installations of Visual Studio, with no mention of Linux/macOS equivalents.
Recommendations
- Add Linux/macOS-specific instructions and examples for installing and running Azurite, including file path conventions (e.g., /home/user/azurite or ~/azurite).
- Include Visual Studio alternatives for Linux/macOS users, such as instructions for running Azurite via npm or Docker on those platforms.
- Provide explicit guidance on locating the Azurite executable when installed via npm or Docker on Linux/macOS.
- Show command-line examples using both Windows and Linux/macOS file paths side by side.
- Clarify that Azurite is cross-platform and works on Linux/macOS, not just Windows.
Storage
Azure Storage migration tools selection guide
...ain/articles/storage/common/storage-migration-tools.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and scenarios (such as Azure File Sync for Windows file servers and references to Windows Server protocols) are described in detail and appear before Linux/NFS equivalents. Windows-centric terminology (NTFS, SMB, Windows file server) is prominent, and Azure File Sync is presented as a primary sync/tiering solution without Linux parity. While Linux tools (NFS, Rsync, DistCP) are mentioned, they are often listed after Windows tools, with less detail and guidance. There are no explicit Linux or macOS command-line examples, nor are Linux migration scenarios discussed with equal depth.
Recommendations
- Provide Linux/macOS-specific migration scenarios and examples, especially for NFS-based file servers and Rsync/DistCP usage.
- Include step-by-step guides or references for Linux-based migrations, matching the detail given for Windows/Azure File Sync.
- Balance the order of presentation so that Linux/NFS and Windows/SMB options are described with equal prominence.
- Add explicit examples or links for using AzCopy, Rsync, and other tools on Linux/macOS, including shell commands.
- Clarify which tools and features are cross-platform, and highlight any limitations or workarounds for non-Windows environments.