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 1026-1050 of 1657 flagged pages
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
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell. PowerShell instructions are explicitly described as requiring Windows PowerShell, and example file paths use Windows-style (e.g., C:\temp\index.html). The CLI section mentions opening a command console such as Windows PowerShell before mentioning alternatives. PowerShell is presented as a main automation option, and Windows tools/paths are referenced first or exclusively in several places. There are no explicit Linux/macOS CLI or shell examples, and Linux file path conventions are not shown.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS terminals as well as Windows PowerShell.
- Provide example file paths using Linux/macOS conventions (e.g., /home/user/index.html) alongside Windows paths.
- In CLI sections, mention Bash or other common Linux/macOS shells as alternatives to Windows PowerShell.
- Note that PowerShell Core is cross-platform and can be used on Linux/macOS, or provide Bash equivalents where appropriate.
- Where local file paths are referenced, show both Windows and Linux/macOS examples.
Create Pull Request
Storage
Upgrade Azure Blob Storage with Azure Data Lake Storage capabilities
...rage/blobs/upgrade-to-data-lake-storage-gen2-how-to.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides upgrade instructions for Azure Blob Storage to Data Lake Storage using three main methods: Portal, PowerShell, and Azure CLI. The PowerShell section is explicitly Windows-focused, instructing users to 'Open a Windows PowerShell command window' and referencing Windows PowerShell as the default shell for CLI usage. PowerShell examples are given before Azure CLI examples, and there is an implicit assumption that users are on Windows when using PowerShell. The CLI section mentions using Windows PowerShell as a console application, even though Azure CLI is cross-platform. There are no Linux/macOS-specific instructions or clarifications for running PowerShell Core or Azure CLI on those platforms.
Recommendations
- Clarify that Azure PowerShell can be used on Linux/macOS via PowerShell Core, and provide instructions for installing/running PowerShell on those platforms.
- In CLI sections, avoid referring to 'Windows PowerShell' as the default console application; mention alternatives like Bash, Terminal, or PowerShell Core for Linux/macOS users.
- Provide explicit examples or notes for Linux/macOS users, such as how to run Azure CLI commands in Bash or Terminal.
- Ensure that cross-platform parity is maintained by listing CLI instructions before or alongside PowerShell, or by indicating that both methods are equally supported on all platforms.
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 First
Powershell Heavy
Missing Linux Example
Summary
The documentation mentions PowerShell and the Azure classic CLI as tools for assigning Azure roles, but does not reference the cross-platform Azure CLI (az) or provide Linux/macOS-specific examples. PowerShell is listed before REST API, and the classic CLI is deprecated and Windows-centric. No Linux/macOS command-line examples are provided for management operations.
Recommendations
- Add instructions and examples using the cross-platform Azure CLI (az), which is widely used on Linux/macOS.
- Reorder tool references to list cross-platform options (Azure CLI, REST API) before Windows-specific tools (PowerShell, classic CLI).
- Remove references to the deprecated Azure classic CLI and replace with Azure CLI guidance.
- Ensure code samples and walkthroughs include Linux/macOS compatible commands where applicable.
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 step-by-step instructions for migrating classic storage accounts to Azure Resource Manager using the Azure Portal and PowerShell. All command-line examples and automation instructions are exclusively given for PowerShell, with no mention of Azure CLI or Bash equivalents. This creates friction for Linux/macOS users who do not use PowerShell, and may not have access to the Azure Portal in automated or headless environments.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, especially for listing classic storage accounts, deleting disk artifacts, and performing the migration steps (validate, prepare, abort, commit).
- Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to relevant CLI documentation.
- Where possible, provide Bash script snippets or guidance for Linux/macOS automation.
- Clarify any steps that are only possible in PowerShell or the Portal, and offer alternatives or workarounds for non-Windows users.
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 references PowerShell cmdlets as the primary example for managing storage accounts post-migration, and discusses the deprecation of legacy PowerShell cmdlets. There is no mention of Linux/macOS equivalents such as Azure CLI, Bash, or REST API usage for these management tasks. This creates a subtle bias toward Windows/PowerShell users, as Linux/macOS users may prefer or require CLI or scripting examples relevant to their platforms.
Recommendations
- Add Azure CLI examples for managing storage accounts before and after migration, including how to identify, migrate, and delete accounts.
- Include Bash or shell script snippets where appropriate, especially for automation tasks.
- Explicitly mention REST API usage for management operations as a cross-platform alternative.
- Clarify that PowerShell is available cross-platform, but also provide CLI and API examples for parity.
- In sections discussing cmdlet deprecation, reference the equivalent Azure CLI commands and provide migration guidance for scripts using CLI.
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 Tools
Windows First
Missing Linux Example
Summary
The documentation page for enabling and managing Azure Storage Analytics logs (classic) demonstrates a notable Windows bias. PowerShell is the only CLI example provided, and instructions explicitly state to 'Open a Windows PowerShell command window,' with no mention of cross-platform alternatives like Azure CLI or Bash. The AzCopy example uses a Windows file path (C:\Logs\Storage) and does not show a Linux/macOS equivalent. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are referenced first and exclusively in several sections.
Recommendations
- Add Azure CLI examples for enabling and managing Storage Analytics logs, as Azure CLI is cross-platform.
- Clarify that PowerShell Core (pwsh) is available on Linux/macOS, and provide instructions for its use if applicable.
- Provide AzCopy examples using Linux/macOS file paths (e.g., /home/user/logs/storage) and note platform differences.
- Explicitly mention that all steps can be performed on Linux/macOS, or call out any platform limitations.
- Consider including Bash or REST API examples for parity.
- Avoid language like 'Open a Windows PowerShell command window'; use 'Open a PowerShell command window' and clarify platform support.
Storage
Prevent authorization with Shared Key
...les/storage/common/shared-key-authorization-prevent.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides step-by-step instructions for disabling Shared Key authorization using the Azure portal, PowerShell, Azure CLI, and ARM templates. The PowerShell example is given before the Azure CLI example, and there is no explicit mention of Linux/macOS compatibility for PowerShell. The Azure portal instructions are Windows-centric, and screenshots are from the Windows interface. There are no explicit Linux/macOS shell examples or clarifications about cross-platform usage for PowerShell. The CLI example is generic and cross-platform, but the ordering and emphasis favor Windows tools.
Recommendations
- Add explicit notes clarifying that Azure CLI and PowerShell Core are cross-platform, and provide installation instructions for Linux/macOS.
- Include bash or shell script examples for Linux/macOS users where appropriate.
- Consider presenting Azure CLI examples before PowerShell, as CLI is more universally available across platforms.
- Where screenshots are shown, clarify that the Azure portal is web-based and accessible from any OS.
- Mention PowerShell Core compatibility for Linux/macOS, or link to relevant installation guides.
Storage
Create a resource instance network rule for Azure Storage
.../common/storage-network-security-resource-instances.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed PowerShell examples before Azure CLI examples, and the PowerShell section is more extensive, including scenarios for adding, removing, and listing rules with multiple resource instances. This ordering and depth may create friction for Linux/macOS users, who are more likely to use Azure CLI or Bash. No Linux-specific tools or shell examples are provided, and PowerShell is not cross-platform by default for many users.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
- Ensure parity in example depth: include scenarios for adding/removing multiple resource instances and listing rules in the Azure CLI section, matching the PowerShell coverage.
- Explicitly mention that both Azure CLI and PowerShell are supported on all platforms, and link to installation guides for each.
- Consider adding Bash script examples for common tasks, or clarify that Azure CLI commands work in Bash, zsh, and other Unix shells.
Storage
Determine which encryption key model is in use for the storage account
...les/storage/common/storage-encryption-key-model-get.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides three methods for determining the encryption key model: Azure portal, PowerShell, and Azure CLI. PowerShell (a Windows-centric tool) is given its own dedicated section and example, and is listed before Azure CLI. There are no Linux shell (bash) or macOS-specific examples, nor is there mention of cross-platform scripting alternatives. Azure CLI is cross-platform, but PowerShell is still presented as a primary method, which may create friction for Linux/macOS users.
Recommendations
- Clarify that PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Provide bash shell examples for Azure CLI usage, demonstrating how to parse output in typical Linux/macOS environments.
- Consider listing Azure CLI before PowerShell, as it is cross-platform and more widely used outside Windows.
- Explicitly mention platform compatibility for each method.
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
Missing Linux Example
Windows Tools
Summary
The documentation for installing and running the Azurite emulator for Azure Storage demonstrates a notable Windows bias. Many command-line and Docker examples use Windows-style paths (e.g., c:\azurite), and instructions for Visual Studio are exclusively for Windows environments. There are no explicit Linux/macOS examples for directory paths, file locations, or command usage, and Windows tools (Visual Studio, Windows file paths) are referenced before cross-platform or Linux alternatives.
Recommendations
- Add Linux/macOS equivalents for all command-line and Docker examples, using POSIX-style paths (e.g., /home/user/azurite or ~/azurite).
- Include instructions for running Azurite on Linux/macOS, such as where to find the azurite executable after npm install, and how to launch it.
- Clarify that Visual Studio instructions are Windows-only, and provide alternative guidance for Linux/macOS users (e.g., using VS Code, npm, or Docker).
- For Docker volume mounts, show both Windows and Linux syntax (e.g., -v /home/user/azurite:/data).
- Where file paths are referenced (e.g., for certificates), show both Windows and Linux/macOS examples.
Storage
Azure Storage migration tools selection guide
...ain/articles/storage/common/storage-migration-tools.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page provides a broad overview of Azure Storage migration tools, but several sections and examples show a Windows bias. Windows-centric tools (e.g., Azure File Sync, Robocopy, PowerShell) are described in detail and often before their Linux equivalents. Linux-native tools (e.g., Rsync, DistCP) are mentioned but with less detail and appear later in the tables. Some sections, such as Azure File Sync, are Windows-only by design, but the overall guidance and examples tend to prioritize Windows scenarios and tools, with limited parity for Linux/macOS users.
Recommendations
- Provide equal detail and step-by-step examples for Linux/macOS migration scenarios, especially for tools like Rsync, DistCP, and NFS-based migrations.
- Include explicit Linux command-line examples (e.g., using Rsync, AzCopy on Linux, bash scripting) alongside Windows/PowerShell examples.
- Mention and link to Linux-specific documentation for agent deployment, tool installation, and troubleshooting.
- Clarify which tools are cross-platform and highlight their usage on Linux/macOS (e.g., AzCopy, Data Box Gateway, Azure Data Factory).
- Ensure tables and recommendations do not default to Windows tools or protocols unless the scenario is inherently Windows-only.
Storage
AzCopy v10 configuration setting (Azure Storage)
...ge/common/storage-ref-azcopy-configuration-settings.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux/macOS examples for configuring proxy settings, but Windows instructions (including PowerShell and CMD) are listed first and in greater detail. The section on bypassing proxies only gives explicit commands for Windows (CMD and PowerShell), while Linux/macOS users are simply told to leave the variable unset. There are also several environment variable descriptions that reference Windows-specific behaviors or defaults (e.g., AzCopy caching proxy lookups on Windows, logging to Windows Event Logger).
Recommendations
- Present Linux/macOS and Windows examples in parallel or alternate which is shown first to avoid implicit prioritization.
- Provide explicit Linux/macOS commands for bypassing proxies, not just 'leave unset', e.g., 'unset HTTPS_PROXY' or 'export HTTPS_PROXY=''.
- Clarify platform-specific behaviors for environment variables, especially where defaults differ (e.g., proxy detection, logging), and ensure Linux/macOS equivalents are described.
- Where Windows-specific tools (PowerShell, CMD) are mentioned, ensure Bash/zsh equivalents are included and equally detailed.
Storage
Authorize access for AzCopy with a service principal
...mmon/storage-use-azcopy-authorize-service-principal.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Linux and Windows examples for environment variable setup, but consistently uses PowerShell syntax for interactive prompts and sensitive variable entry (e.g., Read-Host), even in sections not explicitly marked as Windows-specific. Guidance for exporting certificates references Windows tools (Export-PfxCertificate) without Linux alternatives. In the Azure CLI section, the Windows example uses PSCRED (PowerShell credential) rather than AZCLI, which may confuse users. PowerShell examples and terminology are often presented first or exclusively for sensitive operations, creating friction for Linux/macOS users.
Recommendations
- Provide equivalent Linux/macOS shell examples for interactive variable entry (e.g., using 'read -s' in Bash for secrets) wherever PowerShell/Read-Host is shown.
- Reference Linux/macOS certificate export tools (e.g., openssl) alongside Windows Export-PfxCertificate.
- Clarify the correct environment variable values for AZCOPY_AUTO_LOGIN_TYPE for both platforms (e.g., AZCLI for Azure CLI on all OSes, PSCRED for PowerShell only).
- Ensure that sensitive operations (like setting secrets) have cross-platform guidance and do not default to PowerShell-only examples.
- Where possible, present Linux/macOS and Windows examples side-by-side, or alternate which is shown first.
Storage
Authorize access for AzCopy with a user identity
...e/common/storage-use-azcopy-authorize-user-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux (bash) and Windows (PowerShell) examples for environment variable setup, but Windows/PowerShell examples are consistently shown after Linux ones. However, the 'Authorize by using Azure PowerShell' section is Windows-specific and lacks a Linux equivalent, which may cause friction for Linux/macOS users who do not use PowerShell. The rest of the instructions (AzCopy login, Azure CLI) are cross-platform and include Linux examples.
Recommendations
- Clarify that the 'Authorize by using Azure PowerShell' method is Windows-only, and suggest Linux/macOS users use Azure CLI for equivalent functionality.
- Where PowerShell is used, explicitly state platform limitations and alternatives for Linux/macOS users.
- Consider adding a table or summary comparing all authorization methods and their platform compatibility.
- Ensure that all critical workflows have Linux/macOS equivalents or clear guidance for non-Windows users.
Storage
Download blobs from Azure Blob Storage by using AzCopy v10
...es/storage/common/storage-use-azcopy-blobs-download.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides AzCopy usage examples exclusively with Windows-style paths (e.g., 'C:\myDirectory\myTextFile.txt') and does not include any Linux/macOS path examples (e.g., '/home/user/myTextFile.txt'). All destination paths are shown in Windows format, and there are no explicit Linux/macOS command examples. Although there are tips about quoting differences between shells, the examples themselves are Windows-centric.
Recommendations
- Add parallel examples using Linux/macOS path formats (e.g., '/home/user/myTextFile.txt') for each AzCopy command.
- Include a note or table summarizing path differences and quoting requirements for Windows, Linux, and macOS shells.
- Alternate the order of examples so that Linux/macOS examples are shown first or side-by-side with Windows examples.
- Clarify that AzCopy is fully cross-platform and provide explicit instructions for Linux/macOS users where relevant.
Storage
Synchronize with Azure Blob storage by using AzCopy v10
...storage/common/storage-use-azcopy-blobs-synchronize.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides AzCopy sync examples using Windows-style paths (e.g., 'C:\myDirectory') and mentions quoting conventions for Windows Command Shell (cmd.exe) before Linux/macOS shells. There are no explicit Linux/macOS path examples (e.g., '/home/user/myDirectory'), and all local path examples use Windows syntax. This may cause confusion or friction for Linux/macOS users.
Recommendations
- Add Linux/macOS path examples (e.g., '/home/user/myDirectory') alongside Windows examples.
- Explicitly show command syntax for both Windows (cmd.exe) and Linux/macOS (bash/zsh) shells.
- Clarify quoting conventions for PowerShell, bash, and zsh in addition to cmd.exe.
- Consider alternating the order of examples or providing a tabbed interface for platform-specific commands.
Storage
Use AzCopy v10 in scripts and scheduled transfers
...rticles/storage/common/storage-use-azcopy-in-script.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Linux and Windows examples for scheduling AzCopy tasks, but the Windows example is more detailed, with explicit use of Windows-specific tools (Schtasks) and additional explanation of batch file character escaping. Windows tools and patterns are described in more depth, and Windows-specific issues (like escaping in .cmd files) are covered, while Linux equivalents (e.g., shell escaping) are not discussed. The order of sections and detail level subtly favor Windows users.
Recommendations
- Add equivalent detail for Linux users, such as common shell escaping issues with SAS tokens and how to handle them in bash scripts.
- Provide more information about scheduling with systemd timers as an alternative to cron for Linux users.
- Ensure parity in the explanation of scheduling tools (e.g., explain cron parameters as thoroughly as Schtasks parameters).
- Consider presenting Linux and Windows examples in parallel or alternating order to avoid implicit prioritization.
- Include macOS-specific notes if there are any platform differences.
Storage
Configure Transport Layer Security (TLS) for a client application
...n/transport-layer-security-configure-client-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides examples only for PowerShell and .NET, both of which are primarily Windows-centric (especially PowerShell). There are no examples for configuring TLS in Linux/macOS environments, such as with Python, Java, or using OpenSSL. The verification step recommends Fiddler, a Windows-only tool, without mentioning Linux/macOS alternatives. The overall guidance assumes a Windows-first perspective and omits Linux/macOS-specific instructions.
Recommendations
- Add examples for configuring TLS in client applications on Linux/macOS, such as Python, Java, or using curl/OpenSSL.
- Include instructions for verifying TLS versions using cross-platform tools like Wireshark or tcpdump.
- Clarify any OS-specific requirements or differences in TLS configuration.
- Present examples for multiple platforms side-by-side, or indicate platform applicability for each example.
Storage
Migrate to Transport Layer Security (TLS) 1.2 for Azure Blob Storage
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-migrate-to-TLS2.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page on migrating to TLS 1.2 for Azure Blob Storage demonstrates a notable Windows bias. Quick Tips and guidance focus on Windows OS versions and .NET Framework, with no mention of Linux/macOS equivalents. Examples and troubleshooting links are PowerShell-heavy and reference Windows-specific tools (e.g., Fiddler, WinHTTP). There are no Linux/macOS-specific instructions, tools, or examples for configuring TLS 1.2, which may create friction for non-Windows users.
Recommendations
- Add explicit guidance for Linux and macOS users, including how to verify and enforce TLS 1.2 in common environments (e.g., OpenSSL, curl, Python, Java).
- Include examples for configuring TLS 1.2 in Linux/macOS client applications and scripts.
- Mention Linux/macOS default TLS support (e.g., most modern distributions support TLS 1.2 by default) in the Quick Tips section.
- List cross-platform tools for TLS troubleshooting (e.g., OpenSSL, curl, nmap) alongside Windows tools.
- Provide parity in troubleshooting steps and links for Linux/macOS environments.
Storage
Create multiple Azure Elastic SAN volumes in a batch
...storage/elastic-san/elastic-san-batch-create-sample.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively provides a PowerShell script for batch creation of Azure Elastic SAN volumes, assumes use of Windows file paths (e.g., D:\ElasticSan\TestCsv3.csv), and does not mention or provide examples for Linux/macOS users (e.g., Bash, Azure CLI, or cross-platform scripting). There is no guidance for running the process on non-Windows platforms.
Recommendations
- Add an Azure CLI or Bash script example for batch volume creation using a CSV file.
- Clarify whether the process can be performed on Linux/macOS and provide relevant instructions.
- Use cross-platform file path examples (e.g., /home/user/ElasticSan/TestCsv3.csv) alongside Windows paths.
- Explicitly mention prerequisites and alternatives for non-Windows environments.
Storage
Enable access to Azure file shares using OAuth over REST
...ob/main/articles/storage/files/authorize-oauth-rest.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed examples for Azure PowerShell and Azure CLI, with PowerShell instructions and examples presented before CLI. All example commands for file operations use PowerShell or CLI, but there are no explicit Linux/macOS shell examples (e.g., Bash/cURL), nor are there instructions for using REST APIs directly from Linux environments. The PowerShell section is more extensive and detailed, and the documentation assumes familiarity with PowerShell patterns, which may create friction for Linux/macOS users.
Recommendations
- Add explicit Linux/macOS shell examples using Bash and cURL to demonstrate REST API calls for OAuth authentication and file operations.
- Provide parity in example detail for Azure CLI, including step-by-step instructions and troubleshooting tips similar to those given for PowerShell.
- Reorder sections so that CLI and cross-platform examples are presented before or alongside PowerShell examples.
- Clarify that Azure CLI is cross-platform and highlight usage on Linux/macOS.
- Include notes or links to REST API documentation for users who prefer direct API calls from any OS.
Storage
Use Managed Identities with Azure Files (preview)
...ain/articles/storage/files/files-managed-identities.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page provides both Windows and Linux instructions for using managed identities with Azure Files SMB shares. However, there is a notable Windows bias: PowerShell is used exclusively for all setup and configuration examples, and Windows-specific tools and modules (e.g., AzFilesSmbMIClient, PowerShell modules) are described in detail before Linux equivalents. Windows instructions and examples are generally presented first in each section, and troubleshooting and developer integration guidance is more detailed for Windows (e.g., NuGet, native DLL integration) than for Linux.
Recommendations
- Provide Azure CLI or Bash examples for storage account and file share setup, in addition to PowerShell, to improve parity for Linux/macOS users.
- Present Windows and Linux instructions side-by-side or in a more balanced order, rather than consistently listing Windows first.
- Expand Linux developer integration guidance to match the detail provided for Windows (e.g., more code samples, troubleshooting tips).
- Where possible, mention cross-platform tools or alternatives to PowerShell for users on Linux/macOS.
- Clarify when certain steps (e.g., PowerShell commands) are Windows-only and offer Linux/macOS alternatives.
Storage
Migrate Files Between SMB Azure file shares
...articles/storage/files/migrate-files-between-shares.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively describes migration using Robocopy, a Windows-only tool, and instructs users to deploy a Windows VM. No Linux/macOS alternatives or cross-platform tools are mentioned, and all examples and steps are Windows-centric. This creates friction for Linux/macOS users who may wish to perform similar migrations.
Recommendations
- Add instructions and examples for migrating files using cross-platform tools such as AzCopy, rsync (when SMB mounts are available), or other supported utilities.
- Clarify whether the migration method is strictly Windows-only or if alternatives exist for Linux/macOS environments.
- Provide guidance for mounting SMB Azure file shares on Linux/macOS and performing file migration using native tools.
- Consider reordering or supplementing the documentation to mention cross-platform options before or alongside Windows-specific instructions.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation for SMB file shares in Azure Files shows a moderate Windows bias. Windows/PowerShell examples and tools are presented first and in greater detail, with specific registry and PowerShell instructions for Windows clients. There is a lack of Linux/macOS-specific guidance for SMB client configuration, troubleshooting, or security settings, and no Linux/macOS examples for client-side SMB settings (e.g., encryption ciphers). While Azure CLI examples are provided (which are cross-platform), critical client configuration steps are only described for Windows.
Recommendations
- Add Linux/macOS-specific instructions for configuring SMB client encryption ciphers and other relevant settings (e.g., using mount.cifs options, /etc/samba/smb.conf, or relevant kernel parameters).
- Include troubleshooting guidance for Linux/macOS SMB clients, especially for security/encryption mismatches.
- Provide parity in examples: show how to check and set SMB client configuration on Linux/macOS, not just Windows/PowerShell.
- When referencing client-side changes (e.g., enabling AES-256-GCM), include equivalent steps for Linux/macOS clients, or explicitly state if such configuration is not possible.
- Balance the order of examples so that Linux/macOS are not always presented after Windows.
Storage
Improve SMB Azure File Share Performance
...cs/blob/main/articles/storage/files/smb-performance.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides both Windows and Linux guidance for SMB Multichannel, including explicit Linux kernel and mount command examples. However, performance testing and verification sections focus heavily on Windows tools (diskspd.exe, robocopy, PowerShell), with no Linux equivalents or parity in example commands. Windows configuration and troubleshooting steps are more detailed and presented before Linux, and registration instructions for features only mention Azure PowerShell (which is cross-platform but often Windows-centric in usage).
Recommendations
- Include Linux equivalents for performance testing (e.g., fio, dd) and verification steps (e.g., using smbstatus, dmesg, or other Linux tools to verify multichannel connections).
- Provide example commands for mounting and testing SMB shares on Linux, similar to the detailed Windows PowerShell and diskspd.exe examples.
- Add troubleshooting steps and configuration verification for Linux clients, such as checking kernel modules, CIFS mount options, and network configuration.
- Clarify that Azure PowerShell is cross-platform and provide CLI examples (az CLI) for feature registration, which is more commonly used on Linux/macOS.
- Balance the order of presentation so that Linux and Windows examples are given equal prominence.