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 101-125 of 1657 flagged pages
Storage Enable and manage Azure Storage Analytics logs (classic) ...ticles/storage/common/manage-storage-analytics-logs.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias. PowerShell is the only CLI example provided, and instructions explicitly reference opening a Windows PowerShell command window. There are no Bash, Azure CLI, or Linux shell examples for enabling or managing Storage Analytics logs. File paths in examples use Windows conventions (e.g., 'C:\Logs\Storage'), and Windows-centric tools (PowerShell, Storage Explorer) are mentioned before or instead of cross-platform or Linux-native alternatives. There is no mention of Linux or macOS compatibility, nor guidance for users on those platforms.
Recommendations
  • Add Azure CLI examples for enabling and managing Storage Analytics logs, with explicit instructions for Bash/shell environments.
  • Include Linux/macOS-specific guidance for viewing and managing logs, such as using AzCopy with Linux file paths and shell commands.
  • Mention cross-platform compatibility of tools (e.g., Storage Explorer, AzCopy) and provide download/use instructions for Linux/macOS.
  • Avoid language that assumes the user is on Windows (e.g., 'Open a Windows PowerShell command window'); use platform-neutral phrasing.
  • Provide sample file paths and commands for both Windows and Linux/macOS environments.
  • List Linux/macOS alternatives alongside Windows tools, or present them first in sections where parity exists.
GitHub Create Pull Request
Storage Configure passwordless connections between multiple services ...articles/storage/common/multiple-identity-scenarios.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias primarily through its reliance on Azure Portal GUI instructions, which are more commonly used on Windows, and references to Windows-centric developer tools (e.g., Visual Studio) for local development. There is no mention of Linux-specific tools or command-line alternatives (such as Azure CLI or PowerShell commands for identity and role assignment), and the local development guidance assumes use of Visual Studio or Azure CLI without providing parity for Linux environments. The examples for configuring managed identities and role assignments are exclusively portal-based, omitting CLI or script-based workflows that are preferred in Linux and cross-platform scenarios.
Recommendations
  • Add Azure CLI and/or PowerShell command examples for enabling managed identities and assigning roles, alongside portal instructions.
  • Explicitly mention Linux-compatible development tools (e.g., VS Code, JetBrains IDEs) and provide guidance for configuring local development environments on Linux.
  • Include notes or sections on how to perform all steps (identity creation, role assignment, credential configuration) on Linux, with sample commands.
  • Ensure that references to developer tooling do not assume Windows/Visual Studio as the default, and provide alternatives for Linux/macOS users.
  • Where screenshots are used, consider including CLI output or cross-platform UI examples.
GitHub Create Pull Request
Storage Prevent authorization with Shared Key ...les/storage/common/shared-key-authorization-prevent.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting PowerShell instructions before Azure CLI, referencing Windows-specific tools (e.g., Storage Explorer with Windows tab), and omitting explicit Linux/macOS command-line examples or considerations. The Azure portal and PowerShell are emphasized, while Linux-native shell usage and cross-platform nuances are not addressed.
Recommendations
  • Provide explicit Linux/macOS command-line examples, including shell syntax and installation notes for Azure CLI on those platforms.
  • Include instructions for using Azure CLI in Bash or Zsh, and clarify any differences in command usage or authentication flows on Linux/macOS.
  • Reference cross-platform tools and clarify their support (e.g., Storage Explorer on Linux/macOS, AzCopy usage on Linux).
  • Balance the order of examples: present Azure CLI before PowerShell or side-by-side, and avoid defaulting to Windows-first instructions.
  • Add troubleshooting notes for Linux users (e.g., file permissions, environment variables, authentication issues).
