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 1101-1125 of 1657 flagged pages
Storage Change how a storage account is replicated ...b/main/articles/storage/common/redundancy-migration.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently and often before Azure CLI, with detailed scripts and explanations. PowerShell examples are more extensive, including multi-account conversion and monitoring scripts, while Azure CLI equivalents are present but less detailed. The use of CSV file paths in examples defaults to Windows-style backslashes. The Azure portal (a cross-platform web UI) is always listed first, but command-line instructions consistently present PowerShell before Azure CLI, which is more native to Linux/macOS. No Linux/macOS-specific tools or shell scripts (e.g., Bash) are provided, and there is no mention of platform-specific considerations for CLI usage.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples so that CLI is sometimes presented first, especially in sections relevant to Linux/macOS users.
  • Provide Bash script examples for multi-account operations, using Linux-style paths and idioms.
  • Clarify that Azure CLI is fully supported on Linux/macOS and provide links or notes for installation on those platforms.
  • Use neutral file path examples (e.g., /path/to/input.csv) or show both Windows and Linux path formats.
  • Explicitly mention cross-platform compatibility for all tools and avoid implying PowerShell is the default or preferred automation method.
  • Consider adding a short section or note for Linux/macOS users, highlighting any platform-specific caveats or best practices.
GitHub Create Pull Request
Storage Prevent authorization with Shared Key ...les/storage/common/shared-key-authorization-prevent.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools (Azure portal, PowerShell) are described and illustrated first, with PowerShell examples provided before Azure CLI. There is a lack of explicit Linux/macOS guidance, such as shell-specific notes, and no mention of Linux desktop tools or alternative shells. The Azure CLI example is present, but not prioritized, and instructions for installing CLI or PowerShell do not clarify platform differences. Screenshots and step-by-step instructions focus exclusively on the Azure portal (Windows-style UI) and PowerShell, with no Linux/macOS screenshots or terminal examples.
Recommendations
  • Present Azure CLI examples before PowerShell, or side-by-side, to reflect cross-platform parity.
  • Include explicit notes or sections for Linux/macOS users, such as shell compatibility, installation steps, and troubleshooting tips.
  • Add screenshots or terminal output examples from Linux/macOS environments.
  • Mention Linux desktop tools (if any) or clarify that Storage Explorer and AzCopy are cross-platform.
  • Clarify that Azure CLI and PowerShell are available on Linux/macOS, with links to platform-specific installation guides.
GitHub Create Pull Request
Storage Configure an expiration policy for shared access signatures (SAS) .../main/articles/storage/common/sas-expiration-policy.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides configuration instructions for SAS expiration policy using the Azure portal, PowerShell, and Azure CLI. PowerShell examples are given in detail and presented before Azure CLI, which may indicate a Windows-first approach. The use of PowerShell as a primary scripting example and the absence of Linux/macOS-specific shell examples (such as Bash) or explicit mention of cross-platform compatibility for CLI commands further reinforce a Windows bias. Additionally, screenshots and step-by-step instructions for the Azure portal may implicitly favor Windows users, though the portal itself is web-based.
Recommendations
  • Add Bash shell examples for Azure CLI commands to demonstrate usage on Linux/macOS.
  • Explicitly state that Azure CLI commands work on Linux/macOS and provide installation links or notes for those platforms.
  • Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform.
  • If PowerShell is shown, clarify that PowerShell Core is available on Linux/macOS, or provide equivalent Bash commands.
  • Include troubleshooting or environment notes for Linux/macOS users, such as file path conventions or authentication differences.
GitHub Create Pull Request
Storage Azure Storage Analytics logging ...n/articles/storage/common/storage-analytics-logging.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias. The only command-line example provided is in PowerShell, with no equivalent shown for Azure CLI, Bash, or Linux/macOS shells. References to tools and user agents in log samples are predominantly Windows-based (e.g., 'win32', 'Windows_NT'), and Windows tools (PowerShell, AzCopy) are mentioned before cross-platform alternatives. There is no explicit Linux/macOS example or guidance, which may create friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI and Bash examples alongside PowerShell snippets for managing and filtering logs.
  • Explicitly mention that Azure CLI and REST API can be used from Linux/macOS, and provide sample commands.
  • Include log entry examples that reference Linux/macOS user agents or tools (e.g., azcopy on Linux, Azure CLI).
  • Reorder or balance tool mentions so that cross-platform options are listed before or alongside Windows-specific tools.
  • Clarify that all features are available cross-platform and provide links to relevant Linux/macOS documentation.
