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 726-750 of 1657 flagged pages
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-overview.md ...cles/storage/files/storage-files-migration-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits a clear Windows bias. Windows Server migration scenarios are listed first and in greater detail, with multiple Windows-specific tools (RoboCopy, Azure File Sync, Storage Migration Service) recommended and described. Linux migration is mentioned only briefly, with no detailed examples or tool guidance beyond Azure Storage Mover. Windows tools and patterns (NTFS ACLs, RoboCopy, TreeSize) are referenced exclusively or before Linux equivalents. There are no Linux-specific file-copy tool recommendations or examples, and PowerShell/Windows command-line tools are implicitly prioritized.
Recommendations
  • Add detailed Linux migration examples, including step-by-step guides for SMB file share migration from Linux servers.
  • Include Linux-native file-copy tools (e.g., rsync, smbclient, cifs-utils) in the migration tool tables and discuss their fidelity and suitability.
  • Provide parity in tool descriptions, listing Linux options alongside Windows tools (not just Azure Storage Mover).
  • Offer guidance on preserving file metadata and ACLs when migrating from Linux SMB shares, including mapping between Linux and Azure Files permissions.
  • Ensure Linux scenarios are not relegated to a single row or brief mention; expand coverage to match Windows depth.
  • Consider including sample commands for Linux migration, similar to the RoboCopy/PowerShell examples for Windows.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-networking-overview.md ...les/storage/files/storage-files-networking-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 several signs of Windows bias. Windows terminology, tools, and examples (e.g., PowerShell, Windows Server, SMB over QUIC) are presented first or exclusively in key sections. DNS resolution is demonstrated with PowerShell's Resolve-DnsName, with only a brief mention of nslookup for Linux. The SMB over QUIC section is entirely Windows-centric, with no mention of Linux alternatives or parity. References to Azure File Sync and caching are focused on Windows Server. Linux-specific instructions or parity are generally missing or relegated to links, not inline examples.
Recommendations
  • Provide Linux command-line examples alongside or before Windows/PowerShell examples (e.g., show nslookup and dig for DNS resolution).
  • Explicitly mention Linux support and limitations for SMB and NFS scenarios, including mounting commands and troubleshooting.
  • Include Linux equivalents for advanced features (e.g., SMB over QUIC, if/when available, or note lack of support).
  • Balance references to Windows Server tools (e.g., Azure File Sync) with Linux-based caching or synchronization solutions, or clarify Windows-only features.
  • Ensure links to Linux guides are as prominent as Windows ones, and consider inline Linux walkthroughs where appropriate.
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-08 00:53
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 consistently referencing Windows-specific tools (cmd, PowerShell), showing command-line output with Windows paths and prompts, and omitting explicit Linux/macOS equivalents. All example outputs use Windows-style paths (e.g., C:\Tutorials), and there is no mention of Linux shells or how commands would look/run on Linux/macOS. The instructions for running commands and interpreting output are tailored to Windows environments, and there are no notes or examples for Linux users.
Recommendations
  • Explicitly mention that all dotnet CLI commands work on Linux/macOS terminals (bash, zsh, etc.), and provide example commands/output for those platforms.
  • Replace or supplement Windows-specific references (cmd, PowerShell, C:\ paths) with cross-platform alternatives (e.g., 'terminal', 'bash', '~/Tutorials').
  • Add notes or callouts where behavior or output may differ on Linux/macOS (e.g., path formats, shell prompts).
  • Include screenshots or sample outputs from Linux/macOS environments alongside Windows examples.
  • Avoid using Windows-centric terminology (e.g., 'console window such as cmd, PowerShell') as the default; instead, use 'terminal' or 'command-line interface' and list Windows, Linux, and macOS options equally.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-snapshots-files.md ...main/articles/storage/files/storage-snapshots-files.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (Robocopy, File Explorer 'Previous Versions') are described in detail, with step-by-step instructions and screenshots, whereas Linux equivalents (such as mounting SMB snapshots or restoring from NFS snapshots) are covered in less detail and appear later in the document. Windows restore workflows are presented before Linux ones, and there are no examples for restoring individual files from SMB snapshots on Linux (only mounting is described). PowerShell is consistently presented as a primary automation tool, with no mention of Bash scripting or Linux-native automation. Windows-centric terminology and patterns (e.g., VSS, File Explorer) are used without Linux equivalents.