GitHub Create Pull Request
Storage Get storage account configuration information ...in/articles/storage/common/storage-account-get-info.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently presents PowerShell examples alongside Azure CLI and portal instructions, with PowerShell often mentioned before Azure CLI. PowerShell is a Windows-centric tool, and no Linux-specific shell examples (e.g., Bash, zsh) or platform notes are provided. There is no mention of Linux-specific considerations, nor are alternative Linux-native tools or scripting patterns discussed. This creates a subtle bias toward Windows users and workflows.
Recommendations
  • Add explicit Bash examples for Azure CLI commands, showing usage in Linux/macOS terminals (e.g., with environment variables, piping, jq for JSON parsing).
  • Include notes clarifying that Azure CLI works cross-platform, and provide examples of command usage in Linux shells.
  • Where PowerShell is used, clarify that PowerShell Core is available on Linux/macOS, or provide equivalent Bash commands for property extraction.
  • Consider mentioning Linux-native tools (e.g., curl for REST API calls, jq for JSON parsing) in relevant sections.
  • Reorder examples so that Azure CLI (cross-platform) is presented before PowerShell, or present both equally.
GitHub Create Pull Request
Storage Change how a storage account is replicated ...b/main/articles/storage/common/redundancy-migration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation consistently presents Windows-oriented tools and patterns first, with PowerShell examples and terminology appearing before Azure CLI or cross-platform alternatives. PowerShell scripts are more detailed and feature-rich than their CLI counterparts, including advanced usage such as CSV batch processing. There are no explicit Linux shell script examples, and the CLI examples use generic shell syntax without addressing Linux-specific considerations (e.g., bash, zsh, file paths, permissions). The documentation does not mention Linux-native tools or workflows, nor does it provide parity in scripting sophistication between PowerShell and CLI examples.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples so that CLI is presented first in some sections, reflecting cross-platform priorities.
  • Expand Azure CLI examples to match the depth and features of PowerShell scripts, including robust batch processing, error handling, and output formatting.
  • Provide explicit Linux shell script examples (bash, zsh) for batch operations, including handling of CSV files, file paths, and permissions.
  • Mention Linux-native tools (e.g., shell scripting, cron for scheduling migrations) where appropriate.
  • Clarify that Azure CLI is cross-platform and provide guidance for both Windows and Linux environments (e.g., differences in file paths, line endings).
  • Ensure screenshots and UI references do not assume Windows usage (e.g., file explorer, path formats).
GitHub Create Pull Request
Storage Permitted scope for copy operations (preview) ...es/storage/common/security-restrict-copy-operations.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples and instructions before Azure CLI, with no mention of Linux-specific shell usage or examples. The PowerShell section is detailed and assumes familiarity with Windows tooling, while the Azure CLI instructions are generic and do not reference Linux environments or shell-specific considerations. There are no explicit Linux or macOS command-line examples, nor any mention of Bash, zsh, or other common Linux shells.
Recommendations
  • Add explicit Linux/macOS examples using Bash/zsh for Azure CLI commands, including shell-specific syntax (e.g., environment variable usage, quoting).
  • Clarify that Azure CLI is cross-platform and provide instructions for installing and running it on Linux and macOS, not just generic installation.
  • Reorder the configuration sections to present Azure CLI before PowerShell, as CLI is more commonly used in Linux environments.
  • Mention that PowerShell is available cross-platform, but provide Bash alternatives for Linux users.
  • Include troubleshooting notes or tips relevant to Linux environments (e.g., permissions, path differences, dependency installation).
GitHub Create Pull Request
Storage Create an Azure storage account ...main/articles/storage/common/storage-account-create.md
High Priority View Details →
Scanned: 2026-01-11 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 consistently presented as a primary automation method, often before Azure CLI, and detailed PowerShell examples are provided for key tasks. References to Windows-specific tools (PowerShell) are prevalent, and instructions for deploying Bicep and ARM templates use PowerShell as the first example. While Azure CLI examples are present and Cloud Shell is mentioned (which supports Bash), there is little explicit mention of Linux-specific environments, shells, or considerations. The documentation does not reference Linux package managers, shell environments (e.g., bash, zsh), or alternative scripting approaches, and does not clarify cross-platform differences in command usage or installation.
Recommendations
  • Explicitly mention Linux environments and shells (e.g., bash, zsh) in prerequisites and usage instructions.
  • Provide installation instructions for Azure CLI and Developer CLI using Linux package managers (apt, yum, etc.), not just generic links.
  • When presenting examples for deploying Bicep or ARM templates, alternate the order of PowerShell and CLI examples, or present CLI first to avoid Windows-first perception.
  • Clarify that all CLI examples work natively on Linux/macOS, and note any differences in command syntax or environment setup.
  • Include troubleshooting or tips for common Linux-specific issues (e.g., file permissions, environment variables).
  • Reference Linux tools or scripting approaches where relevant, and avoid assuming PowerShell is the default automation tool.