GitHub Create Pull Request
Storage Azure storage disaster recovery planning and failover ...s/storage/common/storage-disaster-recovery-guidance.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page references Windows-centric tools such as Azure PowerShell and AzCopy for disaster recovery and data copying, but does not provide Linux/macOS equivalents or examples. The mention of Azure PowerShell is prominent, and there are no CLI, Bash, or Linux-native instructions or examples, which may create friction for users on non-Windows platforms.
Recommendations
  • Include Azure CLI examples for all operations currently shown with Azure PowerShell.
  • Explicitly mention that AzCopy is cross-platform and provide usage examples for Linux/macOS.
  • Add Bash or shell script examples for common tasks, such as copying data or initiating failover.
  • Reference platform-agnostic REST API usage for management operations.
  • Clarify tool availability and installation instructions for Linux/macOS users.
GitHub Create Pull Request
Storage Network Connections in Azure Storage Explorer ...in/articles/storage/common/storage-explorer-network.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation describes proxy configuration in Azure Storage Explorer in a cross-platform manner but exhibits subtle Windows bias. It refers to 'system proxy' settings without clarifying differences between Windows, Linux, and macOS, and omits platform-specific instructions or examples for Linux/macOS users. The authentication methods listed (NTLM, Negotiate) are Windows-centric, and there are no explicit Linux/macOS proxy configuration examples or references to common tools (e.g., GNOME/KDE proxy settings, environment variables in bash/zsh, etc.).
Recommendations
  • Add explicit instructions or examples for configuring system proxy settings on Linux and macOS (e.g., GNOME/KDE, network manager, macOS System Preferences).
  • Clarify which authentication methods are supported on non-Windows platforms and note any limitations (e.g., NTLM/Negoitate may not work on Linux/macOS).
  • Include screenshots or step-by-step guides for proxy configuration on Linux/macOS.
  • Mention common Linux/macOS proxy environment variable usage patterns (e.g., ~/.bashrc, ~/.profile).
  • Note any differences in Chromium networking stack behavior across platforms.
GitHub Create Pull Request
Storage Install and run the Azurite emulator for Azure Storage ...ain/articles/storage/common/storage-install-azurite.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Visual Studio and Visual Studio Code are emphasized as primary environments, with detailed instructions and screenshots. File paths and command examples consistently use Windows-style paths (e.g., c:\azurite), and instructions for running Azurite from Visual Studio focus exclusively on Windows, including executable locations. There are no explicit Linux/macOS examples for file paths, workspace setup, or running Azurite from the command line, and no mention of Linux-specific considerations (such as permissions or typical directory conventions).
Recommendations
  • Provide Linux/macOS equivalents for all file path examples (e.g., /home/user/azurite or ~/azurite) alongside Windows paths.
  • Include instructions for running Azurite from the command line on Linux/macOS, including installation locations and permissions.
  • Add a table or section detailing where the Azurite executable is located for Visual Studio Code and npm installations on Linux/macOS.
  • Show Docker volume mount examples using Linux paths (e.g., -v /home/user/azurite:/data).
  • Clarify that Azurite works cross-platform and note any OS-specific differences or caveats.
  • Ensure screenshots and UI instructions are not exclusively Windows-centric.
GitHub Create Pull Request
Storage Initiate a storage account failover ...es/storage/common/storage-initiate-account-failover.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured heavily with detailed installation and usage instructions, including troubleshooting for PowerShell 5.1 (Windows-only). The CLI section is present, but PowerShell instructions are more extensive and appear before CLI. There is no mention of Linux/macOS-specific shell environments, nor are there examples for Bash or other native Linux tools. The portal instructions are platform-agnostic, but command-line guidance is skewed toward Windows/PowerShell users.
Recommendations
  • Add explicit Bash examples for Linux/macOS users, especially for Azure CLI usage.
  • Clarify that Azure CLI commands work cross-platform and provide guidance for Linux/macOS installation and troubleshooting.
  • Reduce PowerShell-specific troubleshooting steps or provide equivalent troubleshooting for Linux/macOS environments (e.g., dealing with Python/CLI extensions).
  • Ensure CLI instructions are as detailed as PowerShell, including advanced usage and troubleshooting.
  • Consider listing Azure CLI instructions before PowerShell, or present both side-by-side.
