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 401-425 of 1657 flagged pages
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-in-script.md ...rticles/storage/common/storage-use-azcopy-in-script.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides both Linux and Windows examples for scheduling AzCopy tasks, but Windows tools (Schtasks, batch files, escaping rules) are described in greater detail and with more context. Windows-specific patterns (batch file escaping, Schtasks usage) are explained thoroughly, while Linux equivalents (cron, shell scripting) receive less explanation. The order of presentation sometimes favors Windows, and some advanced scripting/automation topics (e.g., escaping SAS tokens) are only covered for Windows batch files, with no Linux shell equivalent.
Recommendations
  • Provide equivalent examples and explanations for Linux shell scripting, such as how to escape special characters in SAS tokens in bash scripts.
  • Ensure parity in the depth of explanation for Linux tools (e.g., more details on cron job creation, troubleshooting, and script placement).
  • Include PowerShell examples only if bash/zsh equivalents are also given.
  • Present Linux and Windows examples in parallel, with equal prominence and detail.
  • Add troubleshooting tips and advanced usage for Linux environments, similar to what is provided for Windows.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-extend-servers.md ...articles/storage/file-sync/file-sync-extend-servers.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is exclusively focused on Windows Server environments, with all examples, instructions, and screenshots tailored to Windows. It uses Windows-specific tools (Server Manager, Internet Explorer, PowerShell) and does not mention Linux or provide Linux equivalents or alternatives. There are no cross-platform notes, nor any guidance for non-Windows users.
Recommendations
  • Add a section clarifying platform support and explicitly state whether Azure File Sync is available for Linux servers or not.
  • If Linux is supported, provide equivalent instructions for deploying Azure File Sync on Linux, including setup, agent installation, and configuration steps.
  • Include Linux command-line examples (e.g., Bash, Azure CLI) alongside PowerShell commands where applicable.
  • Reference Linux tools and workflows (such as mounting SMB shares, using curl/wget for downloads, etc.) where relevant.
  • If Azure File Sync is Windows-only, make this clear early in the documentation and suggest alternative solutions for Linux environments (such as Azure File Share with SMB/NFS mounts, or third-party sync tools).
  • Consider adding a comparison table of features and limitations for Windows vs. Linux file server integration with Azure.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively provides a Windows PowerShell example for batch creation of Azure Elastic SAN volumes, referencing a Windows-style file path and omitting any equivalent Linux or cross-platform CLI examples. There is no mention of Bash, Azure CLI, or Linux file system conventions, which may hinder accessibility for Linux users.
Recommendations
  • Add a Bash/Azure CLI example for batch volume creation using a CSV file, demonstrating Linux file path conventions.
  • Include instructions for running the process on Linux/macOS, such as using Azure CLI or PowerShell Core on non-Windows platforms.
  • Mention cross-platform compatibility of the script and tools, or clarify any Windows-specific requirements.
  • Provide sample CSV file paths using Linux conventions (e.g., /home/user/ElasticSan/TestCsv3.csv) alongside Windows examples.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-cloud-tiering-policy.md ...es/storage/file-sync/file-sync-cloud-tiering-policy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing the Windows-specific PowerShell cmdlet `Invoke-StorageSyncFileRecall` as the only example of interacting with Azure File Sync cloud tiering policies. There are no Linux or cross-platform command-line examples, nor is there mention of Linux-compatible tools or workflows. The terminology and scenarios assume Windows server environments, with no guidance for Linux users.
Recommendations
  • Provide equivalent Linux command-line examples, if supported, such as using Azure CLI or REST API for file recall and policy management.
  • Clarify whether Azure File Sync cloud tiering features are available or supported on Linux, and if not, explicitly state the platform limitations.
  • Include references to cross-platform tools or interfaces (e.g., Azure Portal, Azure CLI) for managing cloud tiering policies.
  • Avoid using Windows-specific cmdlets as the sole example; present platform-neutral workflows or alternatives where possible.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-encryption-manage-customer-keys.md ...tic-san/elastic-san-encryption-manage-customer-keys.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides command-line examples exclusively using Azure PowerShell and Azure CLI, with PowerShell examples consistently presented before CLI. There are no Linux-specific shell examples (e.g., Bash scripts), nor are there any references to Linux-native tools or workflows. The structure and variable usage in examples (e.g., $KvName) are PowerShell-centric, which may be less familiar to Linux users. No mention is made of Linux-specific considerations, such as shell compatibility or environment setup.