GitHub Create Pull Request
Storage Azure Storage Analytics logging ...n/articles/storage/common/storage-analytics-logging.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates a Windows bias in several ways: PowerShell is the only command-line example provided for interacting with log blobs, with no equivalent Bash/Azure CLI example for Linux/macOS users. References to tools and user agents in log entries are predominantly Windows-based (e.g., 'win32', 'Windows_NT'), and Microsoft Azure Storage Explorer is mentioned without noting cross-platform support. The ordering of instructions and examples tends to mention Windows tools or PowerShell before Azure CLI or REST API, and there is a lack of explicit Linux/macOS guidance or examples.
Recommendations
  • Add equivalent Azure CLI and/or Bash examples alongside PowerShell snippets for blob listing and metadata filtering.
  • Explicitly mention that Microsoft Azure Storage Explorer is cross-platform, and provide examples or screenshots for Linux/macOS.
  • Include references to Linux/macOS environments in sample log entries (e.g., user agents showing Linux or Darwin).
  • When listing ways to enable logging, mention Azure CLI and REST API before or alongside PowerShell to avoid Windows-first ordering.
  • Add guidance for using storage browsing tools on Linux/macOS (e.g., AzCopy, CLI, third-party tools).
GitHub Create Pull Request
Storage Upgrade to a general-purpose v2 storage account ...ain/articles/storage/common/storage-account-upgrade.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is given a dedicated example and section, and instructions for upgrading via PowerShell are detailed before Azure CLI. PowerShell is a Windows-centric tool, and its installation/configuration is referenced, while Linux-native tools or shell examples (e.g., Bash) are not mentioned. The CLI example is present, but there is no explicit mention of Linux or macOS environments, nor are there any Bash or shell script examples. The documentation assumes familiarity with Windows tools and patterns.
Recommendations
  • Add explicit Bash/shell script examples for Linux/macOS users, especially for Azure CLI usage.
  • Clarify that Azure CLI commands work cross-platform and provide installation instructions for Linux/macOS alongside Windows.
  • Reorder sections so that cross-platform tools (Azure CLI) are presented before Windows-specific tools (PowerShell).
  • Mention Linux/macOS environments in the instructions and provide troubleshooting or tips relevant to those platforms.
  • Consider adding a table comparing upgrade methods across platforms (Portal, PowerShell, CLI, REST API) with platform compatibility notes.
GitHub Create Pull Request
Storage Azure storage disaster recovery planning and failover ...s/storage/common/storage-disaster-recovery-guidance.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its exclusive mention of Windows-centric tools (AzCopy, Azure PowerShell) for data copy and backup operations, without referencing Linux equivalents or CLI usage. Windows tools are listed first and sometimes solely, and there are no examples or instructions for Linux users (e.g., Azure CLI, bash scripts). This may hinder Linux users from easily following disaster recovery steps or best practices.
Recommendations
  • Include Azure CLI examples alongside Azure PowerShell for all relevant operations, especially data copy and failover tasks.
  • Mention and provide examples for AzCopy usage on Linux/macOS, including installation and command-line syntax.
  • Add bash script samples for common operations (e.g., copying blobs, checking sync status) to ensure Linux parity.
  • Explicitly state cross-platform compatibility for tools like AzCopy and clarify any OS-specific limitations.
  • List Linux tools and patterns before or alongside Windows tools to avoid 'windows_first' ordering.
  • Reference documentation for Linux users (e.g., Azure CLI docs, shell scripting guides) in 'See also' sections.
GitHub Create Pull Request
Storage Determine which encryption key model is in use for the storage account ...les/storage/common/storage-encryption-key-model-get.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation presents three methods for determining the encryption key model: Azure portal, PowerShell, and Azure CLI. PowerShell is featured as a primary command-line example, which is Windows-centric, and is listed before Azure CLI, which is cross-platform. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-specific tools or patterns. The Azure CLI example is generic, but the absence of Bash-specific usage or Linux terminal screenshots suggests a subtle Windows bias.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI usage, including sample commands and expected output.
  • Include notes or screenshots showing how to perform these steps on Linux/macOS terminals.
  • Consider listing Azure CLI before PowerShell, as it is cross-platform and more accessible to Linux users.
  • Mention that PowerShell Core is available on Linux, if PowerShell usage is necessary, and provide Linux installation instructions or examples.