GitHub Create Pull Request
Storage Azure Storage migration tools selection guide ...ain/articles/storage/common/storage-migration-tools.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias, especially in the Azure File Sync section, which is exclusively for Windows file servers and Windows protocols. Windows tools and protocols (SMB, NTFS, Windows Server) are mentioned first and in detail, while Linux/NFS scenarios are referenced but not explained with equivalent depth or examples. Scripted transfer tools mention Azure PowerShell before Azure CLI, and graphical tools are described generically without platform parity details. There are no explicit Linux/macOS command-line examples or guidance for Linux-specific migration scenarios.
Recommendations
  • Add explicit Linux/NFS migration examples and workflows, especially for Azure File Sync alternatives.
  • Provide parity in command-line examples for both Windows (PowerShell, Robocopy) and Linux/macOS (Bash, Rsync, DistCP).
  • Clarify which tools are cross-platform and provide platform-specific installation and usage notes.
  • Include Linux/macOS-specific troubleshooting and best practices for migration.
  • List Azure CLI before or alongside PowerShell to avoid Windows-first impression.
GitHub Create Pull Request
Storage Create a resource instance network rule for Azure Storage .../common/storage-network-security-resource-instances.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed PowerShell examples before Azure CLI, with more extensive coverage and explanation for PowerShell. This prioritizes Windows tooling and patterns, which may create friction for Linux/macOS users who typically use Azure CLI or other cross-platform tools.
Recommendations
  • Ensure Azure CLI examples are as detailed and comprehensive as PowerShell examples, including multi-resource instance scenarios and all available operations.
  • Consider presenting Azure CLI examples before PowerShell, or at least in parallel, to avoid implicit prioritization of Windows tools.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add Bash scripting examples for batch operations if relevant.
  • Clarify any differences in capabilities or syntax between PowerShell and Azure CLI.
GitHub Create Pull Request
Storage Use private endpoints ...n/articles/storage/common/storage-private-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page references both Azure PowerShell and Azure CLI for creating private endpoints, but lists PowerShell (a Windows-centric tool) alongside CLI without clarifying cross-platform parity or showing explicit Linux/macOS command-line examples. There are no Bash or Linux-specific instructions, and the order of presentation puts PowerShell before CLI, subtly prioritizing Windows tooling. No Linux/macOS screenshots, shell commands, or OS-specific guidance are provided.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and provide example commands for Linux/macOS environments (e.g., Bash).
  • Include screenshots or terminal output from Linux/macOS environments where relevant.
  • Present Azure CLI instructions before PowerShell, or in parallel, to avoid implicit Windows-first ordering.
  • Mention that PowerShell Core is available on Linux/macOS, if relevant, and clarify any differences.
  • Add troubleshooting or configuration notes for Linux/macOS users, especially around DNS and networking.
GitHub Create Pull Request
Storage AzCopy v10 configuration setting (Azure Storage) ...ge/common/storage-ref-azcopy-configuration-settings.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific behaviors and instructions are often mentioned first or exclusively, especially in proxy configuration and environment variable handling. PowerShell and CMD examples are provided in detail, while Linux/macOS instructions are more concise and sometimes omitted in advanced scenarios. Certain environment variables reference Windows-specific features (e.g., Event Logger, proxy auto-detection), and some optimizations are described as 'not needed or recommended on Windows' but beneficial on Linux, without equivalent detail for Linux/macOS users.
Recommendations
  • Present Linux/macOS examples before or alongside Windows examples, especially in command tables.
  • Expand Linux/macOS instructions for advanced scenarios (e.g., proxy bypass) rather than only stating 'leave unset'.
  • Clarify platform-specific behaviors for all OSes, not just Windows (e.g., proxy auto-detection, logging destinations).
  • Provide parity in troubleshooting and optimization advice for Linux/macOS users.
  • Avoid describing Windows as the default or primary platform; use neutral language and structure.