Recommendations
  • Provide Linux-specific examples for restoring individual files from SMB snapshots, not just mounting.
  • Include Bash scripting examples for snapshot management and automation, alongside PowerShell.
  • Present Linux workflows (mounting, restoring, deleting) in parallel with Windows workflows, rather than after.
  • Mention Linux-native tools (e.g., rsync, cp) for copying/restoring files from mounted snapshots.
  • Add screenshots or terminal output for Linux workflows to match the detail given to Windows examples.
  • Clarify limitations and feature parity between Windows and Linux at the beginning of the document.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/authorize-access-azure-active-directory.md ...rage/queues/authorize-access-azure-active-directory.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 repeatedly mentioning PowerShell and Azure CLI together, with PowerShell always listed first. There are no explicit Linux-specific examples, nor is there mention of Linux-native tools or shell environments. The instructions and references focus on PowerShell and Azure CLI, which, while cross-platform, are often associated with Windows workflows. No bash or Linux command-line examples are provided, and there is no guidance for Linux users on authentication or access patterns.
Recommendations
  • Include explicit bash or Linux shell examples alongside PowerShell and Azure CLI instructions.
  • Alternate the order of PowerShell and CLI mentions, or clarify that both are cross-platform.
  • Reference Linux-native tools or workflows where appropriate (e.g., az CLI in bash, environment variable usage in Linux).
  • Add a section or note for Linux users, highlighting any differences or considerations when authorizing access to queues.
  • Ensure that screenshots or UI references do not assume a Windows environment.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/data-management/dobimigrate-quick-start-guide.md ...tners/data-management/dobimigrate-quick-start-guide.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Azure portal (a GUI-centric, Windows-friendly tool) for all configuration steps, omitting any Linux CLI or automation examples. All network monitoring tool recommendations are Windows-oriented (SolarWinds, Paessler PRTG, Cisco Network Assistant, WhatsUp Gold), with no mention of Linux-native tools (e.g., iftop, nload, vnStat, iperf). There are no Linux shell, Azure CLI, or PowerShell examples, nor any guidance for users operating from Linux environments.
Recommendations
  • Add Linux-centric instructions for Azure Files setup, such as using Azure CLI or REST API from a Linux shell.
  • Include examples of configuring and accessing Azure File shares from Linux clients (e.g., using mount.cifs, smbclient).
  • List Linux-native network monitoring tools (iftop, nload, vnStat, iperf) alongside Windows tools.
  • Provide automation examples using shell scripts or Azure CLI for key steps (storage account creation, access key retrieval, firewall configuration).
  • Clarify that DobiMigrate can be operated from Linux environments, if applicable, and link to relevant documentation.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/tables/storage-performance-checklist.md ...ticles/storage/tables/storage-performance-checklist.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. It references Windows-centric tools (WireShark, NetMon), mentions PowerShell before Azure CLI, and provides .NET Framework-specific configuration examples without Linux or cross-platform equivalents. There are no explicit Linux shell or tool examples, and troubleshooting/networking guidance is oriented toward Windows environments. The .NET configuration section is Windows/.NET Framework-heavy, with only passing mention of other languages or platforms.
