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 751-775 of 1657 flagged pages
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-emulator.md
...b/main/articles/storage/common/storage-use-emulator.md
High Priority
View Details →
Detected Bias Types
Windows Only
Missing Linux Example
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation is heavily biased towards Windows, as the Azure Storage Emulator is only available for Windows. All setup, usage, and command-line instructions are Windows-specific, referencing Windows tools (SQL Server LocalDB, SSMS, Windows authentication, Windows taskbar, Command Prompt). The only code example for generating a SAS token uses Azure PowerShell, with no Linux or cross-platform CLI alternatives. While Azurite is mentioned as the cross-platform replacement, no practical Linux or Azurite usage examples are provided, and the documentation does not guide Linux/macOS users on equivalent workflows.
Recommendations
- Add a clear section or callout at the top directing Linux/macOS users to Azurite, with a link to detailed Azurite setup and usage documentation.
- Provide parallel examples for Azurite, including installation (npm, Docker), starting the emulator, and connecting to it from code.
- Include cross-platform command-line examples (e.g., Azure CLI, Bash) for generating SAS tokens and interacting with the emulator, not just PowerShell.
- Mention and demonstrate how to use Azurite with popular Linux tools and shells.
- Where Windows-specific tools are referenced (e.g., SSMS, LocalDB), suggest cross-platform alternatives or clarify their scope.
- Ensure that all code and workflow examples have Linux/macOS equivalents or clear guidance for non-Windows users.
Create Pull Request
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-troubleshoot.md
...ticles/storage/elastic-san/elastic-san-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows tools and scripts (e.g., PowerShell, iscsicli, mpclaim) are often mentioned first or exclusively, and some troubleshooting steps provide detailed instructions or scripts for Windows before Linux equivalents. In some sections, Linux examples are present but less detailed or referenced after Windows. There are also cases where only Windows session limits or tools are discussed, and Linux-specific details are less prominent.
Recommendations
- Ensure that for every Windows tool or script mentioned (e.g., iscsicli, mpclaim, PowerShell scripts), the equivalent Linux command or script (e.g., iscsiadm, multipath, bash/python scripts) is provided with equal detail and prominence.
- Present Linux and Windows instructions in parallel or side-by-side, rather than listing Windows first by default.
- Where session limits or configuration parameters are discussed for Windows, provide the corresponding Linux values and commands.
- Expand Linux troubleshooting steps to match the depth and clarity of Windows steps, including direct command examples and links to scripts.
- Review the order of examples and ensure Linux is not consistently presented after Windows, to avoid reinforcing a Windows-first perspective.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-cloud-tiering-overview.md
.../storage/file-sync/file-sync-cloud-tiering-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. It exclusively references Windows Server concepts (e.g., NTFS, Windows Server data deduplication, Event Viewer), uses Windows-specific terminology (e.g., reparse points, FILE_ATTRIBUTE_RECALL_ON_DATA_ACCESS), and provides operational examples only for Windows (such as the PowerShell cmdlet Invoke-StorageSyncFileRecall). There are no Linux equivalents, examples, or mentions of cross-platform support, and the documentation assumes the reader is operating in a Windows environment.
Recommendations
- Clarify early in the documentation whether Azure File Sync and cloud tiering are supported on Linux, and if not, state this explicitly.
- If Linux support exists, provide equivalent examples for Linux environments, including command-line operations, file attribute handling, and monitoring/logging instructions.
- Reference Linux file systems (e.g., ext4, XFS) and their handling of file metadata and access times, if applicable.
- Include Linux-native tools or commands for checking file status, disk space, and event logs.
- Avoid assuming NTFS or Windows-specific features (such as reparse points or Event Viewer) are universally available; provide cross-platform alternatives or note limitations.
- If PowerShell cmdlets are mentioned, provide equivalent shell or scripting examples for Linux (e.g., Bash).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/upgrade-to-data-lake-storage-gen2-how-to.md
...rage/blobs/upgrade-to-data-lake-storage-gen2-how-to.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell instructions, referencing Windows PowerShell specifically, and suggesting opening a 'Windows PowerShell command window.' The Azure CLI section also suggests using 'Windows PowerShell' as a console, and does not mention Linux or macOS terminals. There are no explicit Linux/macOS shell examples or guidance, and no mention of Linux-native tools or environments. The documentation assumes a Windows-centric workflow and omits parity for Linux users.
Recommendations
- In the PowerShell section, clarify that Azure PowerShell can be used on Windows, Linux, and macOS, and provide instructions for all platforms.
- In the Azure CLI section, recommend using Bash or other Linux/macOS terminals as alternatives to Windows PowerShell, and provide examples or screenshots from those environments.
- Wherever 'Windows PowerShell' is mentioned, generalize to 'PowerShell' and note cross-platform compatibility.
- Add explicit Linux/macOS instructions or notes for command-line steps, including any differences in command syntax or prerequisites.
- Ensure that screenshots and walkthroughs are not exclusively from Windows environments; include examples from Linux/macOS where possible.
- Mention Linux-native tools or scripting environments (e.g., Bash, zsh) as valid options for running Azure CLI commands.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-server-recovery.md
...rticles/storage/file-sync/file-sync-server-recovery.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation assumes the recovery process is performed exclusively on Windows Server or Azure VMs running Windows. All instructions reference Windows-specific tools (e.g., Robocopy), and there are no examples or guidance for performing the same tasks on Linux servers. The agent installation and registration steps are also linked specifically to Windows Server documentation, with no mention of Linux compatibility or alternatives.
Recommendations
- Explicitly state whether Azure File Sync is supported on Linux, and if not, clarify this early in the documentation.
- If Linux is supported, provide equivalent instructions and examples for Linux environments, including alternative tools (e.g., rsync instead of Robocopy) and Linux-specific agent installation steps.
- If only Windows is supported, add a clear note at the beginning of the article to inform users.
- Where possible, use cross-platform terminology and provide parity in examples for both Windows and Linux users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-server-endpoint-create.md
.../storage/file-sync/file-sync-server-endpoint-create.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets (e.g., Invoke-StorageSyncFileRecall), using Windows-style file paths (e.g., F:\sync1), and mentioning Windows tools (RoboCopy) as behavioral analogies. There are no Linux-specific instructions, examples, or tool references, and no mention of Linux support or parity for Azure File Sync server endpoints.
Recommendations
- Explicitly state platform support (Windows, Linux) for Azure File Sync server endpoints at the beginning of the documentation.
- If Linux is supported, provide equivalent Linux command-line examples (e.g., bash scripts, relevant Linux tools) alongside PowerShell examples.
- Replace or supplement Windows-specific path examples (e.g., F:\sync1) with Linux-style paths (e.g., /mnt/sync1) where appropriate.
- If certain features or tools (like RoboCopy or PowerShell cmdlets) are only available on Windows, clearly note this and suggest Linux alternatives if possible.
- Include troubleshooting and management instructions for Linux servers if they are supported, or clearly state if only Windows is supported.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-server-registration.md
...les/storage/file-sync/file-sync-server-registration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All instructions, examples, and tooling references are exclusively for Windows Server, with no mention of Linux or cross-platform support. PowerShell is the only scripting interface shown, and all file paths, configuration steps, and screenshots are Windows-specific. There is no guidance for Linux servers, nor any indication that Azure File Sync can be used outside of Windows.
Recommendations
- Clearly state in the introduction whether Azure File Sync supports only Windows Server or if there is any Linux support. If Linux is not supported, make this explicit to set user expectations.
- If Linux support exists or is planned, add equivalent Linux instructions, including command-line examples (e.g., Bash, Azure CLI), package installation steps, and configuration file locations.
- Where PowerShell is used, provide Azure CLI or REST API equivalents for cross-platform automation.
- If certain features (e.g., agent installation, server registration) are Windows-only, explicitly note this and provide alternative Azure file integration solutions for Linux users.
- Avoid Windows-centric terminology and screenshots unless the feature is strictly Windows-only; otherwise, include Linux or generic alternatives.
- For proxy configuration and network limits, describe how to achieve similar results on Linux systems, if applicable.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-disaster-recovery.md
...main/articles/storage/files/files-disaster-recovery.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently listing Windows-centric tools (Azure PowerShell) before cross-platform alternatives (Azure CLI), and by referencing PowerShell in key usage examples. There are no explicit Linux or Unix-specific examples or guidance, and Windows/SMB scenarios are implicitly prioritized (e.g., in the redundancy matrix and failover instructions). No Linux/NFS-specific failover or recovery workflows are described.
Recommendations
- Ensure that all command-line examples are provided for both Azure PowerShell and Azure CLI, with equal prominence and in parallel sections.
- Explicitly mention and provide examples for Linux/NFS scenarios, including how to handle failover and remounting from Linux clients.
- When referencing tools or commands, avoid listing Windows/PowerShell first by default; alternate or present both together.
- Include a section or callout for Linux administrators, outlining any differences or considerations for disaster recovery and failover with NFS shares.
- In the redundancy matrix and throughout the document, clarify the parity (or lack thereof) between SMB (Windows) and NFS (Linux) support for DR features.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/secure-file-transfer-protocol-known-issues.md
...ge/blobs/secure-file-transfer-protocol-known-issues.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. The only specific client configuration example provided is for WinSCP, a Windows-centric SFTP client, and no Linux or cross-platform client (such as OpenSSH, FileZilla, or lftp) is mentioned or given as an example. The troubleshooting and client settings sections do not reference Linux tools or provide parity in examples, which may leave Linux users without clear guidance.
Recommendations
- Add configuration examples for popular Linux and cross-platform SFTP clients (e.g., OpenSSH's sftp, FileZilla, lftp) alongside or before WinSCP.
- When listing unsupported clients, clarify whether these are Windows-only or cross-platform, and consider including Linux-specific clients if relevant.
- In the 'Client settings' section, provide equivalent settings or notes for Linux clients (e.g., how to disable resume/temporary filename in OpenSSH sftp or FileZilla, if applicable).
- Ensure troubleshooting steps reference both Windows and Linux command-line tools and error messages where appropriate.
- Consider a dedicated section or table comparing client compatibility and configuration steps for both Windows and Linux environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/archive-rehydrate-handle-event.md
...ticles/storage/blobs/archive-rehydrate-handle-event.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a clear Windows bias by exclusively using Visual Studio (Windows-only) for development, instructing users to set the Function App OS to Windows, and providing no guidance or examples for Linux or cross-platform development environments. There are no instructions for using VS Code, CLI, or other tools commonly used on Linux/macOS, nor any mention of deploying or running on Linux-based Function Apps.
Recommendations
- Provide parallel instructions for developing Azure Functions using cross-platform tools such as Visual Studio Code and the Azure Functions Core Tools CLI.
- Include steps for creating and deploying Function Apps with the OS set to Linux, and highlight any differences or considerations.
- Offer examples for installing dependencies and running/debugging the function on Linux/macOS (e.g., using dotnet CLI, bash, or zsh).
- Mention that Azure Functions can be hosted on both Windows and Linux, and explain how to select the appropriate OS during Function App creation.
- Avoid assuming Visual Studio is the only or primary development environment; reference alternatives early and equally.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/object-replication-configure.md
...articles/storage/blobs/object-replication-configure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides extensive PowerShell examples and references, including file paths and commands that are specific to Windows environments (e.g., C:\temp\json.txt), and often lists PowerShell before Azure CLI. There are no explicit Linux shell or Bash examples, and no mention of Linux-specific tools or considerations. This may make the documentation less approachable for Linux users and those who do not use PowerShell.
Recommendations
- Add Bash shell equivalents for all PowerShell examples, especially for tasks like file manipulation (e.g., using cat, jq, or similar tools for JSON processing).
- Use platform-neutral file paths in examples (e.g., /tmp/json.txt or ./json.txt) or provide both Windows and Linux/Mac paths.
- When listing command-line options, alternate the order or explicitly state that both PowerShell and Azure CLI are cross-platform, and highlight CLI as suitable for Linux/macOS.
- Include a note that Azure CLI commands work natively on Linux/macOS and can be run in Bash or other shells.
- Where PowerShell is used for scripting, provide equivalent Bash scripts or commands for Linux users.
- Review screenshots and UI references to ensure they are not Windows-specific, or provide clarifying notes if UI differs on other platforms.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-best-practices.md
...cles/storage/blobs/data-lake-storage-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. In tool and workflow tables, Azure PowerShell is consistently listed before Azure CLI, and PowerShell is mentioned as a primary method for tasks such as ingesting and downloading data. There is a lack of explicit Linux command-line examples or references to Linux-native tools, and the documentation does not provide parity in example order or depth between Windows and Linux environments. Azure Storage Explorer and AzCopy are cross-platform, but the documentation does not highlight their use on Linux or provide Linux-specific guidance.
Recommendations
- Ensure that Azure CLI examples and references are given equal prominence to PowerShell, and consider listing CLI before or alongside PowerShell to avoid a 'Windows-first' impression.
- Add explicit Linux command-line examples and workflows, such as bash scripts or Linux shell commands, especially for common tasks like data ingestion, download, and monitoring.
- Highlight the cross-platform nature of tools like AzCopy and Azure Storage Explorer, and provide instructions or screenshots for Linux environments.
- Include references to Linux-native tools or integration patterns (e.g., using curl, wget, or Linux automation tools) where appropriate.
- Where PowerShell is mentioned, clarify that it is available on Linux as well, or provide alternative Linux-native command examples.
- Review the order of tool listings in tables and prose to ensure that Windows-specific tools are not always listed first.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/authorize-access-azure-active-directory.md
...orage/blobs/authorize-access-azure-active-directory.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by consistently mentioning PowerShell before Azure CLI, grouping them together as primary command-line interfaces, and not providing explicit Linux- or macOS-specific examples or guidance. The focus on PowerShell, a Windows-centric tool, and the lack of parity in example depth or order for cross-platform tools like Azure CLI may make Linux users feel secondary. There are no explicit Linux shell (bash) or macOS instructions, and the documentation does not clarify cross-platform differences or considerations.
Recommendations
- Ensure that Azure CLI examples are presented before or alongside PowerShell, emphasizing its cross-platform nature.
- Explicitly mention that Azure CLI works on Windows, Linux, and macOS, and provide example commands in bash syntax where appropriate.
- Add a section or callout for Linux/macOS users, highlighting any differences or prerequisites.
- Where PowerShell is referenced, clarify that it is available cross-platform, or provide equivalent bash commands.
- Review linked articles (e.g., 'authorize-data-operations-cli.md' and 'authorize-data-operations-powershell.md') to ensure Linux parity in examples and instructions.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-access-control.md
...cles/storage/blobs/data-lake-storage-access-control.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by listing PowerShell and Azure Storage Explorer (a GUI tool more common on Windows) before Azure CLI in the 'How to set ACLs' section. PowerShell is given its own row, and Storage Explorer is listed first, while Linux-native tools or shell examples are not provided. The only command-line example for obtaining a service principal's object ID uses Azure CLI, which is cross-platform, but no explicit Linux shell (e.g., bash) or Linux file system command analogies are given. There are no Linux-specific examples or references to Linux command-line tools for managing ACLs, despite the POSIX context.
Recommendations
- Provide Linux shell (bash) examples for managing ACLs using Azure CLI, including sample commands for common tasks.
- Include references to Linux-native tools (e.g., setfacl, getfacl) for users familiar with POSIX ACLs, and draw explicit parallels between Azure Data Lake Storage ACLs and Linux file system ACL management.
- Reorder the 'How to set ACLs' table to list Azure CLI before PowerShell and Storage Explorer, or group CLI tools together to avoid a Windows-first impression.
- Add a section or examples specifically targeting Linux users, such as scripting with bash or integrating with Linux-based automation.
- Clarify that Azure CLI is fully supported on Linux and macOS, and provide installation links or tips for non-Windows environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/lifecycle-management-policy-configure.md
...storage/blobs/lifecycle-management-policy-configure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and explanations before Azure CLI equivalents, and by referencing PowerShell-specific cmdlets and workflows. The PowerShell section is more comprehensive, with step-by-step command breakdowns, while the Azure CLI section is less detailed. There is no mention of Linux-specific tools, shells, or workflows, and the use of PowerShell as a primary scripting example assumes a Windows-centric audience.
Recommendations
- Provide equally detailed Azure CLI examples, including step-by-step breakdowns of commands and their parameters, to match the depth of the PowerShell section.
- Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, to encourage non-Windows users.
- Add Bash shell script examples for common lifecycle policy tasks, demonstrating usage in a typical Linux environment.
- Avoid presenting PowerShell examples before CLI or Bash examples; consider presenting CLI first or in parallel, as it is more universally available.
- Reference Linux and macOS environments in prerequisites or introductory sections, clarifying that all operations can be performed from those platforms.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/soft-delete-container-enable.md
...articles/storage/blobs/soft-delete-container-enable.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed PowerShell instructions (a Windows-centric tool) before Azure CLI examples, and does not mention or provide Linux-specific command-line environments or examples. There is a lack of parity in guidance for Linux users, as the PowerShell section is more detailed and appears before the Azure CLI, which is cross-platform. No explicit Linux shell (bash) or scripting examples are given, and the template section assumes use of the Azure Portal, which is platform-agnostic but not CLI-based.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample bash shell usage where appropriate.
- Balance the level of detail between PowerShell and Azure CLI sections to ensure Linux users have equally comprehensive instructions.
- Consider adding a section or note for Linux users, highlighting any platform-specific considerations or tips.
- If possible, provide examples using Azure SDKs or REST API calls that are platform-neutral.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-index-how-to.md
...in/articles/storage/blobs/storage-blob-index-how-to.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently referencing Windows-specific tools and patterns. PowerShell is given a dedicated section, and instructions for the Azure CLI repeatedly suggest using Windows PowerShell as the example terminal, with file paths in Windows format (e.g., C:\demo-file.txt). There are no explicit Linux or macOS examples, nor are cross-platform considerations (such as file path differences or alternative shells) addressed. The documentation does not mention or show Linux command-line environments, and the use of Windows-centric terminology and tools is prevalent throughout.
Recommendations
- Provide explicit Linux/macOS examples alongside Windows ones, especially for CLI commands (e.g., show file paths like /home/user/demo-file.txt).
- When referencing a command console, mention cross-platform options such as Bash, Terminal, or zsh, not just Windows PowerShell.
- Balance PowerShell examples with Bash or generic shell script examples where possible.
- Clarify that Azure CLI and AzCopy are cross-platform, and show usage in both Windows and Linux/macOS environments.
- Avoid using only Windows-style file paths in examples; provide both Windows and Unix-style paths.
- Add notes or callouts about any differences in behavior or prerequisites on Linux/macOS.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-static-website.md
.../articles/storage/blobs/storage-blob-static-website.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. In the 'Uploading content' section, Windows-centric tools and workflows (Azure PowerShell, Visual Studio Code extension, Azure Storage Explorer) are listed alongside cross-platform tools, but PowerShell is given equal prominence to the Azure CLI, and Windows tools are mentioned before Linux-native equivalents. There are no explicit Linux-specific examples or mentions of Linux-native tools or workflows. The documentation does not provide Linux shell (bash) or scripting examples, and it assumes familiarity with tools more common in Windows environments.
Recommendations
- Provide explicit Linux/bash command-line examples for common tasks (e.g., using Azure CLI in bash, AzCopy in Linux).
- Include Linux-native tools or workflows (e.g., mention using rclone, curl, or bash scripting for uploads).
- Balance the order of tool listings: list Azure CLI before PowerShell, and clarify that both are cross-platform.
- Add screenshots or instructions for Linux environments (e.g., terminal screenshots, file path conventions).
- Clarify that Visual Studio Code and Azure CLI are cross-platform, and provide links to Linux installation guides.
- Consider a 'Platform differences' section to highlight any OS-specific considerations.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/authorization-resource-provider.md
...cles/storage/common/authorization-resource-provider.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows-centric tools (PowerShell, Azure classic CLI) before mentioning cross-platform or Linux-native options, and by not providing explicit Linux or Bash/CLI examples. The mention of PowerShell and the Azure classic CLI (which is Windows-focused) without equal emphasis on Azure CLI (which is cross-platform and more commonly used on Linux) further highlights this bias. There are no Linux-specific instructions, and no Bash or shell command examples are provided.
Recommendations
- Include explicit Azure CLI examples, as it is cross-platform and widely used on Linux and macOS.
- When listing tools for assigning roles, mention Azure CLI before PowerShell and Azure classic CLI, or present them together with equal prominence.
- Provide Bash or shell command examples alongside PowerShell examples, or use Azure CLI as the primary example since it works across all platforms.
- Clarify that all management operations can be performed from Linux, macOS, and Windows, and provide links to relevant cross-platform documentation.
- Avoid referencing deprecated or Windows-only tools (such as Azure classic CLI) unless necessary, and always provide modern, cross-platform alternatives.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-performance-checklist.md
...rticles/storage/blobs/storage-performance-checklist.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a mild Windows bias by referencing Windows-specific tools (e.g., WireShark, NetMon) for network diagnostics, and by not providing Linux equivalents or cross-platform alternatives. Additionally, some sections (such as .NET configuration) are Windows-centric, and there is a lack of explicit Linux or cross-platform command-line examples (e.g., AzCopy usage, PowerShell vs. Bash/CLI). The order of mention for tools and examples tends to favor Microsoft/Windows technologies, with Linux or cross-platform considerations only briefly acknowledged or omitted.
Recommendations
- When mentioning diagnostic tools like WireShark and NetMon, include Linux alternatives such as tcpdump or Wireshark (noting its cross-platform nature).
- Provide explicit Linux/Bash command-line examples for tools like AzCopy, and clarify that AzCopy is cross-platform.
- Where .NET configuration is discussed, add references to equivalent settings or considerations for other languages and platforms (e.g., Java, Python, Node.js), and include links to relevant documentation.
- When listing client libraries and tools, mention Azure CLI and its cross-platform nature before or alongside PowerShell.
- Review the order of tool and example presentation to ensure Linux and cross-platform options are not consistently secondary to Windows/PowerShell.
- Add a section or call-out summarizing cross-platform support and best practices for both Windows and Linux environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/encryption-in-transit-for-nfs-shares.md
.../storage/files/encryption-in-transit-for-nfs-shares.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates some Windows bias, particularly in the registration instructions for preview features, where PowerShell is presented before Azure CLI. There are also references to PowerShell and Windows tools (e.g., PowerShell screenshots and cmdlets), even though the main focus of the guide is on Linux clients. However, the core technical instructions and examples for encrypting NFS data in transit are Linux-centric, with detailed steps for multiple Linux distributions and no actual Windows mounting instructions (since NFS Azure Files with EiT is Linux-only).
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more relevant for Linux users.
- Replace or supplement PowerShell screenshots with Linux terminal screenshots where appropriate.
- Avoid using the term 'cmdlet' when referring to Linux commands; use 'command' or 'CLI command' instead.
- Clarify early in the document that the feature is only supported on Linux, and remove any unnecessary references to Windows tools or PowerShell unless specifically relevant to management tasks that can only be done from Windows.
- Ensure all troubleshooting and verification screenshots are from Linux environments.
- If management tasks (such as registration) must be performed from Windows/PowerShell, provide equivalent Bash/CLI instructions and note any platform limitations.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-batch-create-sample.md
...storage/elastic-san/elastic-san-batch-create-sample.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page exclusively provides a PowerShell script example for batch creation of Azure Elastic SAN volumes, referencing a Windows-style file path and omitting any Linux or cross-platform alternatives. There is no mention of Bash, Azure CLI, or Linux-compatible scripting, and the use of PowerShell and Windows file paths is presented as the default approach.
Recommendations
- Include a Bash or Azure CLI script example for Linux/macOS users performing the same batch operation.
- Show file path examples in both Windows (e.g., D:\ElasticSan\TestCsv3.csv) and Linux (e.g., /home/user/ElasticSan/TestCsv3.csv) formats.
- Mention that the operation can be performed from any OS and provide guidance or links for installing and using Azure PowerShell on Linux/macOS, or suggest Azure CLI as an alternative.
- If PowerShell is required, clarify that PowerShell Core is cross-platform and provide instructions for Linux/macOS users.
- Consider reordering or presenting both Windows and Linux options side-by-side to avoid the impression that Windows is the primary or only supported environment.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-custom-domain-name.md
...n/articles/storage/blobs/storage-custom-domain-name.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation exhibits a moderate Windows bias. PowerShell is presented as a primary scripting interface alongside the Azure Portal and Azure CLI, with explicit PowerShell command examples and references. In several sections, PowerShell is listed before Azure CLI, and the CLI tab itself incorrectly instructs users to 'Run the following PowerShell command' instead of 'Azure CLI command.' No Linux-specific shell or scripting examples (such as Bash) are provided, and there is no mention of Linux tools or environments. The documentation assumes familiarity with PowerShell and Windows-centric tooling, which may disadvantage Linux users.
Recommendations
- Correct the Azure CLI sections to refer to 'Azure CLI command' instead of 'PowerShell command.'
- Add Bash shell examples for Azure CLI commands, demonstrating usage in a typical Linux or macOS terminal.
- Clarify that Azure CLI commands can be run on Windows, Linux, and macOS, and provide any OS-specific notes if needed (e.g., line continuation differences).
- Where PowerShell is mentioned, consider adding a note or tab for Bash or sh equivalents, especially for scripting scenarios.
- Review the order of tabs and examples; consider listing Azure CLI (cross-platform) before PowerShell (Windows-centric) to reduce perceived Windows-first bias.
- Audit for any other Windows-centric terminology or assumptions, and ensure parity in guidance for Linux users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-cli.md
...articles/storage/blobs/storage-quickstart-blobs-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is generally cross-platform, focusing on Azure CLI, which works on all major OSes. However, there are subtle Windows biases: the AzCopy example uses a Windows file path ('C:\myDirectory\myFile.txt') without a Linux/macOS equivalent, and no Linux/macOS example is provided for AzCopy. The only explicit file creation example uses 'vi', which is cross-platform but more common on Linux/macOS. Overall, the documentation could better demonstrate parity by including Linux/macOS-specific examples where Windows-specific patterns are shown.
Recommendations
- For every example using a Windows file path (e.g., 'C:\myDirectory\myFile.txt'), provide a Linux/macOS equivalent (e.g., '~/myDirectory/myFile.txt').
- In the AzCopy section, show both Windows and Linux/macOS command examples side by side.
- Explicitly state that AzCopy is available on all major platforms and provide installation links for each.
- Where file creation is demonstrated (e.g., using 'vi'), briefly mention alternatives for Windows users (e.g., 'notepad').
- Review all examples to ensure that neither OS is implicitly prioritized, and that users on any platform can follow along without confusion.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-planning.md
.../main/articles/storage/file-sync/file-sync-planning.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All deployment, management, and troubleshooting instructions assume or require Windows Server. Only Windows Server is supported for Azure File Sync agents, and all examples (such as PowerShell cmdlets) are Windows-specific. There are no Linux or cross-platform examples or guidance, and Linux is only mentioned in the context of direct SMB mounting, not as a sync agent or management platform.
Recommendations
- Clearly state early in the documentation that Azure File Sync is only supported on Windows Server, and explain the rationale.
- Provide a comparison table or section outlining what is and is not possible on Linux/macOS versus Windows, especially for hybrid and migration scenarios.
- Where possible, include Linux/macOS examples for direct SMB mounting and management, or link to relevant documentation.
- If Linux support is not planned, offer alternative solutions or migration paths for organizations with Linux-based file servers.
- Avoid presenting PowerShell/Windows tools as the only management interface; if REST APIs or CLI tools are available, provide cross-platform examples.
- Explicitly mention the lack of Linux agent support in the prerequisites and planning sections to set expectations.