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 551-575 of 1657 flagged pages
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-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 several forms of Windows bias. Windows terminology and tools (e.g., PowerShell, Windows Server, Windows 11) are mentioned first or exclusively in key sections, such as DNS configuration and SMB over QUIC. PowerShell cmdlets are used for DNS resolution examples, with only a brief mention of 'nslookup' as an alternative. The SMB over QUIC section is entirely Windows-centric, with no mention of Linux or cross-platform alternatives. There are references to configuration guides for both Windows and Linux VPN clients, but Windows is listed first. There is a lack of Linux-specific examples or parity in tooling and troubleshooting guidance throughout the page.
Recommendations
  • Provide Linux-specific examples and commands alongside Windows/PowerShell examples, such as showing 'dig' or 'nslookup' usage for DNS resolution.
  • Include parity in SMB and NFS troubleshooting and configuration guidance for Linux clients, not just Windows.
  • Mention Linux-compatible tools and utilities where Windows tools (e.g., PowerShell, Windows Server) are referenced.
  • Add explicit guidance for mounting Azure Files from Linux, including security and networking considerations.
  • Where features are Windows-only (e.g., SMB over QUIC), clarify the lack of Linux support and suggest alternatives or workarounds for Linux environments.
  • Ensure that references to configuration guides for both Windows and Linux are presented with equal prominence and detail.
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-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 demonstrates a moderate Windows bias. Windows-specific tools (Robocopy, File Explorer 'Previous Versions') are described in detail, with step-by-step instructions and screenshots. Windows workflows for restoring files from snapshots are presented before Linux equivalents. PowerShell is featured prominently alongside Azure CLI, but Linux-native tools and workflows (other than mounting SMB/NFS shares) are less detailed. There is a lack of parity in examples for copying/restoring files from SMB snapshots on Linux; only mounting is covered, while restore/copy operations are shown in depth for Windows. Linux users are not given equivalent step-by-step guidance for browsing, restoring, or copying files from SMB share snapshots.
Recommendations
  • Add detailed Linux examples for restoring/copying files from SMB share snapshots, including browsing snapshots and using standard Linux tools (e.g., cp, rsync) after mounting.
  • Provide parity in screenshots and step-by-step instructions for Linux workflows, similar to those given for Windows (e.g., using Nautilus or command line to access previous versions).
  • Mention Linux tools (e.g., smbclient, rsync) where Robocopy is referenced for Windows.
  • Ensure that instructions for mounting and restoring from snapshots on Linux are as comprehensive as those for Windows, including troubleshooting tips.
  • Consider presenting OS-specific workflows in parallel (side-by-side or in tabs), rather than listing Windows first.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/virtual-desktop-workloads.md ...in/articles/storage/files/virtual-desktop-workloads.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 exhibits a Windows bias by focusing exclusively on Windows-centric technologies (FSLogix, roaming profiles, folder redirection), referencing Windows file paths and conventions, and omitting Linux-specific guidance or examples. All usage scenarios, sizing guidance, and technical recommendations are tailored to Windows environments, with no mention of Linux VDI solutions, Linux SMB clients, or cross-platform considerations.