GitHub Create Pull Request
Storage Azure data transfer options for large datasets, moderate to high network bandwidth ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-large-dataset-moderate-high-network.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
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 moderate Windows bias. Windows-centric tools and patterns (e.g., Robocopy, Azure PowerShell) are mentioned, with no explicit Linux/macOS equivalents or examples. Windows tools are referenced first or exclusively, and there is a lack of guidance for Linux users regarding offline transfer tooling and command-line usage. The absence of Linux/macOS-specific instructions or alternatives may create friction for non-Windows users.
Recommendations
  • Include Linux/macOS equivalents for all mentioned Windows tools (e.g., suggest rsync or cp instead of Robocopy for Data Box transfers).
  • Provide explicit Linux/macOS command-line examples for AzCopy and Azure CLI usage.
  • Mention cross-platform compatibility for each tool, clarifying which are available on Linux/macOS.
  • Add notes or links to documentation for Linux/macOS setup and usage for offline and online transfer scenarios.
  • Avoid listing Windows tools (e.g., PowerShell, Robocopy) before cross-platform or Linux-native options.
GitHub Create Pull Request
Storage Require secure transfer to ensure secure connections ...cles/storage/common/storage-require-secure-transfer.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed PowerShell examples and instructions before Azure CLI examples, which may indicate a Windows-first and PowerShell-heavy bias. While Azure CLI is cross-platform and included, the PowerShell section is more prominent and detailed, and appears before CLI instructions. No Linux-specific tools or shell examples are given, and there is no mention of macOS or Linux environments in the setup or usage instructions.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Bash or shell script examples for checking and setting the property using REST API (e.g., with curl or httpie).
  • Include installation instructions for Azure CLI on Linux/macOS.
  • Clarify that PowerShell is available cross-platform, but CLI may be more familiar to Linux/macOS users.
GitHub Create Pull Request
Storage Call REST API operations with Shared Key authorization .../main/articles/storage/common/storage-rest-api-auth.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. It exclusively uses C# code samples intended for Visual Studio, references only Windows tooling (e.g., Fiddler), and assumes a Windows development environment. There are no Linux/macOS code samples, nor any mention of equivalent Linux development tools or workflows. The prerequisites and workflow are tailored to Windows users, creating friction for those on other platforms.
Recommendations
  • Add equivalent code samples in languages commonly used on Linux/macOS (e.g., Python, curl, Bash, Java).
  • Include instructions for setting up the sample on Linux/macOS, such as using VS Code, Mono, .NET Core CLI, or other cross-platform IDEs.
  • Mention and provide examples of Linux/macOS-compatible HTTP debugging tools (e.g., Wireshark, mitmproxy, curl with verbose output) alongside Fiddler.
  • Clarify that the REST API can be called from any platform and provide platform-agnostic sample requests (e.g., using curl).
  • Update prerequisites to include cross-platform options for development environments.
GitHub Create Pull Request
Storage Azure data transfer options for small datasets with low to moderate network bandwidth ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-small-dataset-low-moderate-network.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page shows a moderate Windows bias. While cross-platform tools like Azure Storage Explorer, AzCopy, and Azure CLI are mentioned, Windows-specific tools (notably Azure PowerShell) are highlighted alongside cross-platform options without clarifying their platform limitations. PowerShell is listed before Azure CLI, and there is no explicit mention of Linux/macOS scripting alternatives or examples. The comparison table and recommendations do not provide Linux/macOS-specific guidance or parity for PowerShell functionality.
Recommendations
  • Explicitly clarify platform support for each scripting/programmatic tool, especially noting that Azure PowerShell is primarily for Windows (though PowerShell Core is cross-platform, this is not mentioned).
  • Provide Linux/macOS-specific examples or alternatives where PowerShell is mentioned, such as Bash scripts using Azure CLI.
  • When listing scripting/programmatic tools, avoid listing Windows-centric tools (like PowerShell) before cross-platform tools (like Azure CLI) unless justified.
  • Add example commands for both Windows (PowerShell/CMD) and Linux/macOS (Bash) where relevant.
  • Clarify that AzCopy and Azure CLI are fully cross-platform and provide links to Linux/macOS installation guides.
GitHub Create Pull Request
Storage Authorize access for AzCopy with a managed identity ...ommon/storage-use-azcopy-authorize-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for environment variable configuration, but consistently lists Windows-specific tools (PowerShell, Azure PowerShell) and links to Windows VM configuration guides before or instead of Linux equivalents. Azure PowerShell is emphasized, and Windows instructions are sometimes shown first or in greater detail. There are no explicit Linux VM configuration links, and the use of PowerShell is assumed for Windows users, which may create friction for Linux/macOS users.
Recommendations
  • Include links and instructions for configuring managed identities on Linux VMs, not just Windows VMs.
  • Ensure Linux/macOS examples are presented with equal prominence and detail as Windows/PowerShell examples.
  • Provide parity in CLI usage examples, e.g., using Bash or sh for Linux/macOS, and avoid assuming PowerShell as the default for Windows.
  • Add explicit notes or sections for macOS users where applicable.
  • When referencing Azure CLI and PowerShell, clarify cross-platform support and provide guidance for Linux/macOS users.