GitHub Create Pull Request
Storage Initiate a storage account failover ...es/storage/common/storage-initiate-account-failover.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias by providing extensive, detailed PowerShell instructions (including module installation, troubleshooting, and advanced usage) before Azure CLI examples. PowerShell, a Windows-centric tool, is given more prominence and depth than the cross-platform Azure CLI. There are no Linux-specific shell (bash) examples, and all command-line guidance assumes PowerShell or Azure CLI, with PowerShell presented first and in greater detail.
Recommendations
  • Provide bash (Linux/macOS) shell examples alongside PowerShell for all command-line instructions, especially for Azure CLI usage.
  • Reorder sections to present Azure CLI examples before or alongside PowerShell, as Azure CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any OS-specific installation or troubleshooting notes.
  • Where PowerShell-specific troubleshooting or module management is discussed, offer equivalent guidance for bash or zsh users (e.g., virtual environments, PATH issues).
  • Avoid assuming PowerShell as the default shell for command-line instructions; clarify which shell is being used and offer parity for Linux users.
GitHub Create Pull Request
Storage Introduction to Azure Storage - Cloud storage on Azure ...b/main/articles/storage/common/storage-introduction.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a moderate Windows bias. Windows tools and protocols (such as PowerShell and SMB) are mentioned first or exclusively in several sections, and scripting examples reference Azure PowerShell before Azure CLI. There is a lack of explicit Linux-focused examples, and Windows terminology (e.g., drive letters, Active Directory) is more prevalent than Linux equivalents. Although some cross-platform tools (Azure CLI, AzCopy, Storage Explorer) are mentioned, Linux-specific usage patterns and examples are underrepresented.
Recommendations
  • Provide explicit Linux and macOS usage examples alongside Windows and PowerShell, especially for scripting and mounting shares.
  • Mention Linux tools (e.g., mount, rsync, scp, NFS client usage) and patterns when discussing file shares and data transfer.
  • When listing protocols (SMB, NFS), avoid referencing Windows documentation exclusively; link to cross-platform or Linux-specific resources as well.
  • Balance the order of tool mentions (e.g., list Azure CLI before or alongside PowerShell) and clarify cross-platform compatibility.
  • Include sample commands for mounting Azure Files on Linux (e.g., using mount.cifs or mount.nfs) and accessing Blob Storage via Linux tools.
  • Highlight Linux authentication options (e.g., Kerberos, LDAP) where relevant, not just Active Directory.
  • Add troubleshooting or best practices sections for Linux users where Windows-specific advice is given.
GitHub Create Pull Request
Storage Install and run the Azurite emulator for Azure Storage ...ain/articles/storage/common/storage-install-azurite.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by prioritizing Windows-centric tools (Visual Studio, Visual Studio Code), providing file path and command examples exclusively in Windows format (e.g., c:\azurite), and omitting explicit Linux/macOS instructions or examples. The Visual Studio tab and executable location table are Windows-only, and all command-line and Docker volume examples use Windows paths. There are no Linux or macOS equivalents or guidance for non-Windows environments, despite Azurite being cross-platform.
Recommendations
  • Add explicit Linux/macOS instructions and examples for installing and running Azurite, including file paths (e.g., /home/user/azurite) and shell commands.
  • Include Visual Studio alternatives for Linux/macOS users, such as JetBrains Rider or command-line workflows.
  • Provide Docker volume mount examples using Linux paths (e.g., -v /home/user/azurite:/data).
  • Clarify that Azurite works cross-platform and highlight any OS-specific differences or requirements.
  • Ensure that all command-line options and configuration examples are shown for both Windows and Linux/macOS environments, possibly using tabs or side-by-side examples.