Recommendations
  • Include Linux-specific troubleshooting tools (e.g., tcpdump, iftop, nload) alongside WireShark and NetMon.
  • Provide Azure CLI examples before or alongside PowerShell, especially for cross-platform users.
  • Add configuration/code examples for other languages and platforms (e.g., Python, Java, Node.js) and clarify how to adjust connection/thread limits in those environments.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users where relevant.
  • Ensure that tool recommendations and examples are balanced between Windows and Linux, or are platform-neutral where possible.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/backup-archive-disaster-recovery/datadobi/datadobi-solution-guide.md ...-disaster-recovery/datadobi/datadobi-solution-guide.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure portal (a web GUI often associated with Windows workflows) for all configuration steps, without mentioning or providing examples for Linux CLI tools (such as Azure CLI or REST API usage). All operational and troubleshooting guidance is centered on portal-based workflows, and no Linux-specific tools, shell commands, or PowerShell alternatives are discussed. Additionally, network assessment tools listed are primarily Windows-centric or commercial solutions, with no mention of open-source Linux alternatives.
Recommendations
  • Add equivalent instructions for configuring Azure Storage using Azure CLI and REST API, with example commands suitable for Linux environments.
  • Include examples of how to retrieve storage account keys, create containers, and manage access using Linux shell commands.
  • List open-source, Linux-friendly network monitoring tools (e.g., iftop, nload, vnstat, netstat, iperf) alongside commercial Windows tools.
  • Provide troubleshooting and support guidance for users working from Linux systems, such as how to open Azure support cases via CLI or web.
  • Ensure parity in screenshots and step-by-step guides for both GUI (portal) and CLI workflows.
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-08 00:53
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 before Azure CLI, using .NET code samples exclusively, and omitting Linux-specific shell or SDK examples. There is no mention of Linux tools or patterns, and all code samples and screenshots are oriented toward Windows-centric workflows (PowerShell, .NET, Azure Portal).
Recommendations
  • Provide Linux shell (bash) examples alongside PowerShell, especially for metric queries and log analysis.
  • Include code samples using cross-platform SDKs (e.g., Python, JavaScript) in addition to .NET.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide any necessary platform-specific notes.
  • Add screenshots or instructions for accessing logs and metrics using Linux tools or terminal environments.
  • Ensure that examples and instructions are not exclusively tied to Windows tools or the Azure Portal.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-server-endpoint-delete.md .../storage/file-sync/file-sync-server-endpoint-delete.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All operational steps reference Windows-specific tools such as Task Scheduler, Event Viewer, and PowerShell cmdlets/scripts. There are no examples or guidance for performing these actions on Linux servers, nor any mention of Linux equivalents or cross-platform support. The instructions and screenshots assume the user is running Windows Server, and there is no discussion of Azure File Sync agent support or procedures for Linux systems.
Recommendations
  • Clarify whether Azure File Sync agent is supported on Linux. If not, state this explicitly at the top of the documentation.
  • If Linux support exists, provide equivalent instructions for Linux environments, including how to initiate sync sessions, check sync status, and recall files using Linux tools or CLI commands.
  • Include Linux shell script examples alongside PowerShell examples where applicable.
  • Reference cross-platform Azure CLI commands if available, and provide guidance for non-Windows users.
  • Add a section comparing Windows and Linux procedures, or link to Linux-specific documentation if it exists.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/authorize-access-azure-active-directory.md ...orage/blobs/authorize-access-azure-active-directory.md
High Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently mentioning PowerShell before Azure CLI when discussing command-line access, and by referencing PowerShell as a primary tool for data access. There are no explicit Linux-specific examples or references to Linux-native tools, and the documentation does not provide parity in examples or instructions for Linux users. The focus on PowerShell and lack of Linux examples may make it less accessible for users on Linux platforms.
Recommendations
  • Ensure that Azure CLI examples are presented before or alongside PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Include explicit Linux usage instructions and examples, such as shell commands for authentication and data access.
  • Reference Linux-native tools (e.g., curl, azcopy) where appropriate, and provide sample commands for these tools.
  • Clarify that PowerShell is available on Linux, but also highlight alternatives that are more common in Linux environments.
  • Add a section or callouts for Linux users, describing any platform-specific considerations or best practices.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-cloud-tiering-overview.md .../storage/file-sync/file-sync-cloud-tiering-overview.md