GitHub Create Pull Request
Storage Authorize access for AzCopy with a service principal ...mmon/storage-use-azcopy-authorize-service-principal.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides both Linux and Windows examples for setting environment variables, but consistently uses PowerShell for interactive prompts and sensitive variable input, with no equivalent Linux shell examples (e.g., 'read -s' in bash). Windows-specific tools like Export-PfxCertificate are referenced for certificate export, with no Linux alternatives mentioned. In some sections, Windows/PowerShell commands are shown first or exclusively, and the use of PowerShell is assumed for secure input, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Linux/macOS shell examples for interactive variable input (e.g., using 'read -s' in bash for secrets).
  • Include Linux/macOS alternatives for certificate export (e.g., using 'openssl' to export/create .PFX/.PEM files).
  • Ensure that both Linux and Windows examples are presented side-by-side or in parallel tabs, and avoid showing Windows/PowerShell commands first or exclusively.
  • Clarify cross-platform differences in secret storage and provide guidance for Linux users where features (like secret stores) may differ.
  • Review all references to Windows tools and add Linux/macOS equivalents or links to relevant documentation.
GitHub Create Pull Request
Storage Authorize access for AzCopy with a user identity ...e/common/storage-use-azcopy-authorize-user-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Linux (bash) and Windows (PowerShell) examples for environment variable setup, but Windows/PowerShell is consistently mentioned and shown alongside or before Linux. Azure PowerShell is given its own section, while Linux alternatives (such as bash scripting or native Linux authentication tools) are not discussed. The documentation references Windows-specific concepts like 'secret store' and PowerShell commands, and Azure PowerShell is highlighted as a tool for authentication, with no Linux-native equivalents suggested.
Recommendations
  • Ensure Linux examples are presented first or equally alongside Windows examples.
  • Provide Linux-native alternatives to Azure PowerShell for authentication, such as using bash scripts or other CLI tools.
  • Clarify what Linux users should do if their system lacks a keyring, and suggest cross-platform secret store solutions.
  • Add explicit macOS instructions where relevant.
  • Avoid assuming PowerShell is available on Linux; mention bash and other shells as primary options.
GitHub Create Pull Request
Storage Synchronize with Azure Blob storage by using AzCopy v10 ...storage/common/storage-use-azcopy-blobs-synchronize.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides AzCopy command examples using Windows-style paths (e.g., 'C:\myDirectory') and does not include Linux/macOS path examples (e.g., '/home/user/myDirectory'). Tips about quoting are present, but Windows paths and conventions are shown first and exclusively in all examples involving local directories. No Linux/macOS-specific examples or shell usage patterns are provided.
Recommendations
  • Add Linux/macOS examples alongside Windows examples, using POSIX-style paths (e.g., '/home/user/myDirectory').
  • Show both Windows and Linux/macOS command syntax for local file system operations.
  • Explicitly mention that AzCopy works cross-platform and provide guidance for common Linux/macOS shells (bash, zsh, etc.).
  • Alternate the order of examples so Linux/macOS is not always secondary to Windows.
GitHub Create Pull Request
Storage Upload files to Azure Blob storage by using AzCopy v10 ...cles/storage/common/storage-use-azcopy-blobs-upload.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style file paths (e.g., 'C:\myDirectory\myTextFile.txt') in all command examples and does not provide equivalent Linux/macOS examples (e.g., '/home/user/myDirectory/myTextFile.txt'). While there are tips about quoting differences between shells, all concrete examples use Windows paths and patterns, which may confuse or inconvenience Linux/macOS users.
Recommendations
  • Provide Linux/macOS examples alongside Windows examples, using POSIX-style paths (e.g., '/home/user/myDirectory/myTextFile.txt').
  • Explicitly mention shell differences in wildcard usage and path separators.
  • For each example, show both Windows and Linux/macOS variants, or use a generic placeholder path.
  • Add a section or table summarizing cross-platform differences in AzCopy usage.