GitHub Create Pull Request
Storage Guidelines & limitations: Azure Storage firewall ...storage/common/storage-network-security-limitations.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page references tools such as Azure portal, Azure Storage Explorer, AzCopy, and PowerShell for managing Azure Storage firewall settings. While Azure CLI is mentioned, PowerShell is listed first and more prominently. There are no explicit Linux-specific examples or mentions of Linux-native tools or command-line patterns, and no guidance for Linux users is provided. The documentation implicitly assumes familiarity with Windows-centric tooling and workflows.
Recommendations
  • Provide explicit examples for both PowerShell and Azure CLI, and ensure Azure CLI (cross-platform) is mentioned before or alongside PowerShell.
  • Include Linux-specific usage notes or examples, such as shell commands for AzCopy or Azure CLI.
  • Reference Linux-native tools or workflows where applicable (e.g., bash scripting, Linux authentication patterns).
  • Avoid listing Windows tools (PowerShell) before cross-platform alternatives unless contextually justified.
  • Add a section or callout for Linux/macOS users to clarify parity and any platform-specific considerations.
GitHub Create Pull Request
Storage Create an IP network rule for Azure Storage ...ge/common/storage-network-security-ip-address-range.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed PowerShell examples for managing Azure Storage network rules, which are primarily relevant to Windows users. PowerShell is presented before Azure CLI, and there are no explicit Linux shell or scripting examples. The use of PowerShell commands and installation instructions may implicitly favor Windows environments, while Linux users are only served by the Azure CLI section, which is presented after PowerShell.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide installation instructions for each platform.
  • Add Bash shell script examples for common tasks, demonstrating usage in native Linux environments.
  • Include notes or links to Linux-specific guidance for managing Azure Storage network rules.
  • Consider adding a table comparing PowerShell and CLI commands for parity and quick reference.
GitHub Create Pull Request
Storage Azure Storage migration tools selection guide ...ain/articles/storage/common/storage-migration-tools.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a Windows bias in several ways: Windows-centric tools and scenarios (such as Azure File Sync for Windows file servers) are described in detail and appear before Linux/NFS equivalents. Windows protocols (SMB) and tools (Robocopy, PowerShell) are mentioned more prominently or exclusively, while Linux-native tools (rsync, DistCP) are listed later and with less detail. There is a lack of Linux-specific migration examples, especially for NFS or POSIX file servers, and PowerShell/Windows Server patterns are referenced without equivalent Bash/Linux guidance.
Recommendations
  • Provide equal detail and step-by-step examples for Linux/NFS migration scenarios, including POSIX file servers and Linux-based NAS.
  • Include Linux command-line examples (e.g., Bash, rsync, scp) alongside PowerShell/Robocopy examples for each migration tool.
  • Highlight Linux-compatible tools and workflows (such as AzCopy on Linux, rsync, DistCP) earlier in the document, not just in summary tables.
  • Add explicit guidance for migrating from Linux environments, including handling of NFS permissions, file attributes, and metadata.
  • Ensure graphical and programmatic tool sections mention Linux support and provide instructions for Linux users (e.g., Azure CLI on Linux, SDKs in Python/Go).
  • Balance the discussion of Windows and Linux protocols (SMB vs NFS) and clarify tool limitations or requirements for each OS.
GitHub Create Pull Request
Storage Create a virtual network rule for Azure Storage ...ge/common/storage-network-security-virtual-networks.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed PowerShell examples for managing Azure Storage virtual network rules, which are primarily relevant to Windows environments. PowerShell is presented as a first-class method alongside Azure CLI, but there are no explicit Linux shell (bash) or cross-platform scripting examples. The use of PowerShell commands and terminology may implicitly favor Windows users, and the installation instructions for PowerShell are included without mention of Linux alternatives or parity notes.
Recommendations
  • Add explicit bash shell examples for each CLI command, demonstrating usage in a typical Linux environment.
  • Clarify that Azure CLI is fully cross-platform and highlight its use on Linux and macOS.
  • Include installation and authentication instructions for Azure CLI on Linux and macOS, not just generic links.
  • Where PowerShell is referenced, note that PowerShell Core is available cross-platform, and provide examples for Linux/macOS usage if relevant.
  • Consider reordering tabs to present Azure CLI before PowerShell, or clarify that both are equally supported across platforms.
  • Add a note or section on scripting these operations in bash or other Linux-native shells.