Recommendations
  • Add Bash-specific examples for all CLI commands, using Linux shell variable syntax and conventions.
  • Include notes on environment setup for Linux users (e.g., installing Azure CLI on Linux, authentication differences).
  • Present CLI examples before PowerShell, or alternate the order, to avoid implicit prioritization of Windows tools.
  • Explicitly mention that Azure CLI works cross-platform and provide guidance for Linux/macOS users.
  • Where PowerShell variables are used, provide equivalent Bash variable usage for parity.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-disaster-recovery-best-practices.md ...ile-sync/file-sync-disaster-recovery-best-practices.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools and patterns such as Volume Shadow Copy Service (VSS), the Previous Versions tab, DFS-N, and PowerShell for configuration. There are no examples or guidance for Linux servers, nor any mention of Linux-compatible backup or restore strategies. The documentation assumes the on-premises server is Windows-based and omits consideration for cross-platform scenarios.
Recommendations
  • Include equivalent Linux guidance for on-premises disaster recovery, such as using rsync, LVM snapshots, or other Linux-native backup tools.
  • Provide Linux-specific examples for restoring data, configuring high availability, and managing file sync endpoints.
  • Mention cross-platform compatibility and limitations explicitly, clarifying which features are Windows-only and suggesting alternatives for Linux environments.
  • Add PowerShell alternatives (e.g., Bash scripts) for relevant configuration steps.
  • Reference Linux file system attributes and backup/restore patterns where appropriate.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-modify-sync-topology.md ...es/storage/file-sync/file-sync-modify-sync-topology.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific concepts (such as drive letters and Windows VM guidance) and omitting any mention of Linux or cross-platform scenarios. All operational instructions and examples assume a Windows environment, with no Linux equivalents or guidance provided.
Recommendations
  • Include explicit guidance for Linux servers where Azure File Sync is supported, or clarify if it is not supported.
  • When referencing drive letters or Windows-specific file paths, provide equivalent Linux path examples (e.g., /mnt/data).
  • If there are platform-specific limitations (e.g., Azure File Sync only works on Windows), state this clearly at the beginning of the article.
  • Where UI navigation or commands are described, note any differences for Linux environments or provide alternative instructions if applicable.
  • Review all linked articles to ensure Linux parity or add cross-references to Linux documentation where available.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, referencing only Windows Server and Azure VMs running Windows. Instructions exclusively mention installing the Azure File Sync agent on Windows, and the only data recovery example uses Robocopy, a Windows-specific tool. There are no Linux equivalents or examples provided, nor is there mention of Linux support or alternative tools.
Recommendations
  • Clarify whether Azure File Sync supports Linux servers. If not, explicitly state this limitation.
  • If Linux is supported, provide parallel instructions for Linux environments, including agent installation and registration steps.
  • Offer Linux-based data copy examples (e.g., using rsync) alongside Robocopy.
  • Ensure that references to tools and commands are platform-neutral or provide alternatives for each supported OS.
  • Consider reordering instructions to mention both Windows and Linux environments where applicable, or include a platform support matrix at the beginning.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-smb-protocol.md ...blob/main/articles/storage/files/files-smb-protocol.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a clear Windows bias. Windows terminology, tools, and examples (especially PowerShell) are prioritized throughout. Many advanced configuration and troubleshooting steps are described only for Windows, with PowerShell commands and Windows registry edits, while equivalent Linux (or macOS) guidance is missing. Even when cross-platform tools like Azure CLI are shown, Windows-specific client configuration (e.g., Set-SmbClientConfiguration) is referenced, and there is little to no mention of Linux SMB client configuration or troubleshooting. References to file system features and limitations are also Windows-centric.