High Priority View Details →
Scanned: 2025-07-19 13:51
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation is heavily oriented toward Windows environments. It references Windows Server features (such as NTFS, Event Viewer, and Windows Server data deduplication), uses Windows-specific terminology (e.g., reparse points, FILE_ATTRIBUTE_RECALL_ON_DATA_ACCESS), and provides operational details and troubleshooting steps only for Windows. There are no examples, instructions, or considerations for Linux or cross-platform scenarios, and the only command-line tool mentioned is a PowerShell cmdlet.
Recommendations
  • Clarify early in the documentation that Azure File Sync cloud tiering is currently only supported on Windows Server, if that is the case. If Linux support is planned or available, add corresponding sections.
  • If Linux support is available, provide equivalent examples, operational details, and troubleshooting steps for Linux (e.g., file attributes, file system support, event logging locations, and command-line tools).
  • Where Windows-specific features are discussed (NTFS, Event Viewer, PowerShell), note their platform specificity and, if possible, offer Linux alternatives or explicitly state that these features are not available on Linux.
  • Avoid using only PowerShell cmdlets in examples; if CLI or REST API alternatives exist, include them and show cross-platform usage.
  • In tables and screenshots, clarify if the UI or attributes shown are Windows-specific, and provide Linux equivalents if applicable.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-server-endpoint-create.md .../storage/file-sync/file-sync-server-endpoint-create.md
High Priority View Details →
Scanned: 2025-07-19 13:51
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows file paths (e.g., F:\sync1), Windows tools (RoboCopy), and PowerShell cmdlets (Invoke-StorageSyncFileRecall). There are no examples or instructions for Linux systems, nor is there mention of Linux support or equivalent commands. The documentation assumes the use of Windows servers and omits guidance for Linux-based environments.
Recommendations
  • Include explicit statements about platform support, clarifying whether Linux servers are supported as Azure File Sync endpoints.
  • If Linux is supported, provide equivalent Linux examples (e.g., Linux file paths, CLI commands, and tools) alongside Windows examples.
  • If PowerShell cmdlets are referenced, offer alternative commands for Linux environments (such as Azure CLI or shell scripts) where possible.
  • Avoid referencing Windows-specific tools (like RoboCopy) without mentioning Linux equivalents (such as rsync) or clarifying platform applicability.
  • Add a section or note addressing cross-platform considerations, including any limitations or differences in feature support between Windows and Linux.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-robocopy.md ...cles/storage/files/storage-files-migration-robocopy.md
High Priority View Details →
Scanned: 2025-07-17 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. It exclusively describes migration using RoboCopy, a Windows-only tool, and all instructions, examples, and troubleshooting are tailored for Windows systems. There are no Linux-based migration examples or equivalent tools mentioned, despite the initial claim that sources can include Linux servers. The mounting instructions, command syntax, and optimization tips are all Windows-specific, and there is no guidance for performing similar migrations from or on Linux systems.
Recommendations
  • Provide equivalent migration instructions for Linux environments, such as using rsync, smbclient, or other Linux-compatible SMB tools.
  • Include Linux command-line examples for mounting Azure file shares (e.g., using mount.cifs or smbclient).
  • Discuss Linux-based migration scenarios, including any limitations or differences compared to RoboCopy.
  • Mention cross-platform tools (such as AzCopy, if/when feature parity is sufficient) and provide guidance for both Windows and Linux users.
  • Structure the documentation so that Windows and Linux instructions are presented in parallel or clearly separated sections, rather than focusing solely on Windows.
  • Clarify in the introduction that the article is Windows-specific, or link to a separate Linux migration guide if available.
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: 2025-07-17 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific tools and patterns (such as Azure File Sync, which is only available for Windows servers) are highlighted, often with no Linux equivalent mentioned. PowerShell is frequently referenced, sometimes before or instead of cross-platform tools like Azure CLI. Windows Server and SMB (a protocol most closely associated with Windows) are discussed in detail, while Linux/NFS features are mentioned less frequently and often as secondary. There are also cases where examples or instructions are only provided for Windows or Windows tools, with Linux equivalents missing or less emphasized.
Recommendations
  • Wherever PowerShell is mentioned, ensure Azure CLI (which is cross-platform) is also referenced equally and examples are provided for both.
  • When introducing features or tools (such as Azure File Sync), clarify platform support and, if not available for Linux, suggest alternative solutions or explicitly state the limitation.
  • For every Windows/SMB example or feature, provide a Linux/NFS equivalent where possible, and ensure Linux/NFS features are not consistently presented after Windows/SMB ones.
  • In lists or instructions, avoid always mentioning Windows or Windows tools first; alternate or group by platform.
  • Expand documentation and guidance for Linux administrators, including more detailed examples and troubleshooting for Linux/NFS scenarios.
  • Where features are Windows-only, clearly label them as such and provide links to Linux-relevant documentation.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-overview.md ...cles/storage/files/storage-files-migration-overview.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation exhibits a clear Windows bias. Windows tools (RoboCopy, Azure File Sync, Storage Migration Service) are emphasized and described in detail, while Linux migration scenarios receive minimal attention and lack concrete examples or tool guidance. Windows terminology (NTFS, ACLs, DFS-N, etc.) is used throughout, and migration tables and tool recommendations are Windows-centric. Linux migration is only briefly mentioned, with no step-by-step guides or Linux-native tool recommendations.