GitHub Create Pull Request
Storage Use private endpoints ...n/articles/storage/common/storage-private-endpoints.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias in its guidance for creating private endpoints. It lists PowerShell and Azure CLI as the only automation options, with PowerShell mentioned explicitly and CLI linked but not explained. There are no explicit Linux shell (bash) examples or references to Linux-specific tools or workflows. The examples and instructions do not mention Linux environments, nor do they provide parity for Linux users in terms of step-by-step instructions or troubleshooting. Windows tools and patterns (PowerShell, Azure Portal) are mentioned first or exclusively, while Linux equivalents are missing.
Recommendations
  • Add explicit bash (Linux shell) examples for creating and managing private endpoints using Azure CLI.
  • Clarify that Azure CLI commands work cross-platform and provide sample commands for Linux/macOS terminals.
  • Include troubleshooting steps or notes relevant to Linux environments (e.g., DNS configuration on Linux servers).
  • Balance the order of instructions so that CLI (cross-platform) examples appear before or alongside PowerShell examples.
  • Reference Linux-native tools (such as curl for REST API calls) where appropriate.
  • Ensure that screenshots and UI references are not Windows-specific, or provide Linux alternatives where possible.
GitHub Create Pull Request
Storage Azure Storage Geo Priority Replication ...rage/common/storage-redundancy-priority-replication.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. PowerShell examples are provided alongside Azure CLI, but the CLI examples use Windows-style variable assignment and login commands (Connect-AzAccount), which are not valid on Linux/macOS shells. There is no mention of Bash or Linux-specific usage patterns, nor are there examples showing how to use the Azure CLI in a Linux environment. The PowerShell tab appears before the CLI tab, and all scripting examples assume a Windows context. No Linux tools or shell scripting examples are provided.
Recommendations
  • Provide Azure CLI examples using Bash syntax, with Linux/macOS-compatible variable assignment and authentication (e.g., 'az login').
  • Add explicit instructions for running Azure CLI commands on Linux/macOS, including installation and environment notes.
  • Reorder tabs so that Azure CLI (cross-platform) appears before PowerShell (Windows-specific).
  • Include notes or examples for Linux users, such as using Bash scripts or running commands in a Linux terminal.
  • Avoid using Windows-specific commands (e.g., Connect-AzAccount) in CLI examples; use 'az login' for CLI authentication.
GitHub Create Pull Request
Storage AzCopy v10 configuration setting (Azure Storage) ...ge/common/storage-ref-azcopy-configuration-settings.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias in several ways: Windows commands and PowerShell examples are consistently presented first, with Linux/macOS equivalents following. Proxy configuration instructions and bypassing proxy examples are detailed for Windows (CMD and PowerShell), but Linux/macOS instructions are minimal or absent for certain scenarios (e.g., proxy bypass). Windows-specific behaviors (e.g., automatic proxy detection, Event Logger) are described in detail, while Linux-specific behaviors are less emphasized. Some environment variables mention Windows explicitly, with Linux notes as afterthoughts.
Recommendations
  • Present Linux/macOS examples before or alongside Windows examples to avoid Windows-first ordering.
  • Provide equivalent detailed instructions for Linux/macOS, especially for proxy bypass and environment variable configuration.
  • Include shell-specific examples for Linux (e.g., bash, zsh) where appropriate, not just 'export'.
  • Clarify platform-specific behaviors for all OSes, not just Windows (e.g., logging destinations, proxy detection).
  • Add notes or sections highlighting Linux/macOS best practices and troubleshooting tips, similar to Windows coverage.
  • Review environment variable descriptions to ensure Linux/macOS relevance is equally emphasized.