Recommendations
  • Add Linux (and macOS) client configuration and troubleshooting steps for SMB Multichannel and SMB security settings, including examples for modifying smb.conf and using tools like smbclient or mount.cifs.
  • When describing how to set SMB channel encryption or protocol versions, include Linux equivalents (e.g., specifying vers=3.1.1, client min protocol, or cipher settings in smb.conf or mount options).
  • For advanced features or limitations, clarify how they apply to Linux clients and tools, and provide links to relevant Linux documentation.
  • Balance PowerShell examples with equivalent Bash/Linux shell commands where possible, especially for client-side configuration.
  • When referencing Windows tools or registry edits, provide a parallel section for Linux (and macOS) users, or explicitly state if a feature is not configurable on non-Windows clients.
  • In all lists and scenarios, avoid assuming Windows as the default; mention Linux and macOS clients equally, and provide parity in guidance and examples.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-resource-move.md .../articles/storage/file-sync/file-sync-resource-move.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through the exclusive use of PowerShell for command-line examples, and by not providing equivalent instructions for Linux or cross-platform CLI tools. The only scripting example for managing Azure File Sync resources is given in PowerShell, with no mention of Azure CLI, Bash, or other Linux-friendly approaches. The overall workflow assumes users are familiar with Windows-centric tools and patterns, and does not address Linux server scenarios or provide parity for non-Windows environments.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, especially for resource management and managed identity assignment.
  • Explicitly mention and document how to perform Azure File Sync operations from Linux environments, including using Bash and Azure CLI.
  • Clarify whether Azure File Sync supports Linux servers, and if so, include guidance and examples for those scenarios.
  • Ensure that portal instructions are platform-neutral and do not assume a Windows context.
  • Add a section or callout for Linux administrators, outlining any differences or considerations when managing Azure File Sync resources.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-configure-file-level-permissions.md ...torage-files-identity-configure-file-level-permissions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, tools, and patterns. All examples for mounting and configuring ACLs use Windows-specific commands (net use, icacls, Windows File Explorer, PowerShell), and there is no mention of Linux equivalents or how to manage file-level permissions from Linux clients. Windows terminology and tools are used exclusively or introduced before any cross-platform considerations. The only Linux reference is in the final 'Next step' section, which links to a separate page but does not provide any Linux-specific guidance or examples within the main content.
Recommendations
  • Add Linux-specific instructions and examples for mounting Azure file shares and managing permissions, including relevant SMB client commands (e.g., mount.cifs, smbclient) and ACL management tools (e.g., setfacl, getfacl).
  • Clarify whether Windows ACLs can be managed or enforced from Linux clients and, if not, explain the limitations and alternatives for Linux environments.
  • Provide parity in examples by including both Windows and Linux workflows side-by-side where possible, especially for mounting shares and configuring permissions.
  • Explicitly mention any cross-platform limitations or requirements for Azure Files ACLs, so Linux administrators understand what is and isn't possible.
  • Consider restructuring the documentation so that Windows and Linux approaches are presented with equal prominence, rather than Windows-first.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-faq.md .../blob/main/articles/storage/files/storage-files-faq.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Files and Azure File Sync demonstrates a strong Windows bias. Most operational examples, troubleshooting steps, and tool references are Windows-centric, with frequent mentions of Windows File Explorer, PowerShell/cmd commands, Windows registry edits, and Windows-specific behaviors. Linux and macOS are mentioned in introductory statements and in the NFS section, but practical examples, management steps, and troubleshooting guidance are almost exclusively provided for Windows environments. There are few, if any, Linux/macOS-specific instructions or parity in examples.
