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 76-100 of 392 flagged pages
Storage
Migrate to Azure Files Using RoboCopy
...cles/storage/files/storage-files-migration-robocopy.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. It exclusively recommends RoboCopy, a Windows-only tool, for migration to Azure Files, and all examples, instructions, and troubleshooting are centered around Windows Server and RoboCopy usage. Although the SMB protocol is mentioned as cross-platform and Linux is briefly referenced as a possible source, there are no Linux-specific migration instructions, examples, or equivalent tooling recommendations. The mounting instructions, command syntax, and optimization tips are all Windows-centric, leaving Linux/macOS users without actionable guidance.
Recommendations
- Provide equivalent migration instructions for Linux/macOS environments, such as using rsync, smbclient, or other SMB-compatible tools.
- Include Linux-specific examples for mounting Azure file shares and copying data.
- Discuss cross-platform alternatives to RoboCopy, such as AzCopy (with caveats), or third-party tools that support SMB on Linux/macOS.
- Clarify limitations and differences for Linux/macOS users, and link to relevant documentation for those platforms.
- Present examples for both Windows and Linux/macOS side by side, or in separate sections, to ensure parity.
Create Pull Request
Storage
On-premises NAS migration to Azure File Sync via Data Box
...ge/files/storage-files-migration-nas-hybrid-databox.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows Server as the migration target and exclusively uses Windows-native tools (Robocopy, Event Viewer) for migration and monitoring. There are no Linux/macOS migration examples, nor are Linux tools or workflows mentioned. All migration steps assume the use of Windows Server and Windows-specific utilities, which creates friction for users with Linux-based environments or those seeking platform-neutral guidance.
Recommendations
- Add Linux/macOS migration scenarios, including steps for copying data from NAS to Azure using Linux tools (e.g., rsync, azcopy, SMB/NFS mounts).
- Provide equivalent Linux commands and workflows alongside Robocopy, such as rsync or cp for file transfer and azcopy for direct Azure uploads.
- Clarify whether Azure File Sync can be used with Linux servers, and if not, suggest alternative hybrid cloud solutions for Linux environments.
- Include troubleshooting and monitoring guidance for Linux, such as using syslog, journalctl, or Azure CLI for sync status.
- Explicitly state platform limitations early in the document, so Linux/macOS users can quickly assess applicability.
Storage
Deploy Tiger Bridge Continuous Data Protection, Archive and Disaster Recovery with Azure Blob Storage
...up-archive-disaster-recovery/tiger-bridge-cdp-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily Windows-centric, requiring a Windows file server for deployment and referencing only Windows-native tools (Volume Shadow Copy Service, Windows Explorer, DFSR, Tiger Bridge Shell Extension). There are no Linux/macOS deployment instructions, examples, or tool references. All configuration and recovery steps assume a Windows environment, leaving Linux/macOS users without guidance or support.
Recommendations
- Explicitly state platform requirements and limitations at the beginning of the guide.
- Provide Linux/macOS compatibility information for Tiger Bridge (if available), or clarify if the product is Windows-only.
- If Tiger Bridge supports Linux/macOS, add equivalent deployment, configuration, and recovery instructions for those platforms.
- Include examples using Linux file servers, CLI tools, and file managers (e.g., Nautilus, Finder) where applicable.
- Reference Linux-native backup/restore tools and workflows alongside Windows tools.
- If Tiger Bridge is Windows-only, recommend alternative solutions for Linux/macOS users.
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 demonstrates a moderate Windows bias. Windows terminology, features, and PowerShell examples are frequently presented first or exclusively, especially for client configuration and troubleshooting. Registry and PowerShell instructions are provided only for Windows clients, with no equivalent Linux/macOS guidance for advanced SMB client configuration. While Azure CLI examples are cross-platform, client-side configuration and troubleshooting are Windows-centric, and references to Windows features (e.g., registry keys, Set-SmbClientConfiguration) lack Linux/macOS parity.
Recommendations
- Add equivalent Linux/macOS client configuration and troubleshooting guidance, especially for advanced SMB features (e.g., encryption cipher selection, multichannel support).
- Include Linux/macOS examples for mounting and configuring SMB shares, not just links in 'Next steps'.
- Clarify which SMB features and settings are relevant or supported on Linux/macOS clients, and provide references to appropriate tools (e.g., smb.conf, mount.cifs, smbclient).
- When discussing client-side configuration (e.g., enabling encryption ciphers), provide instructions for Linux/macOS (e.g., how to set ciphers in smb.conf) alongside Windows PowerShell examples.
- Balance the order of examples so that Linux/macOS are not consistently presented after Windows, or only as links.
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 and metadata caching, but several sections show Windows bias. Windows tools (robocopy, diskspd.exe, PowerShell) are used for performance verification and examples, with no Linux equivalents provided. PowerShell is the only CLI shown for feature registration, and Windows configuration steps precede Linux instructions. Linux examples are present for mounting, but Linux performance testing and verification steps are missing.
Recommendations
- Add Linux equivalents for performance testing (e.g., fio, dd) and verification commands for SMB Multichannel connections.
- Include Azure CLI or Bash examples for feature registration alongside PowerShell.
- Provide guidance for Linux troubleshooting and configuration verification, similar to the Windows PowerShell steps.
- Balance the order of examples so Linux and Windows instructions are presented with equal prominence.
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 and references a Windows-style file path (e.g., D:\ElasticSan\TestCsv3.csv). There are no Bash, Azure CLI, or cross-platform examples, nor any mention of how to perform the task on Linux or macOS. This creates friction for non-Windows users.
Recommendations
- Provide equivalent Bash or Azure CLI script examples for Linux/macOS users.
- Use cross-platform file path examples (e.g., $HOME/ElasticSan/TestCsv3.csv) or clarify path differences.
- Explicitly state PowerShell Core (pwsh) compatibility on Linux/macOS if applicable, or provide instructions for installing PowerShell on those platforms.
- Add a section or note addressing Linux/macOS users and their workflow.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a moderate Windows bias. In the 'Disconnect volumes from clients' section, Windows instructions and PowerShell scripts are presented first, with Linux instructions following. PowerShell is emphasized throughout, and Windows tools/scripts are referenced explicitly. While Azure CLI examples are provided (which are cross-platform), the initial focus and scripting guidance favor Windows users.
Recommendations
- Present Linux and Windows instructions in parallel or in a neutral order, rather than always listing Windows first.
- Provide Bash shell script examples for Linux users, not just Python scripts.
- Clearly indicate that Azure CLI commands work on all platforms, and consider leading with CLI examples.
- Where possible, use platform-agnostic language and tools, or provide equal depth for both platforms.
- Add macOS-specific notes if there are any platform-specific considerations.
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-creating Azure Elastic SAN volumes, assumes use of Windows-style file paths, and does not mention or provide any examples for Bash, Azure CLI, or cross-platform scripting. There is no guidance for Linux or macOS users.
Recommendations
- Add equivalent Bash or Azure CLI script examples for Linux/macOS users.
- Use cross-platform file path examples or clarify that file paths should be adapted for the user's OS.
- Explicitly state that the PowerShell script can be run on PowerShell Core (pwsh) on Linux/macOS, if applicable.
- Mention prerequisites and installation steps for non-Windows environments.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a moderate Windows bias. Windows/Powershell examples and scripts are consistently presented before their Linux/Azure CLI equivalents. The 'Disconnect volumes from clients' section provides a PowerShell script for Windows and a Python script for Linux, but the Windows instructions and parameters are listed first. In all resource deletion sections, PowerShell tabs precede Azure CLI tabs, and there are no Bash or native Linux shell examples. The overall structure and ordering favor Windows users and tools.
Recommendations
- Present Azure CLI (cross-platform) examples before or alongside PowerShell examples.
- Alternate the order of Windows and Linux sections, or combine them where possible.
- Add Bash or shell script examples for Linux users where appropriate.
- Standardize parameter naming and descriptions across platforms for clarity.
- Explicitly mention that Azure CLI works on all platforms, and link to installation guides for Linux/macOS.
Storage
Plan for an Azure Files deployment
.../main/articles/storage/files/storage-files-planning.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits moderate Windows bias. Azure File Sync is described as a Windows Server-only solution, and Windows terminology and tools (Active Directory, SMB, PowerShell) are referenced more frequently and often before Linux equivalents. In protocol and identity sections, Windows OS versions are listed first and in more detail, while Linux is mentioned secondarily. There are references to using PowerShell and CLI for management and backup, but Linux-specific tools and workflows are not described. Examples and guidance for Linux (and macOS) users are limited or deferred to other documentation.
Recommendations
- Provide explicit Linux and macOS examples for mounting, managing, and backing up Azure file shares, including CLI commands and configuration steps.
- Include parity in tool recommendations (e.g., show Linux CLI workflows alongside PowerShell).
- Clarify limitations and alternatives for Linux users regarding Azure File Sync and other Windows-centric features.
- List supported OSes in a neutral order or group them by protocol rather than by Windows-first.
- Add links to Linux/macOS-specific guides wherever Windows tools or workflows are mentioned.
Storage
Zonal Placement for Azure File Shares
...cs/blob/main/articles/storage/files/zonal-placement.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides command-line examples exclusively using Azure PowerShell, which is primarily a Windows-centric tool. There are no CLI examples for Linux/macOS users (e.g., Azure CLI or Bash). The structure presents PowerShell as the only scripting option, and does not mention or provide parity for Linux-native tools or workflows. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Azure CLI/bash.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI can be used and provide links to Azure CLI documentation.
- Consider reordering or presenting both PowerShell and Azure CLI examples side-by-side, or allow users to select their preferred platform/tool via tabs.
- Clarify any limitations or differences between PowerShell and Azure CLI for these operations, if any exist.
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 for interactive examples (such as prompting for secrets/passwords) and references Windows-specific tools like Export-PfxCertificate. Guidance for secure secret entry is only shown in PowerShell, with no Linux shell equivalent. Windows tools and patterns (PowerShell, certificate store) are mentioned before or instead of Linux alternatives, and the Azure CLI section uses different environment variable values for Windows and Linux without clear explanation.
Recommendations
- Provide equivalent secure secret entry examples for Linux shells (e.g., using 'read -s' in bash) alongside PowerShell prompts.
- Mention Linux alternatives to Windows certificate management tools (e.g., 'openssl' for exporting certificates).
- Clarify why environment variable values differ between Windows and Linux for Azure CLI integration, and ensure parity if possible.
- Where PowerShell is used for interactive examples, also show bash/zsh equivalents for Linux/macOS users.
- Avoid referencing Windows certificate store and Export-PfxCertificate without mentioning Linux/macOS certificate handling.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux troubleshooting steps, but Windows tools (iscsicli, mpclaim, PowerShell scripts) are frequently mentioned first or exclusively in some sections. Windows-specific scripts and parameters are highlighted, and PowerShell is referenced for configuration changes. Linux equivalents are present but sometimes secondary, and some examples (like session limits) are Windows-only.
Recommendations
- Ensure Linux examples and tools (e.g., iscsiadm, multipath) are mentioned first or alongside Windows equivalents.
- Provide parity in troubleshooting steps, including session limits and configuration changes for Linux/macOS.
- Include Bash or Python script examples for Linux where PowerShell scripts are provided for Windows.
- Clarify any OS-specific limitations and provide workarounds or alternatives for Linux/macOS users.
- Where possible, use cross-platform Azure CLI commands and avoid Windows-centric terminology.
Storage
What's New in Azure Files and Azure File Sync
...cs/blob/main/articles/storage/files/files-whats-new.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows terminology, tools (PowerShell), and features (Azure File Sync agent for Windows, Windows Server support) are frequently mentioned, often before or in greater detail than Linux equivalents. PowerShell and Windows-centric management patterns are referenced more often than Linux alternatives. Some features and enhancements are described with a Windows-first perspective, and Linux-specific examples or parity details are sometimes missing or less emphasized.
Recommendations
- Ensure Linux and macOS management tools (e.g., Bash, shell scripts, Linux CLI examples) are mentioned alongside PowerShell and Windows tools.
- Provide explicit Linux/macOS usage examples for Azure File Sync, mounting shares, and management tasks wherever Windows examples are given.
- Highlight parity and limitations for Linux/macOS users in feature descriptions, especially for agent extensions and authentication scenarios.
- Balance the order of presentation so Linux/NFS features are not consistently listed after Windows/SMB features.
- Add links to Linux/macOS documentation and troubleshooting guides in 'See also' sections.
Storage
Improve SMB Azure File Share Performance
...cs/blob/main/articles/storage/files/smb-performance.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides both Windows and Linux coverage for SMB Multichannel, but Windows examples, tools, and configuration steps are presented first and in greater detail. Windows-specific tools (robocopy, diskspd.exe, PowerShell) are used for performance testing and verification, with no Linux equivalents or examples provided. Registration steps for features use only Azure PowerShell and portal, omitting CLI or Linux-native options. References to further documentation are Windows-centric.
Recommendations
- Provide Linux equivalents for performance testing (e.g., fio, dd, or ioping) and show example commands.
- Include Linux methods for verifying SMB Multichannel status and configuration (e.g., using smbstatus, dmesg, or mount options).
- Add Azure CLI examples for feature registration alongside PowerShell and portal instructions.
- Balance references to documentation by including links to Linux SMB Multichannel resources (e.g., Samba documentation).
- Present examples for both platforms in parallel tabs or sections, rather than Windows-first.
- Clarify any platform-specific limitations or differences in feature support.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools and workflows (such as Robocopy and the Previous Versions tab in File Explorer) are described in detail, with step-by-step instructions and screenshots. These Windows features are presented before Linux equivalents, and Linux-specific instructions are less detailed and appear later in the document. There is a lack of parity in example depth, especially for restoring SMB snapshots on Linux, where only mounting is described, not browsing or restoring files. Windows tools (Robocopy, File Explorer) are mentioned exclusively for local restore, while Linux alternatives are not discussed. PowerShell examples are present throughout, but Linux shell alternatives are limited to Azure CLI and basic mount/cp commands.
Recommendations
- Provide Linux/macOS-specific examples for restoring files from SMB snapshots, including browsing and copying files after mounting.
- Include parity in screenshots and step-by-step instructions for Linux workflows, similar to those provided for Windows.
- Mention and demonstrate Linux-native tools (e.g., rsync, cp) for copying/restoring files from mounted SMB/NFS snapshots.
- Clarify which features (such as Previous Versions) are Windows-only, and suggest Linux/macOS alternatives where possible.
- Ensure that example order alternates or is grouped by platform, rather than consistently presenting Windows first.
Storage
Authorize access to blobs using Microsoft Entra ID
...orage/blobs/authorize-access-azure-active-directory.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It repeatedly references PowerShell and the Azure portal (both Windows-centric tools) before mentioning Azure CLI, and does not provide explicit Linux/macOS examples or guidance. There are no references to Linux-specific tools, shell environments, or cross-platform command-line patterns. The examples and instructions assume familiarity with Windows tools, which may create friction for Linux/macOS users.
Recommendations
- Provide explicit Linux/macOS examples for command-line operations, such as using Bash with Azure CLI.
- Mention cross-platform compatibility of Azure CLI and clarify usage on Linux/macOS (e.g., installation, authentication).
- Include screenshots or walkthroughs for Linux/macOS environments where relevant.
- Avoid listing PowerShell before Azure CLI, or present both equally, noting their platform compatibility.
- Reference Linux-native tools (e.g., curl, wget) for REST API calls where appropriate.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed PowerShell examples for monitoring Azure Blob Storage metrics, with PowerShell presented before Azure CLI. This ordering and emphasis may create friction for Linux/macOS users, as PowerShell is primarily a Windows tool, although it is available cross-platform. No Linux-specific tools (e.g., Bash scripts) or explicit Linux/macOS guidance is given, but Azure CLI examples are present and are cross-platform.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is natively cross-platform and preferred by many Linux/macOS users.
- Add explicit notes or sections highlighting that Azure CLI commands work on Linux/macOS and Windows.
- Include Bash script examples or references for common monitoring tasks.
- Clarify that PowerShell Core is available on Linux/macOS, if PowerShell examples are retained.
- Consider adding troubleshooting tips or environment setup instructions for Linux/macOS users.
Storage
Perform a point-in-time restore on block blob data
...articles/storage/blobs/point-in-time-restore-manage.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias by consistently presenting PowerShell examples and instructions before Azure CLI equivalents. PowerShell, a Windows-centric tool, is featured heavily, with detailed command usage and explanations. The Azure CLI examples, which are cross-platform and preferred by many Linux/macOS users, are present but always follow PowerShell, and there is no mention of Bash scripting or Linux-specific considerations. No Linux/macOS-specific tooling or patterns are referenced, and screenshots are exclusively of the Azure Portal (which is platform-agnostic).
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to prioritize cross-platform usage.
- Explicitly mention that Azure CLI works on Linux/macOS and provide installation links or notes for those platforms.
- Include Bash script snippets or usage patterns where appropriate, especially for automation scenarios.
- Add a short section or note for Linux/macOS users, clarifying tool compatibility and any OS-specific caveats.
- Consider balancing example order (alternating PowerShell and CLI first) or grouping by platform.
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
Missing Linux Example
Summary
The documentation references Windows-centric tools such as Azure PowerShell and AzCopy for disaster recovery and data copying, and lists them before or without mentioning Linux/macOS alternatives. There are no explicit Linux/macOS command examples or mentions of platform-neutral tools like Azure CLI, and no guidance for Linux users on performing equivalent operations.
Recommendations
- Include Azure CLI examples for all operations, as it is cross-platform and widely used on Linux/macOS.
- When mentioning AzCopy, clarify that it is available for Windows, Linux, and macOS, and provide installation and usage instructions for each platform.
- List platform-neutral tools (e.g., REST API, Azure CLI) before platform-specific ones like PowerShell.
- Add explicit Linux/macOS command examples for data copying, failover initiation, and other key tasks.
- Avoid implying that PowerShell is the default or only option for scripting Azure Storage operations.
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 Azurite shows a notable Windows bias. Visual Studio and Visual Studio Code (Windows-centric tools) are presented first and in detail, with specific instructions and screenshots. Command-line examples consistently use Windows-style paths (e.g., c:\azurite) and never mention Linux/macOS equivalents (e.g., /home/user/azurite or ~/azurite). The location of the Azurite executable is only described for Windows installations of Visual Studio. There are no explicit Linux/macOS instructions, examples, or screenshots, and no mention of platform-specific considerations for those environments.
Recommendations
- Add Linux/macOS-specific instructions and examples for installing and running Azurite, especially for npm, Docker, and GitHub methods.
- Include command-line examples using POSIX-style paths (e.g., /home/user/azurite) alongside Windows paths.
- Clarify that Azurite works cross-platform and note any platform-specific differences or caveats.
- Provide guidance for locating the Azurite executable on Linux/macOS if installed via npm or other methods.
- Add screenshots or terminal output from Linux/macOS environments where appropriate.
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 demonstrates a moderate Windows bias, particularly in the Azure File Sync section, which is exclusively for Windows file servers and emphasizes Windows protocols and features (NTFS, SMB, Windows Server). Windows-centric tools and terminology (e.g., Azure PowerShell, Windows Server protocols) are mentioned before or more prominently than Linux equivalents. While Linux-friendly tools (AzCopy, Rsync, NFS, Data Box Gateway) are referenced, examples and guidance for Linux scenarios are less detailed or absent, and Windows migration patterns are described first and in greater depth.
Recommendations
- Add explicit Linux migration scenarios and examples, especially for NFS sources and Rsync usage.
- Provide parity in step-by-step instructions for both Windows and Linux environments, including PowerShell and Bash/CLI equivalents.
- Clarify which tools are cross-platform and highlight Linux/macOS compatibility where applicable.
- Include references to Linux file system permissions and attributes (e.g., POSIX ACLs) alongside NTFS.
- Ensure graphical and command-line tool instructions (e.g., AzCopy, Storage Explorer) include Linux/macOS installation and usage notes.
Storage
Require secure transfer to ensure secure connections
...cles/storage/common/storage-require-secure-transfer.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed PowerShell examples and instructions before Azure CLI examples, indicating a Windows-first and PowerShell-heavy bias. While Azure CLI is cross-platform and included, the PowerShell section is more prominent and detailed, and is presented before CLI, which may create friction for Linux/macOS users. No Linux-specific tools or shell examples (e.g., Bash) are provided, and there is no mention of platform-specific considerations for non-Windows environments.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Add Bash or shell script examples for common operations, especially for checking and setting the secure transfer property.
- Explicitly mention that Azure CLI works on Linux/macOS and provide installation links or notes for those platforms.
- Consider including REST API curl examples, which are platform-agnostic.
- Balance the depth of explanation between PowerShell and CLI sections.
Storage
Call REST API operations with Shared Key authorization
.../main/articles/storage/common/storage-rest-api-auth.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing Windows development tools (Visual Studio), providing only C# code samples, and mentioning Windows-specific utilities (Fiddler) for network inspection. There are no Linux/macOS development environment instructions, nor alternative tooling suggestions for non-Windows platforms. The guidance assumes a Windows-centric workflow and does not address how to perform the same tasks on Linux or macOS, which may create friction for non-Windows users.
Recommendations
- Include instructions for setting up a development environment on Linux/macOS, such as using VS Code, JetBrains Rider, or MonoDevelop.
- Provide C# build/run instructions using .NET Core CLI (dotnet build/run), which is cross-platform.
- Suggest cross-platform network inspection tools (e.g., Wireshark, mitmproxy) alongside Fiddler.
- Explicitly state that the sample code works on Linux/macOS and provide troubleshooting tips for those platforms.
- Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
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 Windows Command Shell (cmd.exe) specifically when discussing quoting conventions. There are no explicit Linux/macOS path examples (e.g., '/home/user/myDirectory'), nor is there mention of Linux/macOS shell usage beyond quoting. This creates a subtle Windows-first bias and may cause confusion for Linux/macOS users.
Recommendations
- Include Linux/macOS path examples (e.g., '/home/user/myDirectory') alongside Windows examples.
- Explicitly mention Linux/macOS shells (e.g., bash, zsh) in tips about quoting and command usage.
- Alternate the order of examples so that Linux/macOS examples are shown first in some sections.
- Add a note clarifying that AzCopy works cross-platform and provide OS-specific guidance where relevant.