Recommendations
  • Add examples and guidance for Linux-based VDI environments, such as using Azure Files with Linux session hosts or Linux SMB clients.
  • Include information about mounting Azure Files SMB shares from Linux, including relevant commands (e.g., mount.cifs) and authentication considerations.
  • Discuss compatibility and performance differences for Linux clients, including any limitations or best practices for Linux VDI workloads.
  • Reference Linux equivalents to Windows tools and patterns (e.g., alternatives to FSLogix for Linux, or how Linux user profiles can be stored on Azure Files).
  • Ensure that tables and recommendations include both Windows and Linux scenarios, or explicitly state platform limitations.
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-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 consistently mentioning PowerShell before Azure CLI, grouping PowerShell and CLI together without distinguishing platform differences, and omitting explicit Linux/macOS usage examples. There are no references to Linux-specific tools, shell commands, or platform considerations, and the examples and instructions do not address cross-platform nuances, such as authentication flows or environment setup for Linux users.
Recommendations
  • Provide explicit Linux/macOS examples for authentication and queue access, using Bash and Azure CLI.
  • When referencing PowerShell and Azure CLI, clarify platform compatibility and usage differences (e.g., show both Windows PowerShell and Bash CLI commands side-by-side).
  • Include notes or sections on environment setup for Linux/macOS users, such as installing Azure CLI, configuring credentials, and troubleshooting common issues.
  • Avoid grouping PowerShell and Azure CLI together as equivalent; highlight that Azure CLI is cross-platform and PowerShell is primarily Windows-focused.
  • Add links to Linux/macOS documentation or tutorials for Azure Storage and Microsoft Entra ID integration.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/queues-auth-abac-examples.md ...n/articles/storage/queues/queues-auth-abac-examples.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page provides detailed examples for Azure Queue Storage role assignment conditions, but all command-line examples are exclusively in Azure PowerShell, a Windows-centric tool. There are no CLI/bash/Linux shell examples, nor is Azure CLI mentioned. The structure consistently presents PowerShell after portal/code editor, with no parity for Linux users or cross-platform command-line usage.
Recommendations
  • Add equivalent Azure CLI examples for all scenarios, using bash syntax and cross-platform commands.
  • Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide installation links.
  • Where PowerShell is used, clarify its availability on Linux/macOS, or prefer Azure CLI for broader compatibility.
  • Ensure that command-line examples are presented in parallel tabs (e.g., 'PowerShell', 'CLI/Bash') to avoid Windows-first perception.
  • Review all screenshots and instructions to ensure they do not assume a Windows environment (e.g., file paths, tool references).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-performance-checklist.md ...ticles/storage/queues/storage-performance-checklist.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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-centric tools (Network Monitor), omits Linux equivalents (such as tcpdump or netstat), and mentions PowerShell before Azure CLI when discussing client libraries and tools. The .NET configuration section is Windows/.NET-focused, with no comparable guidance for Linux or other platforms. There are no explicit Linux examples, and Windows tools/patterns are mentioned exclusively or first in relevant sections.