Recommendations
  • Provide equivalent Linux/macOS command-line examples (e.g., using mount, smbclient, or NFS utilities) alongside Windows/PowerShell commands for mounting, troubleshooting, and managing Azure file shares.
  • Include Linux/macOS-specific guidance for managing tiered files, handling file attributes, and troubleshooting common issues (e.g., using lsattr, setfattr, or stat for file attributes).
  • When discussing tools (e.g., AzCopy, file copy tools), clarify cross-platform support and provide usage examples for Linux/macOS shells.
  • Balance the order of presentation: when listing supported platforms or providing examples, alternate or parallelize Windows and Linux/macOS instructions rather than defaulting to Windows first.
  • Add troubleshooting and operational guidance for Linux/macOS environments, such as handling permissions, mounting issues, and integration with non-Windows authentication systems.
  • Where registry or Windows-specific configuration is discussed, note if there are equivalent settings or behaviors on Linux/macOS, or explicitly state if a feature is Windows-only.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-nas-hybrid.md ...es/storage/files/storage-files-migration-nas-hybrid.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
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, with all steps, examples, and tooling (e.g., RoboCopy, Azure File Sync agent) being Windows-centric. There are no Linux migration examples, nor are Linux-compatible tools or workflows mentioned. The migration route explicitly requires moving data to Windows Server before syncing to Azure, and all troubleshooting and cut-over steps assume a Windows environment.
Recommendations
  • Add guidance for migrating from NAS directly to Azure file shares without requiring an intermediate Windows Server, if supported.
  • Include Linux-based migration examples and tools (e.g., rsync, azcopy, SMB mounting on Linux) where possible.
  • Mention Linux-compatible alternatives to RoboCopy and provide example commands for those tools.
  • Clarify whether Azure File Sync or similar hybrid cloud features are available for Linux servers, and if not, suggest best practices for Linux environments.
  • Reorder sections or add parallel Linux workflows so that Linux administrators do not feel secondary to Windows users.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-whats-new.md ...cs/blob/main/articles/storage/files/files-whats-new.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page consistently prioritizes Windows-centric features, tools, and terminology. Windows and PowerShell are mentioned first or exclusively in several sections, especially regarding Azure File Sync, agent installation, and SMB protocol details. There are frequent references to Windows Server versions, PowerShell cmdlets, and Windows-specific SMB features, while Linux equivalents are either mentioned later, less prominently, or omitted. Examples and instructions for Linux are sparse or missing, particularly for agent installation and management tasks.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for agent installation, management, and authentication scenarios.
  • Ensure parity in tool references: mention Linux CLI commands (e.g., shell scripts, mount commands) and management workflows where PowerShell is referenced.
  • Highlight Linux compatibility and support in feature announcements (e.g., Azure File Sync, SMB/NFS features) and clarify any limitations or differences.
  • Add links to Linux-focused documentation pages wherever Windows-focused links are provided.
  • When listing supported platforms or protocols, avoid listing Windows first by default; alternate or use alphabetical order.
  • Include troubleshooting and best practices for Linux environments, not just Windows.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-linux-hybrid.md .../storage/files/storage-files-migration-linux-hybrid.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, focusing almost exclusively on Windows Server and Windows-native tools (notably Robocopy) for migration. Linux is only mentioned as a source, with no concrete Linux-side migration examples or tool recommendations. Windows tools and workflows are described in detail, while Linux alternatives are only briefly referenced and not demonstrated. The guide assumes migration to Windows is required, and all operational steps, troubleshooting, and examples are Windows-specific.
Recommendations
  • Provide concrete Linux-side migration examples, such as using rsync, scp, or other Linux-native tools for initial data transfer.
  • Include step-by-step instructions or command examples for copying data from Linux to Windows, not just referencing Robocopy.
  • Discuss and compare Linux copy tools' fidelity and limitations in more detail, possibly linking to or providing a table of options.
  • Offer guidance for scenarios where Windows Server is not the final destination, or where hybrid Linux/Windows environments are required.
  • Balance the presentation by listing Linux options before or alongside Windows tools, rather than only after or as an aside.
  • If Powershell or Windows-specific commands are shown, provide equivalent Linux shell commands where possible.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-cli.md ...zure-docs/blob/main/articles/storage/blobs/blob-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias primarily through the use of Windows-style file paths (e.g., C:\temp\) in all code samples, and references to creating files in Windows directories. There are no explicit Linux or cross-platform examples for file paths or file creation, and the instructions assume a Windows filesystem layout. The mention of AzCopy as a recommended tool is neutral, but the sample XML file location is given only as C:\temp, reinforcing the Windows-first approach. No PowerShell examples are present, but Bash is used throughout, which is cross-platform; however, the path conventions and file references are Windows-centric.
Recommendations
  • Provide parallel examples using Linux/macOS file paths (e.g., /tmp/, /home/user/) alongside Windows paths.
  • Explicitly state that Bash scripts and Azure CLI commands work on Linux/macOS and Windows, and clarify any platform-specific differences.
  • When referencing sample files (like blob-list.xml), include instructions for both Windows and Linux/macOS users on where to create and how to reference these files.
  • Use environment variables or platform-agnostic path construction in examples to avoid hardcoding Windows paths.
  • Mention that AzCopy is available on Linux/macOS and provide installation links for those platforms.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-nas-hybrid-databox.md ...ge/files/storage-files-migration-nas-hybrid-databox.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
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 operational platform. All examples, instructions, and tooling (e.g., Robocopy, Event Viewer) are Windows-centric, with no mention of Linux alternatives or cross-platform approaches. The migration workflow assumes the use of Windows Server for Azure File Sync, and Linux/NAS systems are only referenced as the source, not as possible targets or participants in the sync process.
Recommendations
  • Explicitly state that Azure File Sync currently only supports Windows Server, but provide guidance for Linux users on alternative migration strategies (e.g., using azcopy, rsync, or third-party tools).
  • Include Linux-based examples for copying data to Data Box (e.g., using SMB/CIFS mounts and Linux copy tools).
  • Mention and link to Azure Files NFS support and migration guides for Linux environments where applicable.
  • Clarify the limitations for non-Windows environments early in the documentation, and suggest best practices for Linux/NAS admins.
  • Where Robocopy is recommended, offer equivalent Linux commands (e.g., rsync) for copying data to Data Box SMB shares, if supported.
  • Add troubleshooting tips for Linux users interacting with Data Box or Azure Files.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-tutorial-queues.md ...ain/articles/storage/queues/storage-tutorial-queues.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments. Command-line examples and output consistently use Windows-specific shells (cmd, PowerShell) and Windows-style paths (e.g., C:\Tutorials). There is no mention of Linux or macOS equivalents, nor are bash or sh examples provided. The use of Visual Studio Code is cross-platform, but the instructions and sample outputs assume a Windows file system and terminal. This may make it less approachable for Linux or macOS users.