Recommendations
  • Provide Linux-focused migration examples, including step-by-step guides using Linux-native tools (e.g., rsync, cifs-utils, smbclient) for copying data to Azure file shares.
  • Include Linux command-line examples alongside Windows/Powershell examples when demonstrating mounting, copying, or migrating data.
  • Expand the migration guides table to include more detailed Linux scenarios, such as migrating from Linux SMB servers or NFS to Azure Files, and clarify tool support for Linux environments.
  • Discuss Linux file permission and metadata mapping (e.g., POSIX ACLs vs. NTFS ACLs) and any limitations or considerations.
  • Balance the order of presentation so that Linux and Windows tools and scenarios are introduced with equal prominence.
  • Reference Linux-compatible third-party tools (e.g., rsync, rclone) where appropriate, and provide links to their documentation.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-robocopy.md ...cles/storage/files/storage-files-migration-robocopy.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. It exclusively recommends and demonstrates the use of RoboCopy, a Windows-only tool, for migrating to Azure Files. All examples, mounting instructions, and optimization tips are tailored to Windows Server and PowerShell. There is no mention of equivalent Linux tools or workflows, nor are there any Linux-specific examples or guidance, despite the initial checklist noting Linux servers as possible sources.
Recommendations
  • Include Linux migration options, such as using rsync, smbclient, or mount.cifs for SMB-based transfers to Azure Files.
  • Provide parallel Linux command-line examples for mounting Azure file shares and copying data.
  • Discuss the limitations and considerations for Linux-based SMB clients when migrating to Azure Files.
  • Reference or link to Linux-specific documentation for Azure Files migrations.
  • Clarify in the introduction that the guide is Windows-specific, or create a separate Linux migration guide for parity.
  • Mention cross-platform tools (e.g., AzCopy, where appropriate) and their usage from Linux environments, even if with caveats.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/immutable-version-level-worm-policies.md ...storage/blobs/immutable-version-level-worm-policies.md
High Priority View Details →
Scanned: 2025-07-15 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias by referencing PowerShell commands (e.g., Remove-AzRmStorageContainer) as the primary example for deleting containers, and by mentioning PowerShell before Azure CLI. There are no explicit Linux shell or Bash examples, and the documentation does not provide parity in command-line examples for Linux users. The focus on PowerShell and the absence of Linux-native command examples may disadvantage Linux administrators.
Recommendations
  • Provide equivalent Bash or Linux shell command examples alongside PowerShell commands, especially for common administrative tasks such as deleting containers.
  • When referencing command-line tools, mention Azure CLI before or alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux.
  • Include explicit notes or examples for Linux users where command syntax or behavior may differ.
  • Avoid assuming PowerShell as the default scripting environment; clarify that both PowerShell and Bash/Azure CLI are supported.
  • Where possible, provide REST API examples or links, as these are platform-agnostic.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/immutable-container-level-worm-policies.md ...orage/blobs/immutable-container-level-worm-policies.md