GitHub Create Pull Request
Storage Download blobs from Azure Blob Storage by using AzCopy v10 ...es/storage/common/storage-use-azcopy-blobs-download.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style paths (e.g., 'C:\myDirectory\myTextFile.txt') in all examples and does not provide any Linux/macOS path examples (e.g., '/home/user/myTextFile.txt'). Windows paths are shown exclusively, and there is no parity for Linux/macOS users in terms of example commands or output. While there are notes about quoting differences between shells, the actual examples remain Windows-centric.
Recommendations
  • For each example, provide both Windows and Linux/macOS versions, showing appropriate local paths (e.g., 'C:\myDirectory' and '/home/user/myDirectory').
  • Alternate the order of examples so Linux/macOS is shown first in some cases.
  • Add a section or table summarizing shell differences, including quoting and path formats for Windows (cmd.exe), PowerShell, Bash, and zsh.
  • Explicitly mention that AzCopy is cross-platform and provide guidance for Linux/macOS users on installation and usage.
  • Ensure that all flags and options are demonstrated in both Windows and Linux/macOS contexts.
GitHub Create Pull Request
Storage Find errors & resume jobs with logs in AzCopy (Azure Storage) ...rticles/storage/common/storage-use-azcopy-configure.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias in several areas. The example for reviewing logs uses the Windows PowerShell 'Select-String' command for both Linux and Windows tabs, omitting a native Linux alternative (e.g., 'grep'). Additionally, environment variable examples use PowerShell syntax for Windows and bash syntax for Linux, but the log review section does not provide a Linux-specific command. The default log/plan file location is described with Windows syntax first, and the tip about quoting paths is focused on Windows cmd.exe, with Linux/macOS as an afterthought.
Recommendations
  • Provide native Linux/macOS command examples (e.g., use 'grep UPLOADFAILED ...' for log review on Linux/macOS).
  • Ensure Linux/macOS instructions are given equal prominence and clarity as Windows instructions.
  • When discussing file paths and environment variables, present Linux/macOS conventions first or side-by-side with Windows.
  • Expand tips to include shell-specific guidance for Linux/macOS users (e.g., bash, zsh).
GitHub Create Pull Request
Storage Copy or move data to Azure Storage by using AzCopy v10 ...main/articles/storage/common/storage-use-azcopy-v10.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally presents AzCopy as a cross-platform tool, but there is a notable Windows bias in example usage and ordering. The only concrete command example uses a Windows file path (C:\local\path) and does not show a Linux/macOS equivalent. In download instructions, Windows binaries are listed first, and decompression instructions for Linux are deferred to external documentation. There are no explicit PowerShell-only instructions or exclusive references to Windows tools, but the lack of Linux/macOS command examples and the Windows-first ordering create friction for non-Windows users.
Recommendations
  • Provide parallel example commands using Linux/macOS file paths (e.g., /home/user/path) alongside Windows examples.
  • Alternate or randomize the order of OS download links to avoid implicit prioritization.
  • Include basic Linux/macOS decompression instructions (e.g., tar -xvf) directly in the documentation.
  • Clarify shell usage for each OS (e.g., Bash for Linux/macOS, Command Prompt/PowerShell for Windows) when discussing command syntax.
  • Ensure all critical examples and instructions are shown for both Windows and Linux/macOS users.
GitHub Create Pull Request
Storage Configure Transport Layer Security (TLS) for a client application ...n/transport-layer-security-configure-client-version.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides examples only for PowerShell and .NET, both of which are primarily Windows-centric. There are no examples for configuring TLS in Linux/macOS environments or using common Linux tools. The verification step recommends Fiddler, a Windows-only tool, without mentioning Linux alternatives. The order and content create a clear Windows-first bias, and Linux/macOS users are left without direct guidance.
Recommendations
  • Add examples for configuring TLS in Linux/macOS environments, such as using curl, wget, or OpenSSL.
  • Include instructions for setting TLS versions in Python, Java, or other cross-platform languages.
  • Suggest Linux/macOS-compatible network tracing tools (e.g., Wireshark, tcpdump, mitmproxy) for TLS verification.
  • Present examples for multiple platforms side-by-side or in tabs, rather than Windows-only.
  • Explicitly mention OS support and differences in TLS configuration.
GitHub Create Pull Request
← Previous Page 45 of 67 Next →