GitHub Create Pull Request
Storage Call REST API operations with Shared Key authorization .../main/articles/storage/common/storage-rest-api-auth.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing exclusively on Windows development tools (Visual Studio), providing only C# code samples, and referencing Windows-centric utilities (Fiddler) for network inspection. There are no Linux-specific instructions, alternative IDEs, or cross-platform code samples (e.g., Python, curl, bash). The prerequisites and workflow assume a Windows environment, and Linux development scenarios are not addressed.
Recommendations
  • Add instructions for setting up the sample on Linux, including alternative IDEs (e.g., VS Code, JetBrains Rider) and .NET Core/SDK installation steps.
  • Provide code samples in cross-platform languages such as Python (using requests), curl, or bash scripts to demonstrate REST API calls.
  • Mention Linux-compatible network inspection tools (e.g., Wireshark, tcpdump, mitmproxy) alongside or instead of Fiddler.
  • Clarify that the REST API can be called from any OS, and provide explicit examples for Linux and macOS environments.
  • Include troubleshooting tips for Linux users, such as handling SSL certificates or configuring environment variables.
GitHub Create Pull Request
Storage Grant limited access to data with shared access signatures (SAS) ...b/main/articles/storage/common/storage-sas-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. In the 'Get started with SAS' section, PowerShell is listed first for user delegation SAS examples, and there is no Bash or Linux shell example provided. The only command-line examples are PowerShell (Windows-centric) and Azure CLI (cross-platform but not explicitly Linux/Bash-focused). There are no explicit Linux or Bash examples, nor are Linux tools or patterns mentioned. The note about generating SAS tokens references PowerShell and Azure CLI, but does not mention Bash or Linux-specific workflows.
Recommendations
  • Add explicit Bash/Linux shell examples for creating SAS tokens, especially in the 'Get started with SAS' section.
  • Ensure that Azure CLI examples are presented with Linux/Bash syntax (e.g., using environment variables, piping, etc.), and clarify cross-platform usage.
  • Consider listing Azure CLI or Bash examples before PowerShell to avoid 'windows_first' ordering.
  • Reference Linux tools (such as curl, jq, or AzCopy on Linux) where relevant, and provide guidance for Linux users.
  • Add notes or links for Linux users on how to install and use Azure CLI and AzCopy on Linux systems.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (Robocopy) for offline transfers, listing AzCopy and Azure PowerShell before Azure CLI in the comparison table, and omitting explicit Linux or cross-platform examples for data transfer. There are no Linux-specific tools or usage patterns mentioned, nor are Linux command-line examples provided.
Recommendations
  • Include Linux-specific or cross-platform data transfer tools and examples, such as rsync, scp, or native Linux file copy commands for offline transfers.
  • Provide explicit instructions and examples for using AzCopy and Azure CLI on Linux and macOS, not just Windows.
  • Mention cross-platform alternatives to Robocopy, such as rsync, and clarify which tools are available on which operating systems.
  • Ensure that Azure CLI is listed alongside or before Azure PowerShell, as CLI is cross-platform.
  • Add a section or table column indicating OS compatibility for each tool and service.
  • Where possible, provide step-by-step examples for both Windows and Linux environments for key transfer scenarios.
GitHub Create Pull Request
Storage Authorize access for AzCopy with a managed identity ...ommon/storage-use-azcopy-authorize-managed-identity.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation exhibits a moderate Windows bias. References to enabling managed identities on VMs consistently link to Windows VM instructions, with no mention of Linux VM equivalents. Environment variable examples are provided for both Linux (bash) and Windows (PowerShell), but PowerShell is emphasized in several places, and the Azure PowerShell tool is discussed in detail. The Azure CLI section uses different environment variable values for Linux and Windows, with Windows using 'PSCRED' (PowerShell credential store), which may not be applicable outside Windows. There is no guidance for enabling managed identities on Linux VMs, and Windows tools/patterns (PowerShell, Windows VM links) are mentioned before or instead of Linux equivalents.
Recommendations
  • Add links and instructions for enabling managed identities on Linux VMs, not just Windows VMs.
  • Ensure that all environment variable examples are provided for both bash (Linux/macOS) and PowerShell (Windows), and clarify any platform-specific differences.
  • Review and explain the use of 'PSCRED' for AZCOPY_AUTO_LOGIN_TYPE on Windows, and clarify what should be used on Linux.
  • Include Azure CLI usage examples for both platforms, and avoid implying that PowerShell is required for Windows.
  • Where screenshots or UI instructions are given, note any differences for Linux VM configuration in the Azure portal.
  • Consider a parity checklist to ensure all steps and references are equally covered for Linux and Windows users.
GitHub Create Pull Request
← Previous Page 5 of 67 Next →