High Priority View Details →
Scanned: 2025-07-15 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell commands (Remove-AzRmStorageContainer, Remove-AzStorageContainer) as primary examples for control plane and data plane operations, and by mentioning these Windows-centric tools before the Azure CLI equivalents. There are no explicit Linux shell or cross-platform examples, and the focus on PowerShell may disadvantage Linux users.
Recommendations
  • Provide equivalent Linux shell (bash) and Azure CLI examples alongside or before PowerShell commands.
  • When referencing command-line tools, ensure Azure CLI (which is cross-platform) is given equal or greater prominence than PowerShell.
  • Include explicit notes or examples for Linux/macOS users, especially for common administrative tasks.
  • Avoid assuming the use of Windows tools or patterns; clarify that all operations can be performed from any OS using Azure CLI or REST API.
  • Consider adding a table or section summarizing command syntax for PowerShell, Azure CLI, and REST API to ensure parity.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/soft-delete-blob-enable.md ...main/articles/storage/blobs/soft-delete-blob-enable.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is featured prominently as a primary automation method, with detailed instructions and examples. There are several references to Windows-specific tools (e.g., Windows PowerShell as a console example), and PowerShell is mentioned before Azure CLI in most sections. While Azure CLI examples are provided (which are cross-platform), the documentation sometimes defaults to Windows-centric language and patterns, such as suggesting Windows PowerShell as the default local CLI environment, and does not explicitly mention or show Linux/macOS terminal usage or shell conventions.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell prompts for Bash (e.g., $) as well as PowerShell (e.g., PS>), or use neutral prompts.
  • When referencing command-line environments, mention Bash or other Linux/macOS shells alongside Windows PowerShell.
  • Balance the ordering of PowerShell and Azure CLI sections, or alternate their order to avoid always listing PowerShell first.
  • Where possible, provide Bash-specific notes or examples, especially for multi-line commands or environment variable usage.
  • Avoid language that assumes the user is on Windows (e.g., 'open a command console application such as Windows PowerShell'); instead, use neutral phrasing like 'open a terminal or command prompt.'
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/quickstart-blobs-c-plus-plus.md ...articles/storage/blobs/quickstart-blobs-c-plus-plus.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-specific tools and workflows (such as Visual Studio and .sln files), providing Windows command examples before Linux ones, and focusing on Windows-centric project setup. Linux alternatives are sometimes mentioned but are less detailed or appear after Windows instructions. There is little guidance for Linux-native development environments or editors, and the project creation flow is tightly coupled to Visual Studio on Windows.
Recommendations
  • Provide equal prominence to Linux development workflows, such as using CMake or Makefiles, and include instructions for setting up projects in popular Linux IDEs (e.g., CLion, Qt Creator, VS Code) or via command line.
  • When showing environment variable setup, present Linux and Windows instructions side-by-side or in tabs, rather than listing Windows first.
  • Offer code snippets and project setup instructions that are platform-agnostic or provide parallel instructions for both Windows and Linux.
  • Avoid assuming Visual Studio as the default IDE; mention cross-platform alternatives and provide guidance for both.
  • Include Linux-specific troubleshooting tips or notes where relevant, especially for dependency installation and environment configuration.
  • Ensure all screenshots and step-by-step guides have Linux equivalents or clarify when a step is Windows-only.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/simulate-primary-region-failure.md ...icles/storage/blobs/simulate-primary-region-failure.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides both Windows and Linux command-line examples for static route manipulation, but the Fiddler-based failure simulation method is Windows-specific and lacks any Linux or cross-platform alternative. Additionally, Fiddler is introduced as a primary method without mentioning its Windows-only nature or suggesting Linux equivalents. In some instructions, Windows is mentioned first, and the overall flow assumes familiarity with Windows tools.