Recommendations
  • Include explicit instructions and examples for Linux/macOS users, such as using bash/zsh terminals and POSIX-style paths.
  • Show sample outputs using Linux/macOS conventions (e.g., /home/user/Tutorials, $ prompt).
  • Mention that all dotnet CLI commands work on Linux/macOS and provide any necessary platform-specific notes (e.g., permissions, environment variables).
  • Replace references to 'cmd, PowerShell' with 'terminal (cmd, PowerShell, bash, zsh, etc.)' and clarify that the tutorial is cross-platform.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., case sensitivity, file permissions).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/queues-storage-monitoring-scenarios.md .../storage/queues/queues-storage-monitoring-scenarios.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell examples first, providing detailed PowerShell commands, and omitting equivalent Linux shell (bash) or cross-platform SDK examples. The Azure CLI example is present, but there are no bash-specific instructions or Linux tool references. The .NET SDK example is also Windows-centric, with no mention of Python or other cross-platform SDKs. There is no discussion of Linux-native monitoring tools or patterns.
Recommendations
  • Add bash shell examples for querying metrics and logs using Azure CLI, showing usage on Linux/macOS.
  • Include SDK examples in Python or JavaScript to complement the .NET example, demonstrating cross-platform code.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide installation or usage notes for those platforms.
  • Avoid presenting PowerShell examples first; alternate or parallelize example order with bash/Azure CLI.
  • Reference Linux-native monitoring tools (e.g., cron jobs, systemd timers, or integration with Linux logging solutions) where relevant.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/data-management/cirrus-data-migration-guide.md ...artners/data-management/cirrus-data-migration-guide.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Links Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by linking primarily to Windows-specific Azure VM guides and referencing Windows documentation before Linux equivalents. While the main migration example uses a Linux source host, there are no explicit Linux or cross-platform command-line examples for Azure VM setup, and the quickstart and overview links are Windows-centric. There are also no PowerShell-specific commands, but Linux parity is lacking in the initial setup and reference materials.
Recommendations
  • Provide parallel links to both Windows and Linux Azure VM quickstart and overview documentation wherever VM setup is referenced.
  • Include explicit Linux and Windows command-line examples for common tasks (e.g., verifying VM readiness, mounting/unmounting disks) to ensure parity.
  • Balance references to Windows and Linux tools/utilities in all sections, especially in 'Next steps' and implementation prerequisites.
  • Clarify in the prerequisites and implementation steps that the process is applicable to both Windows and Linux hosts, and provide OS-specific notes or callouts where behaviors differ.
  • Consider including a table or section summarizing OS-specific steps and commands for both Windows and Linux environments.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/primary-secondary-storage/tiger-bridge-deployment-guide.md ...ary-secondary-storage/tiger-bridge-deployment-guide.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a strong Windows bias. All deployment steps and examples assume a Windows Server environment, referencing NTFS/ReFS file systems and requiring a Windows file server for installation. There are no Linux-specific instructions, examples, or screenshots. Windows tools and patterns (e.g., Windows Explorer shell extension, context menu integration) are mentioned exclusively, and the documentation does not provide parity for Linux environments or tools.
Recommendations
  • Add explicit instructions and examples for deploying Tiger Bridge on Linux servers, including supported file systems (e.g., ext4, XFS) and relevant configuration steps.
  • Include screenshots and CLI examples for Linux environments, such as using NFS/SMB mounts and configuring Tiger Bridge via Linux command line.
  • Mention Linux equivalents for Windows-specific features (e.g., file management via shell extensions), or clarify if such features are unavailable.
  • Provide guidance for integrating Tiger Bridge with Linux-based NAS systems, including step-by-step instructions.
  • Ensure that references to file systems, tools, and patterns are balanced between Windows and Linux, or clearly state platform limitations.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools (Azure Storage Explorer, PowerShell) are listed before cross-platform or Linux-native options, and examples for Linux-specific commands (such as setfacl, getfacl, or POSIX shell usage) are missing. The guidance for obtaining service principal object IDs uses Azure CLI, which is cross-platform, but does not mention Linux-native identity management patterns. There is no explicit example or guidance for managing ACLs using Linux tools or from a Linux shell, despite the POSIX ACL model being described. The documentation assumes familiarity with Windows tools and environments, and does not provide parity for Linux users who may want to interact with ACLs using native Linux commands or scripts.
