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 376-392 of 392 flagged pages
Storage Best practices for configuring an Elastic SAN ...cles/storage/elastic-san/elastic-san-best-practices.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Image Bias
Summary
The documentation presents Windows examples and tooling first in several sections, including MPIO and iSCSI configuration. Windows-specific tools (PowerShell, Registry Editor, iSCSI Initiator app) are described in detail, with screenshots, while Linux equivalents are covered later or with less visual emphasis. Azure CLI is mentioned but PowerShell is referenced first for enabling Accelerated Networking. Screenshots for Windows configuration steps are provided before Linux, and more images are present for Windows workflows.
Recommendations
  • Alternate the order of Windows and Linux sections, or present them side-by-side to avoid Windows-first bias.
  • Provide equal visual aids (screenshots, step-by-step instructions) for Linux workflows, matching the detail given for Windows.
  • Reference Azure CLI before or alongside PowerShell for cross-platform parity.
  • Include explicit macOS instructions or notes where applicable, especially for iSCSI and MPIO configuration.
  • Ensure all configuration steps and troubleshooting guidance are equally detailed for Linux as for Windows.
GitHub Create Pull Request
Storage Connect Azure Elastic SAN to Azure Kubernetes over iSCSI ...rticles/storage/elastic-san/elastic-san-connect-aks.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation lists both Azure PowerShell and Azure CLI as prerequisites, but PowerShell (a Windows-centric tool) is mentioned before CLI. The example for retrieving volume information presents the Azure PowerShell command first, then the Azure CLI command. No Linux-specific tools or patterns are mentioned, but CLI parity is maintained. There are no PowerShell-only steps, and all critical tasks can be completed with Azure CLI, which is cross-platform.
Recommendations
  • List Azure CLI before Azure PowerShell in prerequisites and examples, as CLI is cross-platform and preferred for Linux/macOS users.
  • Explicitly note that Azure CLI works on Linux/macOS and provide installation links for those platforms.
  • Where PowerShell and CLI examples are given, alternate their order or group them together under clear headings (e.g., 'Using Azure CLI' and 'Using Azure PowerShell').
  • Add a brief note that all steps can be completed on Linux/macOS using Azure CLI.
GitHub Create Pull Request
Storage Backup Azure Elastic SAN volumes .../articles/storage/elastic-san/elastic-san-snapshots.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias by consistently listing PowerShell examples before Azure CLI, referencing Windows-specific backup coordination tools (Volume Shadow Service), and mentioning Windows applications first. However, Linux parity is maintained through the inclusion of Azure CLI examples and a brief mention of Linux tools (fsfreeze).
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present them side-by-side.
  • Expand the discussion of Linux backup coordination tools, providing more detail and examples (e.g., using fsfreeze, LVM snapshots, or application-consistent backup strategies for Linux).
  • Include explicit macOS/Linux shell commands where relevant, especially in CLI sections.
  • When referencing Windows tools (like Volume Shadow Service), provide equivalent Linux/macOS solutions with equal detail and prominence.
  • Add notes clarifying that Azure CLI works cross-platform and highlight any OS-specific considerations.