Recommendations
  • Include Linux equivalents for diagnostic tools (e.g., mention tcpdump, netstat, or iftop alongside Wireshark and Network Monitor).
  • When listing client libraries and tools, mention Azure CLI before or alongside PowerShell, and clarify cross-platform support.
  • Add configuration guidance for other languages and platforms (e.g., Java, Python, Node.js) with examples for Linux environments.
  • Provide examples or notes for Linux-specific performance tuning (e.g., adjusting TCP settings, disabling Nagle's algorithm on Linux).
  • Ensure that tool recommendations and troubleshooting steps are platform-neutral or include both Windows and Linux options.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/backup-archive-disaster-recovery/tiger-bridge-cdp-guide.md ...up-archive-disaster-recovery/tiger-bridge-cdp-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 page exhibits a strong Windows bias. All deployment and configuration instructions assume the use of Windows Server, with explicit requirements for a Windows file server and references to Windows-native tools such as Volume Shadow Copy Service, Windows Explorer, and DFSR. There are no examples, instructions, or mentions of Linux or cross-platform alternatives. All screenshots and shell extension usage are shown in the context of Windows Explorer, and no Linux equivalents (e.g., CLI, desktop environments, or file managers) are discussed.
Recommendations
  • Add explicit support statements for Linux servers if Tiger Bridge supports Linux, or clarify platform limitations.
  • Provide Linux-specific deployment and configuration instructions, including installation steps, file system integration, and recovery workflows.
  • Include examples using Linux tools (e.g., CLI commands, file managers like Nautilus or Dolphin) for backup, restore, and archive operations.
  • Mention Linux equivalents to Windows features (e.g., Linux snapshot tools, file versioning, undelete utilities) where applicable.
  • If Tiger Bridge is Windows-only, clearly state this limitation early in the documentation to set user expectations.
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-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 by exclusively referencing the Azure portal (a web GUI commonly used by Windows admins), omitting any CLI or automation examples (such as Azure CLI, PowerShell, or Bash), and failing to mention Linux-native tools or workflows. All step-by-step instructions and screenshots are based on the Azure portal, with no guidance for Linux users who may prefer command-line or scripting approaches. Additionally, network monitoring tool recommendations are primarily Windows-centric, with no mention of Linux alternatives.
Recommendations
  • Add equivalent instructions for configuring Azure Blob Storage using Azure CLI and/or REST API, including command-line examples suitable for Linux environments.
  • Include sample scripts for DobiSync integration with Azure Storage using Bash or Python, demonstrating automation-friendly workflows.
  • Mention Linux-native network monitoring tools (e.g., iftop, nload, vnstat, Netdata) alongside Windows tools for bandwidth assessment.
  • Provide guidance for accessing Azure support via CLI (az support) or other non-portal methods.
  • Ensure screenshots and instructions are not exclusively tied to the Azure portal; offer parity for users who do not use GUI-based workflows.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/data-management/atempo-quick-start-guide.md ...d-partners/data-management/atempo-quick-start-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 page exhibits Windows bias by providing only Windows file server (SMB/CIFS) migration examples, referencing Windows Data Movers, and omitting Linux/NFS migration scenarios. The tools and configuration steps are described exclusively for Windows environments, with no mention of Linux equivalents or guidance for Linux administrators.
Recommendations
  • Include parallel examples for migrating from Linux file servers (e.g., NFS shares) to Azure, detailing the steps and configuration differences.
  • Explicitly mention supported Linux platforms and provide guidance for deploying Miria Data Movers on Linux systems.
  • Add instructions for configuring Miria source storage for NFS shares, including screenshots and step-by-step guidance.
  • List Linux-compatible network monitoring tools (e.g., iftop, nload, vnStat) alongside Windows tools in the bandwidth assessment section.
  • Ensure that references to OS-specific procedures are balanced, and avoid presenting Windows steps before Linux unless justified by usage statistics.
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-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 by exclusively referencing Azure portal (a web GUI typically used on Windows), omitting any Linux-specific CLI or shell examples for storage account or file share setup. All network monitoring tool examples are Windows-centric (SolarWinds, Paessler PRTG, Cisco Network Assistant, WhatsUp Gold) with no mention of Linux-native tools (e.g., iftop, nload, vnstat, iperf). There is no guidance for Linux users on how to perform equivalent operations (e.g., using Azure CLI, mounting Azure Files via SMB on Linux, or using Linux network utilities).
Recommendations
  • Add Linux-specific instructions for creating and managing Azure storage accounts and file shares using Azure CLI and shell commands.
  • Include examples of mounting Azure Files shares on Linux systems (e.g., using mount.cifs or SMB client).
  • List Linux-native network monitoring tools (iftop, nload, vnstat, iperf) alongside Windows tools.
  • Provide parity in screenshots and step-by-step guides for both GUI (portal) and CLI workflows.
  • Explicitly mention cross-platform compatibility and provide troubleshooting tips for Linux environments.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/data-management/storagex-quick-start-guide.md ...partners/data-management/storagex-quick-start-guide.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 page demonstrates a Windows bias by prioritizing Windows/Active Directory concepts, tools, and examples throughout. Installation and deployment instructions are Windows-centric (e.g., references to C:\ProgramData, 'Run as administrator', desktop shortcuts), and the use of Windows-specific utilities like portqryui is highlighted. There is little to no mention of Linux-specific deployment, tools, or examples, and NFS/Linux scenarios are only briefly referenced without operational guidance or parity in walkthroughs.
Recommendations
  • Add explicit Linux deployment instructions, including installation paths, service management, and script execution on Linux hosts.
  • Provide Linux-specific examples for NFS migrations, including how to configure service accounts, permissions, and export rules on Linux NAS devices.
  • Include Linux-native tools for network and port checking (e.g., netstat, ss, nmap, iperf) alongside Windows tools.
  • Balance screenshots and CLI walkthroughs to show both Windows and Linux environments.
  • Clarify which steps are OS-agnostic and which require platform-specific actions, and provide guidance for both.
  • Mention Linux authentication and identity management alternatives to Active Directory (e.g., LDAP, Kerberos) where relevant.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/primary-secondary-storage/isv-file-services.md ...artners/primary-secondary-storage/isv-file-services.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 moderate Windows bias. Several ISV solutions (Tiger Technology, XenData) are described as operating specifically on Windows Server or using NTFS, with features such as 'Windows Shell integration' and 'Disaster Recovery for Windows servers' highlighted. The 'Operating Environment' and 'Automatic failover' features repeatedly reference Windows Server and Windows clustering, with no mention of Linux equivalents or parity. There are no explicit Linux management or deployment examples, and Linux-specific features or environments are not discussed, even for solutions that likely support them. Windows terminology and tools are mentioned before or instead of Linux alternatives.
Recommendations
  • For each ISV solution, clarify if Linux environments are supported and provide equivalent details for Linux deployment, management, and failover features.
  • Where Windows-specific features (e.g., NTFS tiering, Windows Shell integration, Windows clustering) are mentioned, add Linux equivalents (e.g., ext4/XFS tiering, Linux desktop integration, Linux HA clustering) if available.
  • Include example use cases and management options for Linux-based deployments, especially for solutions that are cross-platform.
  • In tables and feature lists, ensure Linux operating environments and features are listed alongside Windows, not omitted.
  • Avoid language that implies Windows is the default or only supported platform unless that is a technical limitation; otherwise, highlight cross-platform capabilities.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/storage-explorer/vs-azure-tools-storage-manage-with-storage-explorer.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/storage-explorer/vs-azure-tools-storage-manage-with-storage-explorer.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 demonstrates a mild Windows bias. Windows is listed first in prerequisites and emulator support, and the legacy Azure Storage Emulator is mentioned as Windows-only before Azurite (which is cross-platform). There are no Linux-specific troubleshooting or usage examples beyond installation, and Windows tools (.NET runtime, Storage Emulator) are referenced without Linux equivalents or parity in explanation.
Recommendations
  • Rotate the order of operating systems in prerequisites or present them in alphabetical order to avoid implicit prioritization.
  • Provide Linux-specific troubleshooting steps and usage examples, such as common issues with snap installations or manual dependency resolution.
  • Expand on Azurite as the recommended emulator for all platforms, and clarify that the legacy Azure Storage Emulator is deprecated and Windows-only.
  • Mention .NET runtime requirements for Linux and macOS explicitly, including installation instructions or links.
  • Ensure parity in screenshots and UI instructions by including examples from Linux and macOS environments, not just Windows.
  • Add notes or sections for Linux-specific password manager integration and common desktop environment issues.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/primary-secondary-storage/nasuni-deployment-guide.md ...s/primary-secondary-storage/nasuni-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 consistently uses Windows terminology, screenshots, and patterns (e.g., 'Windows Azure Platform', Windows-style UI navigation, and references to Windows file servers and SMB/CIFS protocols) without providing Linux equivalents or examples. There are no CLI or Linux-based instructions, and all visuals and steps assume a Windows/Azure Portal GUI workflow. Linux tools, patterns, or command-line alternatives are absent.
Recommendations
  • Add equivalent instructions for Linux users, such as using Azure CLI or PowerShell Core on Linux to create and manage storage accounts.
  • Include screenshots or examples from Linux environments (e.g., Azure CLI in a Bash shell) alongside Windows/Azure Portal GUI steps.
  • Mention and provide guidance for NFS and Linux file server migration scenarios, not just Windows/SMB workloads.
  • Clarify that Nasuni Edge Appliances can be deployed on Linux-based hypervisors and provide relevant configuration steps.
  • Avoid using 'Windows Azure Platform' as the sole cloud provider label; use 'Microsoft Azure' or clarify cross-platform support.
  • Provide parity in credential management instructions for Linux environments (e.g., using environment variables or config files).
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific tools (WireShark, NetMon) for network diagnostics, mentions PowerShell before Azure CLI when discussing supported tools, and links to a blog hosted on 'windowsazurestorage'. The .NET configuration section is Windows-centric, with no equivalent Linux or cross-platform examples for connection/thread management. There are no explicit Linux-specific examples, tools, or troubleshooting guidance, and Windows/PowerShell patterns are mentioned before or instead of Linux/CLI alternatives.
Recommendations
  • Add Linux-specific diagnostic tool suggestions (e.g., tcpdump, iftop, nload) alongside WireShark and NetMon.
  • Mention Azure CLI before or alongside PowerShell when listing supported tools, and provide example commands for both.
  • Include cross-platform or Linux-specific configuration guidance for connection/thread management, such as for Python, Java, or Node.js clients.
  • Avoid using Windows-centric blog links or terminology (e.g., 'windowsazurestorage') in favor of neutral or cross-platform sources.
  • Explicitly state that the guidance applies to both Windows and Linux environments, and provide parity in examples and troubleshooting steps.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-specific tools (AzCopy, Azure Storage Explorer, WASB driver) and PowerShell as primary means for certain operations (e.g., restoring soft-deleted blobs), often before or without mentioning Linux alternatives. The WASB driver is discussed without noting Linux equivalents, and PowerShell is listed before Azure CLI in some contexts. There are no explicit Linux shell or command examples, and Windows-centric terminology is used (e.g., 'Windows Azure Storage Blob').
Recommendations
  • Provide Linux shell (bash) examples alongside PowerShell for all command-line operations.
  • Mention Linux-compatible tools (e.g., Azure CLI, SDKs) before or alongside Windows tools.
  • Clarify cross-platform compatibility for AzCopy and Azure Storage Explorer, including installation and usage on Linux/macOS.
  • Reference Hadoop ABFS driver usage in both Windows and Linux environments.
  • Avoid Windows-first terminology (e.g., WASB) or clarify its relevance to both platforms.
  • Include explicit guidance for Linux users in sections discussing PowerShell or Windows tools.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/lifecycle-management-policy-configure.md ...storage/blobs/lifecycle-management-policy-configure.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and command breakdowns, while the Azure CLI section is much shorter and lacks equivalent step-by-step guidance. PowerShell is presented before Azure CLI in both main sections, and Windows-centric tools (PowerShell) are described in greater detail. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native tooling or scripting approaches.
Recommendations
  • Provide equally detailed Azure CLI examples, including step-by-step breakdowns and explanations for each command, similar to the PowerShell section.
  • Include Bash or shell script examples for Linux users, demonstrating how to use Azure CLI in typical Linux environments.
  • Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI first to avoid implicit prioritization of Windows tools.
  • Explicitly mention cross-platform compatibility and note that Azure CLI works natively on Linux, macOS, and Windows.
  • Add troubleshooting or usage notes relevant to Linux environments, such as file path conventions or authentication differences.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/secure-file-transfer-protocol-support.md ...storage/blobs/secure-file-transfer-protocol-support.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 subtle Windows bias. SFTP command examples are presented in PowerShell syntax, and the only explicit command-line example references OpenSSH on Windows. There are no Linux-specific SFTP command examples, nor is there mention of Linux-native SSH/SFTP usage patterns. The documentation does not provide parity for Linux users in terms of examples or tool references, even though SFTP is commonly used on Linux systems.
Recommendations
  • Add Linux-specific SFTP command examples, such as using the sftp command in a bash shell.
  • Present both Windows (PowerShell) and Linux (bash) examples side-by-side when demonstrating SFTP connections.
  • Reference Linux-native tools and documentation (e.g., OpenSSH on Linux, usage of ~/.ssh/ directories, key generation with ssh-keygen).
  • Avoid using PowerShell syntax exclusively for generic SFTP commands; use platform-neutral syntax or provide both.
  • Explicitly mention that SFTP is supported on both Windows and Linux, and provide guidance for both platforms.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-dotnet.md ...icles/storage/blobs/storage-quickstart-blobs-dotnet.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Visual Studio Heavy Powershell Mention Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Visual Studio (a Windows-centric IDE) in instructions and screenshots, listing Windows consoles (cmd, PowerShell) before Bash, and referencing Windows-specific tools and workflows. While .NET CLI instructions are cross-platform, Visual Studio is presented first and in greater detail, and there are no explicit Linux-specific examples, screenshots, or troubleshooting steps. PowerShell is mentioned as a console option, but no Linux shell commands or package manager instructions (e.g., apt, yum) are provided.
Recommendations
  • Provide Linux-specific instructions and screenshots for common workflows (e.g., using VS Code, JetBrains Rider, or CLI-only development).
  • List Bash and Linux consoles before or alongside Windows consoles (cmd, PowerShell) when giving CLI instructions.
  • Include troubleshooting steps for Linux environments (e.g., file permissions, directory creation, .NET SDK installation via apt/yum).
  • Mention cross-platform editors (VS Code, Rider) more prominently, and provide equivalent steps for opening projects.
  • Add notes about package installation and environment setup for Linux (e.g., installing .NET SDK on Ubuntu, Fedora).
  • Ensure all CLI commands are tested and confirmed to work on Linux and macOS, and clarify any platform-specific differences.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-install-azurite.md ...ain/articles/storage/common/storage-install-azurite.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 exhibits a Windows bias by prioritizing Windows-centric tools (Visual Studio, Visual Studio Code), providing file paths and examples using Windows conventions (e.g., c:\azurite), and omitting explicit Linux/macOS installation and usage instructions. The location of executables and workspace directories is described only for Windows, and there are no Linux shell or macOS Terminal examples. Docker volume mounts and npm usage also use Windows paths exclusively.
Recommendations
  • Add Linux/macOS-specific instructions and examples for installing and running Azurite, including shell commands and typical file paths (e.g., ~/azurite or /home/user/azurite).
  • Include Visual Studio Code extension installation and usage steps for Linux/macOS environments.
  • Provide Docker run examples using Linux-style volume mounts (e.g., -v ~/azurite:/data) and clarify cross-platform differences.
  • Document the location of Azurite executables for non-Windows environments, if applicable.
  • Ensure all command-line examples use both Windows and Linux/macOS path formats, or use environment-agnostic variables.
  • Mention any platform-specific caveats or requirements (e.g., permissions, port usage) for Linux/macOS users.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-private-endpoints.md ...n/articles/storage/common/storage-private-endpoints.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 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a primary method for creating private endpoints, mentioning Azure PowerShell before Azure CLI, and referencing Windows-centric tools (AzCopy, Storage Explorer) in the context of copying blobs. There is no explicit mention of Linux-specific tools, nor are Linux shell examples provided. The documentation assumes familiarity with Windows tooling and patterns, and does not offer parity for Linux users.
Recommendations
  • Provide Linux shell (bash) examples alongside PowerShell for all command-line instructions.
  • Mention and demonstrate usage of Linux-native tools (e.g., curl, wget, or SDKs in Python) for interacting with Azure Storage.
  • Ensure Azure CLI examples are presented before or alongside PowerShell, as CLI is cross-platform.
  • Reference cross-platform tools and clarify their availability on Linux (e.g., AzCopy, Storage Explorer).
  • Explicitly state that all procedures can be performed from Linux environments and provide guidance for Linux users where necessary.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-authorize-service-principal.md ...mmon/storage-use-azcopy-authorize-service-principal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides both Linux and Windows examples for environment variable configuration, but consistently uses PowerShell syntax for Windows and Bash for Linux. However, in sections outside of the explicit Linux/Windows tabs, PowerShell is used for interactive examples (e.g., prompting for secrets), and Windows-specific tooling (such as Export-PfxCertificate) is referenced without Linux equivalents. The Azure PowerShell workflow is described in detail, while Linux-native alternatives (such as Bash read prompts or OpenSSL for certificate export) are not mentioned. Windows-specific tools and patterns (PowerShell, certificate store, Export-PfxCertificate) are referenced before or instead of Linux alternatives, indicating a Windows bias.
Recommendations
  • Provide Linux/Bash equivalents for all interactive examples, such as using 'read -s' for secret prompts.
  • Reference Linux-native certificate management tools (e.g., OpenSSL) alongside Windows tools like Export-PfxCertificate.
  • Ensure parity in instructions for both platforms, including guidance for Linux keyring and secret storage.
  • When mentioning Windows-specific tools or flows, immediately follow with Linux alternatives.
  • Add explicit Bash examples for setting environment variables interactively, not just statically.
  • Clarify any platform-specific limitations (e.g., secret store availability) and provide workarounds for Linux.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-google-cloud.md ...cles/storage/common/storage-use-azcopy-google-cloud.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 Windows Shell Special Handling
Summary
The documentation demonstrates mild Windows bias by mentioning Windows-specific shell behaviors and commands before their Linux/macOS equivalents, and by providing special handling instructions for Windows Command Shell (cmd.exe). The environment variable setup table lists Windows first, and guidance on quoting in AzCopy commands prioritizes Windows shell differences. However, Linux and macOS are also covered, and most command examples are platform-neutral.
Recommendations
  • Present environment variable setup instructions in alphabetical order by OS (Linux, macOS, Windows) or group Unix-like systems together for parity.
  • When discussing shell-specific quoting, mention Linux/macOS first or provide equal prominence to all platforms.
  • Add explicit PowerShell examples if Windows is mentioned, and provide equivalent Bash examples for Linux/macOS.
  • Include troubleshooting or tips sections for both Windows and Linux/macOS users, not just Windows shell peculiarities.
  • Ensure that any references to tools or patterns are balanced between Windows and Linux/macOS, and avoid assuming Windows as the default platform.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-minimum-version.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-minimum-version.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation exhibits Windows bias in several ways. It references the Windows implementation of SSL as a security advantage, mentions PowerShell as a primary automation tool, and provides detailed PowerShell examples before Azure CLI examples. There is no mention of Linux-specific tools or patterns (e.g., Bash scripting, OpenSSL usage), and the CLI examples are generic, not tailored to Linux environments. The documentation does not provide parity for Linux users in terms of troubleshooting, automation, or tool recommendations.
Recommendations
  • Add explicit Linux/Bash examples alongside PowerShell, especially for scripting and automation tasks.
  • Reference OpenSSL and Linux TLS stack considerations where relevant, especially in security notes.
  • Clarify that Azure CLI commands work cross-platform and provide Linux-specific installation and usage notes.
  • Avoid statements that imply Windows security advantages without acknowledging Linux/OpenSSL contexts.
  • Include troubleshooting steps and examples for Linux clients (e.g., how to test TLS versions with curl or OpenSSL).
  • Balance the order of examples so that PowerShell and CLI/Bash are presented equally, or alternate which comes first.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-small-dataset-low-moderate-network.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-small-dataset-low-moderate-network.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page lists Azure PowerShell as a recommended scripting/programmatic tool alongside AzCopy and Azure CLI, but does not mention Linux-native equivalents or scripting languages (e.g., Bash, shell scripting). PowerShell is a Windows-centric tool, and its mention before Azure CLI (which is more cross-platform) may suggest a Windows-first bias. There are no Linux-specific examples or references to Linux shell scripting, and the scripting section is weighted toward Windows tools.
Recommendations
  • Provide Linux shell scripting examples (e.g., Bash) for data transfer operations.
  • Explicitly mention that Azure CLI and AzCopy are fully supported on Linux and provide sample Linux commands.
  • Balance the order of tool presentation by listing cross-platform tools (AzCopy, Azure CLI) before Windows-centric tools (PowerShell).
  • Include references to Linux automation patterns (e.g., cron jobs, shell scripts) for data transfer.
  • Clarify platform support in the scripting section, emphasizing parity between Windows and Linux.
GitHub Create Pull Request
← Previous Page 23 of 67 Next →