Recommendations
  • Add explicit examples for managing ACLs using Linux shell commands and POSIX tools (e.g., setfacl, getfacl) where applicable.
  • Include guidance for Linux users on how to interact with Azure Data Lake Storage ACLs from a Linux environment, such as using Azure CLI in Bash, or scripting with curl and REST API.
  • Ensure that cross-platform tools (Azure CLI, REST API) are listed before Windows-specific tools (PowerShell, Storage Explorer) in example tables and guidance.
  • Reference Linux identity management and permission assignment patterns, especially when discussing service principals and group management.
  • Provide parity in troubleshooting and advanced features (e.g., sticky bit) by showing how to view and set these from Linux environments.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-centric tools (PowerShell, Azure Storage Explorer) are listed before or more prominently than Linux equivalents; PowerShell is frequently referenced for command-line operations, with no explicit Bash or Linux shell examples; Windows tools and patterns (e.g., Azure portal, PowerShell) are often mentioned first in tables and lists; and there is a lack of explicit Linux or Bash command examples, even though cross-platform tools like Azure CLI and AzCopy are referenced.
Recommendations
  • Provide explicit Linux/Bash shell examples alongside PowerShell for command-line operations.
  • Ensure Azure CLI examples are given equal prominence to PowerShell, and clarify cross-platform compatibility.
  • Mention Linux-native tools (e.g., Bash scripts, cron jobs) where relevant, especially for automation and ingestion.
  • List cross-platform tools (AzCopy, Azure CLI, REST) before Windows-specific tools in tables and lists.
  • Include guidance for using Azure Data Lake Storage from Linux environments, such as mounting via NFS or using Linux SDKs.
  • Clarify that Azure Storage Explorer and AzCopy are cross-platform, and provide installation/use instructions for Linux.
  • Add references to Linux-based orchestration tools (e.g., systemd, cron) for automation and monitoring.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-acl-azure-portal.md ...es/storage/blobs/data-lake-storage-acl-azure-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools (Azure Storage Explorer, PowerShell) before mentioning cross-platform alternatives (Azure CLI). There are no explicit Linux or macOS examples, nor is there guidance on using Linux-native tools or patterns. The ordering and tool selection suggest a preference for Windows environments.
Recommendations
  • Provide explicit Linux/macOS examples for managing ACLs, such as using Azure CLI commands in a bash shell.
  • Mention Azure CLI as a cross-platform first-class tool, and provide step-by-step instructions for its use alongside PowerShell.
  • Reference Linux-native scripting patterns (e.g., bash scripts) and clarify tool availability on non-Windows platforms.
  • Include screenshots or terminal output from Linux environments where appropriate.
  • Ensure parity in tool recommendations by listing Azure CLI before or alongside PowerShell and Storage Explorer.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-known-issues.md ...ticles/storage/blobs/data-lake-storage-known-issues.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned as a primary tool for managing soft-deleted blobs and directories, and Windows-specific tools such as AzCopy and Azure Storage Explorer are referenced without explicit mention of Linux alternatives or parity. The WASB (Windows Azure Storage Blob) driver is discussed before its Hadoop/Linux equivalent (ABFS), and PowerShell is listed before Azure CLI in some instructions. There are no explicit Linux shell examples or references to Linux-native tools or workflows.
Recommendations
  • Provide Linux shell (bash) examples alongside PowerShell for operations such as restoring soft-deleted blobs.
  • Explicitly mention cross-platform compatibility for tools like AzCopy and Azure Storage Explorer, and provide installation/use instructions for Linux.
  • List Azure CLI examples before or alongside PowerShell, as CLI is cross-platform.
  • Reference the ABFS driver before WASB when discussing Hadoop integrations, and clarify Linux/Hadoop support.
  • Add a section or note highlighting Linux support and any platform-specific considerations for Data Lake Storage management.
GitHub Create Pull Request
← Previous Page 17 of 67 Next →