GitHub Create Pull Request
Storage Disaster recovery and failover for Azure Files ...main/articles/storage/files/files-disaster-recovery.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page references Azure PowerShell before Azure CLI and client libraries when describing how to query the Last Sync Time property, and lists PowerShell as a method for initiating account failover before CLI and API. There are no explicit Linux/macOS examples, and the only command-line tool named is PowerShell, which is Windows-centric (though available on Linux, it's less commonly used there). No Linux-specific tools or workflows are highlighted, and the documentation does not provide parity in example ordering or tool recommendations.
Recommendations
  • List Azure CLI before or alongside PowerShell when describing how to query properties or initiate failover, as CLI is more commonly used on Linux/macOS.
  • Provide explicit example commands for both PowerShell and Azure CLI, ensuring Linux/macOS users see relevant syntax.
  • Mention that PowerShell is cross-platform, but clarify that CLI is often preferred on Linux/macOS.
  • Include guidance or links for using REST API or SDKs from Linux/macOS environments.
  • Add a note or section highlighting Linux/macOS workflows for disaster recovery and failover tasks.
GitHub Create Pull Request
Storage GlusterFS to Azure Files Migration Guide ...in/articles/storage/files/glusterfs-migration-guide.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias: Windows examples and tools (Robocopy, PowerShell) are often presented first, and Windows-specific migration tooling is highlighted before Linux equivalents. The troubleshooting and verification steps use PowerShell/Windows commands before Linux alternatives. However, Linux guidance is present and reasonably detailed, with parity in migration steps and tool recommendations (rsync, fpsync).
Recommendations
  • Alternate the order of Windows and Linux sections, or present them side-by-side to avoid implicit prioritization.
  • Include Linux verification commands before or alongside Windows commands in the 'Verify migration succeeded' section.
  • Expand Linux migration tooling recommendations (e.g., mention additional tools like lsyncd, tar for special cases).
  • Provide more direct links to Linux-specific documentation and troubleshooting resources.
  • Ensure that all critical steps (mounting, migration, verification, troubleshooting) have equally detailed Linux instructions and examples.
GitHub Create Pull Request
Storage Configure a Site-to-Site VPN for Azure Files ...icles/storage/files/storage-files-configure-s2s-vpn.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation exhibits mild Windows bias, primarily by recommending Windows Server RRAS as the only example of an on-premises VPN appliance, mentioning it before any Linux alternatives, and referencing PowerShell throughout. However, the core Azure configuration steps are cross-platform, with both PowerShell and Azure CLI examples provided. There are no critical sections that are Windows-only, and mounting instructions for Windows, macOS, and Linux are linked at the end.
Recommendations
  • Explicitly mention and link to Linux-based VPN appliance guides (e.g., strongSwan, OpenVPN, libreswan) alongside Windows RRAS in the prerequisites section.
  • Provide example references or links for configuring Linux VPN appliances for S2S with Azure VPN Gateway.
  • When listing on-premises appliance options, avoid suggesting Windows Server RRAS as the default or only example.
  • Consider listing Azure CLI examples before PowerShell, or side-by-side, to reinforce platform neutrality.
  • Add a brief note clarifying that all Azure CLI commands work on Linux/macOS and Windows.
GitHub Create Pull Request
Storage Best practices for monitoring Azure Queue Storage .../storage/queues/queues-storage-monitoring-scenarios.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents PowerShell examples before Azure CLI, and only provides a .NET (C#) SDK code sample for programmatic access, which is most commonly used on Windows. There are no Linux/macOS-specific shell examples (e.g., Bash), nor are cross-platform SDKs (like Python or JavaScript) demonstrated. However, the Azure CLI example is cross-platform, and no critical tasks are Windows-only.
Recommendations
  • Provide Bash or shell script examples for Linux/macOS users alongside PowerShell.
  • Include SDK code samples in cross-platform languages such as Python or JavaScript.
  • Alternate the order of examples so that Azure CLI or Bash is shown before PowerShell, or present them side-by-side.
  • Explicitly mention that Azure CLI commands work on Linux/macOS as well as Windows.
  • Add notes or links for Linux/macOS users where portal instructions or screenshots are shown.
GitHub Create Pull Request
Storage Introduction to Azure Files ...n/articles/storage/files/storage-files-introduction.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page displays a mild Windows bias. Windows and PowerShell are mentioned before Linux equivalents in several sections, and Windows tooling (PowerShell, Azure File Sync) is highlighted more prominently than Linux alternatives. While Linux and macOS support is acknowledged, examples and tooling references tend to favor Windows, and Windows scenarios (such as Azure File Sync) are described in more detail.
Recommendations
  • Ensure Linux and macOS examples and tooling are mentioned with equal prominence and detail as Windows.
  • Add explicit references to Linux-native tools (e.g., mount, cifs-utils, NFS utilities) and scripting options (bash, shell scripts) alongside PowerShell.
  • Highlight Linux/macOS-specific features or integration patterns where relevant, such as automounting via fstab or using cron jobs for automation.
  • Provide parity in advanced scenarios, such as caching or synchronization, by mentioning or linking to Linux/macOS equivalents if available.
  • Where Windows-specific features (e.g., Azure File Sync) are described, clarify whether Linux/macOS alternatives exist or note their absence.
GitHub Create Pull Request
Storage Understand Azure Files Billing ...b/main/articles/storage/files/understanding-billing.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias through repeated references to Windows-specific concepts and tools, such as VSS (Volume Shadow Copy Service) and Windows File Server, especially in the context of snapshots and Azure File Sync. Windows is mentioned first in the table comparing OS storage unit labeling, and the explanations often use Windows terminology (e.g., 'Windows properties dialog') as the primary reference point. However, the page does not provide command-line examples or instructions that are Windows/Powershell-only, nor does it omit Linux/macOS equivalents for critical tasks. The bias is mostly in framing and terminology, not in actionable steps.
Recommendations
  • Include references to Linux/macOS equivalents when discussing features like snapshots (e.g., mention LVM snapshots or ZFS on Linux).
  • When describing file share mounting, clarify SMB/NFS usage on Linux/macOS and provide links to relevant documentation.
  • Balance terminology by referencing non-Windows tools and dialogs (e.g., Linux 'du' or 'ls' for file size, macOS Finder properties).
  • When discussing Azure File Sync, note that it is Windows-only and suggest alternatives for Linux/macOS users, if available.
  • In tables and explanations, alternate the order of OS references or provide equal detail for all platforms.
GitHub Create Pull Request
Storage Assign an Azure role for access to queue data ...ticles/storage/queues/assign-azure-role-data-access.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for assigning Azure roles, but PowerShell (typically associated with Windows) is presented before Azure CLI. There are no Linux/macOS-specific examples or notes, and PowerShell is given equal prominence to Azure CLI, despite CLI being more cross-platform. No Windows-only tools are mentioned, but the ordering and emphasis may create a slight bias toward Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and provide installation links for each platform.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, or link to cross-platform PowerShell documentation.
  • Consider including Bash or shell script examples where relevant, or reference automation approaches common to Linux/macOS users.
GitHub Create Pull Request
Storage Performance and scalability checklist for Queue Storage ...ticles/storage/queues/storage-performance-checklist.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a mild Windows bias. It references Windows-specific tools (e.g., Network Monitor), mentions PowerShell before Azure CLI, and provides .NET Framework configuration examples without equivalent Linux/macOS guidance. There are no explicit Linux/macOS examples or tool recommendations, and the order of presentation tends to favor Windows-centric technologies.
Recommendations
  • Include Linux/macOS equivalents for all tool recommendations (e.g., suggest tcpdump alongside Wireshark and Network Monitor).
  • Provide configuration/code examples for popular Linux/macOS development stacks (e.g., Python, Java) where .NET examples are given.
  • Mention Azure CLI before or alongside PowerShell, and clarify cross-platform support.
  • Explicitly state when recommendations apply to all platforms, and link to platform-specific guidance where available.
GitHub Create Pull Request
Storage Quickstart: Azure Queue Storage client library - .NET ...les/storage/queues/storage-quickstart-queues-dotnet.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions Windows-specific consoles (cmd, PowerShell) before Bash when instructing users to create the project, but otherwise provides cross-platform instructions and examples. No Windows-only tools, PowerShell-heavy examples, or missing Linux/macOS equivalents are present. The .NET SDK and CLI commands are inherently cross-platform.
Recommendations
  • List Bash first or equally alongside cmd and PowerShell when referencing console windows.
  • Explicitly state that all commands work on Linux/macOS terminals as well as Windows.
  • Consider adding a note confirming cross-platform compatibility for .NET CLI commands.
GitHub Create Pull Request
Storage Quickstart: Azure Queue Storage client library for JavaScript ...les/storage/queues/storage-quickstart-queues-nodejs.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page shows minor Windows bias in the 'Create the project' section, where Windows consoles (cmd, PowerShell) are mentioned before Bash, and Visual Studio Code is suggested as the editor without alternatives. However, all code and commands are cross-platform, and Linux/macOS users can follow the instructions without issue.
Recommendations
  • List Bash first or equally alongside cmd/PowerShell when mentioning consoles.
  • Explicitly state that all commands work on Linux/macOS terminals.
  • Suggest alternative editors (e.g., 'Open the project in your preferred code editor, such as Visual Studio Code, Sublime Text, or Vim').
  • Add a note confirming cross-platform compatibility for all steps.
GitHub Create Pull Request
Storage Tutorial: Work with Azure Queue Storage queues in .NET ...ain/articles/storage/queues/storage-tutorial-queues.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. Console examples and output use Windows-specific tools (cmd, PowerShell) and Windows-style paths (e.g., C:\Tutorials). The instructions mention 'cmd, PowerShell, or Azure CLI' as console options, listing Windows shells first and showing only Windows output. There are no explicit Linux/macOS terminal examples, nor any mention of Linux-specific patterns (e.g., bash, sh, or typical Linux file paths). However, the actual commands (dotnet, code .) are cross-platform, and the tutorial would work on Linux/macOS with minor adjustments.
Recommendations
  • Include Linux/macOS terminal examples and outputs alongside Windows examples.
  • Mention bash/zsh as alternative shells when referring to the console.
  • Show Linux/macOS file paths (e.g., /home/user/Tutorials) in at least one example.
  • Clarify that all commands work cross-platform and note any OS-specific differences.
  • Avoid listing Windows shells first; use neutral phrasing like 'in a terminal window (such as bash, cmd, PowerShell, or Azure CLI)'.
GitHub Create Pull Request
Storage Migrate your block data to Azure with Cirrus Data ...artners/data-management/cirrus-data-migration-guide.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias, primarily by referencing Windows resources and guides before Linux equivalents and lacking explicit Linux/macOS step-by-step examples. The main implementation guide links to Windows-focused Azure VM creation documentation and the 'Next steps' section prioritizes Windows VM documentation. While the migration process itself is described generically and does mention Linux as a source, there are no detailed Linux/macOS-specific instructions or troubleshooting tips, and no PowerShell or Windows-only tools are referenced.
Recommendations
  • Include direct links to Linux and macOS Azure VM creation guides alongside the Windows guide.
  • Provide explicit step-by-step migration examples for Linux and macOS hosts, including common commands and troubleshooting tips.
  • Ensure parity in 'Next steps' by linking to Linux/macOS VM documentation and migration guides.
  • Add notes or sections addressing OS-specific considerations, such as disk mounting/unmounting commands for Linux/macOS.
GitHub Create Pull Request
Storage Performance and scalability checklist for Table storage ...ticles/storage/tables/storage-performance-checklist.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates mild Windows bias by referencing Windows-specific tools (WireShark, NetMon), mentioning PowerShell before Azure CLI, and providing .NET Framework configuration examples without equivalent Linux/macOS or cross-platform code samples. There are no explicit Linux/macOS examples or tool recommendations, and Windows-centric terminology appears first in several sections.
Recommendations
  • Include Linux/macOS equivalents for network diagnostic tools (e.g., tcpdump, iftop) alongside WireShark and NetMon.
  • Mention Azure CLI before or alongside PowerShell when discussing supported tools.
  • Provide configuration/code examples for other languages and platforms (e.g., Python, Java, Node.js) and note any OS-specific considerations.
  • Clarify that WireShark is cross-platform and NetMon is Windows-only.
  • Add explicit notes or examples for Linux/macOS users where relevant (e.g., disabling Nagle algorithm, connection/thread pool settings).
GitHub Create Pull Request
Storage Get started with Storage Explorer ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/storage-explorer/vs-azure-tools-storage-manage-with-storage-explorer.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation generally presents Windows information first and gives more detail about Windows-specific tools (e.g., Azure Storage Emulator). While Linux/macOS installation steps are included and reasonably detailed, the local storage emulator section prioritizes the Windows-only Azure Storage Emulator before mentioning Azurite (cross-platform). There are no PowerShell-specific examples, but the overall structure and some tool recommendations are Windows-centric. Some troubleshooting and dependency links are more detailed for Ubuntu than other Linux distros, and SLES is noted as untested.
Recommendations
  • Present cross-platform tools (e.g., Azurite) before Windows-only tools in emulator sections.
  • Add parity in troubleshooting and installation instructions for all supported Linux distributions, not just Ubuntu.
  • Explicitly mention and provide examples for Linux/macOS command-line usage where relevant (e.g., installing via tar.gz, using snap commands).
  • Clarify support status for SLES and provide guidance for users on unsupported platforms.
  • Ensure that any references to Windows-specific requirements (e.g., .NET runtime) are matched with equivalent Linux/macOS instructions.
GitHub Create Pull Request
← Previous Page 16 of 16 Next →