Recommendations
  • For the Fiddler section, explicitly state that Fiddler is a Windows-only tool and provide equivalent instructions for Linux users, such as using mitmproxy or similar cross-platform tools.
  • When introducing tools or commands, present Linux and Windows options in parallel, rather than defaulting to Windows-first phrasing.
  • Add a section or callout for Linux/macOS users that describes how to simulate HTTP failures using open-source, cross-platform tools.
  • Where screenshots or UI steps are shown for Windows-only tools, provide comparable visuals or command-line steps for Linux alternatives.
  • Review the prerequisites and tool recommendations to ensure Linux users are not left without guidance for any step.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-query-acceleration-how-to.md ...e/blobs/data-lake-storage-query-acceleration-how-to.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides PowerShell examples for all code scenarios, but does not provide equivalent Linux shell (bash/CLI) examples. The setup instructions for .NET reference 'command prompt' (a Windows term) and do not mention cross-platform shells. The PowerShell examples use Windows-specific tools and patterns, and are always presented first in each code tab group, indicating a 'Windows-first' ordering. There are no bash, Azure CLI, or Linux-native scripting examples, and no mention of Linux-specific tools or environments.
Recommendations
  • Add equivalent Azure CLI (az storage blob query) or bash scripting examples alongside PowerShell for all scenarios.
  • In setup instructions, use cross-platform terminology such as 'terminal' instead of 'command prompt', and clarify that commands work on Windows, Linux, and macOS.
  • Alternate the order of code tabs or default to a more neutral SDK (such as Python or JavaScript) to avoid a Windows-first impression.
  • Explicitly mention that PowerShell examples can be run on PowerShell Core on Linux/macOS, or provide bash alternatives.
  • Review all references to Windows-specific tools and ensure Linux users are equally supported.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-account-upgrade.md ...ain/articles/storage/common/storage-account-upgrade.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias by presenting PowerShell as a primary upgrade method, listing it before Azure CLI, and referencing PowerShell-specific modules and installation instructions. While Azure CLI is included (which is cross-platform), there are no explicit Linux/bash examples, nor is there mention of Linux-specific considerations or parity in tooling. The documentation assumes familiarity with PowerShell and Windows-centric patterns.
Recommendations
  • Provide explicit bash/Linux shell examples alongside or before PowerShell examples, especially for Azure CLI commands.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, possibly linking to Linux-specific installation instructions.
  • Avoid listing PowerShell before Azure CLI unless there is a clear reason; consider alternating order or presenting CLI first for broader platform neutrality.
  • Mention that PowerShell Core is available cross-platform, if PowerShell examples are retained, and provide guidance for Linux/macOS users.
  • Add a section or note addressing Linux/macOS users, highlighting any differences or confirming parity in the upgrade process.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-choose-data-transfer-solution.md ...torage/common/storage-choose-data-transfer-solution.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias. Scripted/programmatic transfer tools list 'Azure PowerShell' before 'Azure CLI', and the 'Next steps' section links to a PowerShell quickstart before the Azure CLI equivalent. There are no explicit Linux or Bash/Shell examples or references, and the focus on PowerShell may suggest a Windows-centric approach. No Linux-specific tools or workflows are mentioned.
Recommendations
  • Ensure that Azure CLI and Bash/Shell examples are presented alongside or before PowerShell examples, especially in quickstarts and code snippets.
  • Explicitly mention Linux/macOS compatibility for tools like AzCopy and Azure CLI.
  • Include links to Linux/Bash quickstarts or tutorials where available.
  • Balance references to PowerShell and CLI in both the main text and 'Next steps' section.
  • Consider adding a table or section comparing tool usage across Windows, Linux, and macOS.
GitHub Create Pull Request
← Previous Page 30 of 67 Next →