1359
Total Pages
1162
Linux-Friendly Pages
197
Pages with Bias
14.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

392 issues found
Showing 101-125 of 392 flagged pages
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a single example command using a Windows-style path (C:\local\path) and does not offer a Linux/macOS equivalent. Windows download links are listed first in the portable binary section, and the only explicit example uses Windows conventions. There is no PowerShell-specific content, but Linux users may experience friction due to the lack of direct examples for their platform.
Recommendations
  • Provide parallel example commands using Linux/macOS path syntax (e.g., /home/user/path) alongside Windows examples.
  • Alternate the order of download links or group them by OS family to avoid Windows-first presentation.
  • Explicitly mention how to decompress tar files on Linux and zip files on macOS, possibly with example commands.
  • Add notes or examples for running AzCopy in Linux/macOS shells (e.g., bash, zsh), including invocation syntax.
  • Ensure all example commands and instructions are OS-agnostic or include both Windows and Linux/macOS variants.
Storage How to use managed identities with Azure File Sync ...cles/storage/file-sync/file-sync-managed-identities.md
Medium Priority View Details →
Scanned: 2026-01-12 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 for configuring managed identities with Azure File Sync demonstrates a notable Windows bias. All command-line examples use PowerShell, and the required Az.StorageSync PowerShell module is Windows-centric. There are no CLI, Bash, or Linux-native instructions, nor is there mention of cross-platform alternatives. The documentation assumes the use of Windows tooling and patterns, which may create friction for Linux/macOS users, especially those managing Azure Arcโ€“enabled servers from non-Windows environments.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Clarify whether the Az.StorageSync module or its functionality is available via Azure CLI or REST API, and provide instructions if possible.
  • Add explicit guidance for Linux/macOS administrators, especially for Azure Arcโ€“enabled servers, including how to perform role assignments and managed identity configuration from non-Windows systems.
  • Reorder examples or provide tabs for Azure CLI, Bash, or REST API before or alongside PowerShell to avoid Windows-first presentation.
  • Mention any platform limitations or requirements up front so users can plan accordingly.
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
๐Ÿ”ง Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits moderate Windows bias, primarily in the tooling and example sections. PowerShell is presented first and in greater detail than Azure CLI, and Windows-specific tools and patterns (such as Azure File Sync with Windows file servers) are referenced exclusively for certain geo-redundancy scenarios. Linux/macOS alternatives are mentioned but not given equal prominence or detail.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell, with equal detail and explanation.
  • Include explicit Linux/macOS guidance for geo-redundancy scenarios, such as using NFS shares or Linux-based file servers with Azure File Sync (if supported), or alternative sync/copy strategies.
  • Reference cross-platform tools (e.g., AzCopy, rsync) with example usage for Linux/macOS in relevant sections.
  • Clarify any Windows-only limitations and provide Linux/macOS workarounds or alternatives where possible.
  • Ensure that diagrams and workflow descriptions do not assume Windows-only environments.
Storage Analyze Azure Files metrics with Azure Monitor ...b/main/articles/storage/files/analyze-files-metrics.md
Medium Priority View Details →
Scanned: 2026-01-12 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. PowerShell examples are provided in detail and appear before Azure CLI examples, which are more cross-platform. There is no mention of Linux-specific tools or shell scripting, and troubleshooting links reference Windows tabs. No explicit Linux/macOS examples or guidance are given, and screenshots and instructions are generic but do not address Linux-specific scenarios.
Recommendations
  • Add explicit Linux/macOS shell examples (e.g., Bash) for metric queries using Azure CLI.
  • Include troubleshooting links and instructions for Linux/macOS clients, not just Windows.
  • Ensure that CLI examples are presented before or alongside PowerShell to emphasize cross-platform support.
  • Reference Linux tools (such as curl, jq) for parsing metric outputs.
  • Add notes or sections addressing Linux-specific usage patterns or issues when monitoring Azure Files.
Storage Migrate to SMB Azure file shares using Azure Storage Mover .../articles/storage/files/migrate-files-storage-mover.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
๐Ÿ”ง Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows tools like Robocopy are referenced as alternatives, and migration examples or tool mentions (e.g., Azure File Sync) are Windows-centric. While the guide states that Linux SMB shares are supported, there are no Linux-specific examples, troubleshooting steps, or tool mentions. The agent deployment instructions mention Hyper-V and VMware, but do not discuss Linux VM environments or provide Linux command-line examples for agent registration, despite referencing SSH.
Recommendations
  • Add explicit Linux migration examples, such as migrating from a Samba SMB share.
  • Include Linux-specific troubleshooting steps and agent deployment instructions (e.g., deploying the agent on a Linux VM).
  • Mention Linux tools or patterns where relevant (e.g., alternatives to Robocopy for Linux).
  • Ensure parity in example order and detail for both Windows and Linux environments.
  • Clarify any OS-specific requirements or limitations for agent installation and operation.
Storage On-Premises AD DS Authentication for Azure Files ...storage/files/storage-files-identity-ad-ds-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 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 moderate Windows bias. Windows terminology, tools, and references (e.g., Windows ACLs, DACLs, domain joining, and troubleshooting links) are used exclusively or before Linux equivalents. Prerequisites and configuration steps reference Windows-specific guides and tools, with minimal or no Linux-specific instructions or examples. Linux support is mentioned, but practical guidance for Linux users is lacking.
Recommendations
  • Add explicit Linux mounting instructions and examples (e.g., using cifs-utils, mount.cifs, Kerberos setup on Linux).
  • Include links to Linux-specific troubleshooting guides for Azure Files mounting errors.
  • Provide guidance on configuring file-level permissions on Linux clients (e.g., mapping AD DS identities to Linux users/groups, handling ACLs).
  • Mention Linux domain join equivalents (e.g., using realmd, sssd, or samba for AD DS integration).
  • Balance references to Windows and Linux tools, ensuring both platforms are covered in prerequisites and step-by-step instructions.
Storage Best practices for monitoring Azure Queue Storage .../storage/queues/queues-storage-monitoring-scenarios.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides PowerShell and Azure CLI examples for monitoring Azure Queue Storage metrics, listing PowerShell first. While Azure CLI is cross-platform, the PowerShell example is Windows-centric and no explicit Linux/macOS shell examples (e.g., Bash) are given. The code sample for SDK usage is in C#, which is common but not inherently Windows-biased. No Linux-specific tools or workflows are mentioned, and portal screenshots and instructions are platform-neutral.
Recommendations
  • Add Bash or shell script examples for metric queries, especially for Linux/macOS users.
  • List Azure CLI examples before PowerShell, or present them side-by-side to avoid Windows-first bias.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide installation links.
  • Consider adding Python or other cross-platform SDK examples alongside C#.
Storage Manage block blobs with Azure CLI ...zure-docs/blob/main/articles/storage/blobs/blob-cli.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias, primarily through the use of Windows-style file paths (e.g., C:\temp\) in all code examples, and by referencing the creation of files in Windows directories. There are no explicit Linux/macOS examples, nor are Linux-style paths (e.g., /tmp/) shown. The XML example instructs users to create a file in C:\temp, and the Bash scripts use Windows paths for uploads and downloads, which may confuse or inconvenience Linux/macOS users. However, all CLI commands themselves are cross-platform Bash scripts, and no Windows-only tools or PowerShell commands are present.
Recommendations
  • Provide Linux/macOS equivalent examples for file paths (e.g., /tmp/bloblist.xml) alongside Windows paths.
  • Add notes clarifying that users should adjust file paths for their operating system.
  • Where examples reference creating files or directories, include both Windows and Linux/macOS instructions.
  • Consider alternating the order of examples, or defaulting to OS-neutral paths (e.g., ./temp/) where possible.
Storage Best practices for using Azure Data Lake Storage ...cles/storage/blobs/data-lake-storage-best-practices.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy ๐Ÿ”ง Windows Tools
Summary
The documentation page lists Windows-centric tools (PowerShell, Azure Storage Explorer) before cross-platform or Linux-native alternatives, and provides examples and guidance for PowerShell more prominently than for Linux shells. While Azure CLI and REST are mentioned, PowerShell is frequently referenced for tasks like data ingestion, downloading, and monitoring, and is often listed before CLI. There is little explicit mention of Linux/macOS-specific workflows, and no Bash or shell script examples are provided.
Recommendations
  • Ensure Azure CLI examples are provided alongside PowerShell, and list them first or equally.
  • Include Bash/shell script examples for common tasks (e.g., data ingestion, monitoring).
  • Clarify cross-platform compatibility for tools like AzCopy and Azure Storage Explorer.
  • Add explicit guidance for Linux/macOS users, including installation and usage notes for CLI tools.
  • Avoid listing Windows tools (PowerShell, Storage Explorer) before cross-platform alternatives unless contextually justified.
Storage Filter data by using Azure Data Lake Storage query acceleration ...e/blobs/data-lake-storage-query-acceleration-how-to.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy ๐Ÿ”ง Windows Tools Windows First
Summary
The documentation provides PowerShell examples and instructions for every major code sample and setup step, but does not offer equivalent Linux/macOS CLI (e.g., Bash, Azure CLI) examples. PowerShell is a Windows-centric tool, and its use is presented first in each section. There is no mention of Linux-native tools or shell environments, nor guidance for Linux/macOS users to achieve the same tasks.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all setup and query steps.
  • Include Bash shell script examples for Linux/macOS users where appropriate.
  • Clearly indicate cross-platform alternatives for PowerShell commands.
  • Reorder examples so that cross-platform tools (Azure CLI, SDKs) are presented before or alongside PowerShell.
  • Explicitly state platform compatibility for each example.
Storage Container-level WORM policies for immutable blob data ...orage/blobs/immutable-container-level-worm-policies.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy ๐Ÿ”ง Windows Tools Windows First
Summary
The documentation page shows moderate Windows bias. In the 'Deletion' section, PowerShell commands (Remove-AzRmStorageContainer, Remove-AzStorageContainer) are mentioned first and described in detail, with links to their documentation. The Azure CLI command is mentioned after PowerShell, and both are described as alternatives. There is no mention of Linux-specific tools, shell examples, or parity for Linux/macOS users. The focus on PowerShell and Windows-centric tools may create friction for users on non-Windows platforms.
Recommendations
  • Provide explicit examples for Linux/macOS users, such as Bash or shell commands using Azure CLI.
  • List Azure CLI commands before or alongside PowerShell commands to avoid Windows-first ordering.
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS, and provide installation or usage links.
  • Avoid exclusive references to Windows tools; mention platform-neutral alternatives where possible.
  • Consider adding REST API examples or code snippets in Python/JavaScript for broader platform coverage.
Storage Using the HDFS CLI with Azure Data Lake Storage .../blobs/data-lake-storage-use-hdfs-data-lake-storage.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides HDFS CLI usage examples for Azure Data Lake Storage, but in the SSH connection section, it presents sample PowerShell code for establishing SSH connections, which is a Windows-centric approach. There are no explicit Linux/macOS shell examples for SSH, and PowerShell is mentioned before any Unix shell commands, despite the context being an HDInsight Hadoop cluster on Linux.
Recommendations
  • Provide equivalent Linux/macOS shell (bash) examples for SSH connections, e.g., using the standard 'ssh' command in bash/zsh.
  • Avoid presenting PowerShell code as the default or only example in Linux-focused sections.
  • Explicitly mention that the HDFS CLI commands are cross-platform and can be run from any OS with Hadoop installed.
  • Add a note or section clarifying usage from Linux/macOS environments, including any OS-specific prerequisites.
Storage Configure a lifecycle management policy ...storage/blobs/lifecycle-management-policy-configure.md
Medium Priority View Details →
Scanned: 2026-01-12 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 featured as a primary scripting example, with detailed command breakdowns and variable initialization, while the Azure CLI example is brief and lacks equivalent step-by-step guidance. PowerShell is presented before Azure CLI in all code sections, and no Linux-specific shell examples (e.g., Bash) or platform notes are provided. The use of PowerShell-specific cmdlets and terminology may create friction for Linux/macOS users.
Recommendations
  • Provide equally detailed Azure CLI examples, including variable initialization and step-by-step breakdowns.
  • Add explicit Bash/Linux shell examples where applicable, especially for CLI usage.
  • Include platform notes clarifying that Azure CLI works cross-platform and does not require PowerShell.
  • Alternate the order of PowerShell and CLI examples, or present CLI first to avoid implicit Windows-first bias.
  • Mention that PowerShell is available on Linux/macOS, or clarify when examples are Windows-specific.
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy ๐Ÿ”ง Windows Tools Windows First
Summary
The documentation page provides extensive PowerShell examples and references, which are primarily associated with Windows environments. PowerShell is presented as a first-class option alongside Azure CLI and portal, but its usage (including file paths like C:\temp\json.txt) and instructions (such as installing PowerShell modules) are Windows-centric. There are no explicit Linux/macOS shell script examples, and PowerShell examples use Windows-style paths and conventions. While Azure CLI is cross-platform and included, the prominence and detail of PowerShell instructions may create friction for Linux/macOS users.
Recommendations
  • Include Bash or shell script examples for key tasks, especially for downloading and applying JSON policy files.
  • Use platform-neutral file paths (e.g., /tmp/json.txt) in CLI and PowerShell examples, or provide both Windows and Linux/macOS variants.
  • Clarify that PowerShell Core is available cross-platform, and provide installation instructions for Linux/macOS.
  • Where PowerShell is used, add equivalent Bash/CLI commands for Linux/macOS users.
  • Explicitly mention that Azure CLI is cross-platform and recommend it for Linux/macOS users.
Storage Quickstart: Azure Blob Storage library - C++ ...articles/storage/blobs/quickstart-blobs-c-plus-plus.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example ๐Ÿ”ง Windows Tools
Summary
The documentation exhibits a Windows bias by prioritizing Windows-specific tools and workflows, such as Visual Studio and .sln files, and providing detailed instructions and screenshots for Windows environments. Linux instructions are present but less detailed and often appear after Windows examples. The setup and project creation sections focus almost exclusively on Windows, with no equivalent guidance for Linux/macOS IDEs or build systems beyond CMake and vcpkg.
Recommendations
  • Add explicit instructions for creating and building the project on Linux/macOS, including using CMake directly or alternative IDEs (e.g., CLion, VS Code).
  • Provide screenshots or step-by-step guidance for Linux/macOS workflows, such as opening source files and compiling with g++/clang.
  • Ensure environment variable setup instructions for Linux/macOS are as detailed as those for Windows.
  • Mention cross-platform compatibility and highlight any OS-specific caveats or requirements.
  • Present Linux/macOS instructions and examples alongside Windows, not after them.
Storage Limitations & known issues with SFTP in Azure Blob Storage ...ge/blobs/secure-file-transfer-protocol-known-issues.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
๐Ÿ”ง Windows Tools Missing Linux Example
Summary
The documentation page mentions WinSCP, a Windows-centric SFTP client, and provides configuration guidance specific to it. No equivalent Linux/macOS client (such as FileZilla, Nautilus, or command-line sftp/ssh) is referenced, nor are any Linux/macOS-specific instructions or examples provided. This creates a subtle bias towards Windows users, as Linux/macOS administrators may not see guidance relevant to their platforms.
Recommendations
  • Include examples and recommended settings for popular Linux/macOS SFTP clients (e.g., FileZilla, command-line sftp, Cyberduck).
  • Provide configuration guidance for Linux/macOS tools where relevant, especially if there are known issues or settings that affect compatibility.
  • List cross-platform clients first, or group client recommendations by OS.
  • Explicitly state that the guidance applies to all platforms, and note any platform-specific caveats.
Storage Connect to Azure Blob Storage from an SFTP client ...blobs/secure-file-transfer-protocol-support-connect.md
Medium Priority View Details →
Scanned: 2026-01-12 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 Windows bias by providing only a Windows PowerShell example for connecting to Azure Blob Storage via SFTP, referencing Windows-specific tools first, and omitting explicit Linux/macOS command-line examples. While the core SFTP commands are platform-agnostic, the initial connection instructions and context are tailored to Windows users, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit Linux/macOS connection examples, such as using the native 'sftp' command in a Bash terminal.
  • Present platform-neutral instructions first, or provide parallel examples for Windows (PowerShell) and Linux/macOS (Bash).
  • Reference cross-platform SFTP clients and tools, not just Windows OpenSSH.
  • Clarify that the SFTP commands shown are applicable across platforms, and note any platform-specific differences if relevant.
Storage Tutorial - Simulate a failure in reading data from the primary region ...icles/storage/blobs/simulate-primary-region-failure.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
๐Ÿ”ง Windows Tools Windows First
Summary
The documentation presents two methods for simulating a failure: static routing and Fiddler. While the static routing instructions provide both Linux and Windows commands, the Fiddler method is Windows-only, as Fiddler is not natively available for Linux/macOS. Additionally, Fiddler is introduced before any mention of Linux/macOS alternatives, and no cross-platform equivalent tool is suggested for non-Windows users.
Recommendations
  • Provide cross-platform alternatives to Fiddler, such as mitmproxy or similar tools available on Linux/macOS, with equivalent instructions.
  • Explicitly state platform limitations for Fiddler and suggest Linux/macOS users use alternative tools.
  • Ensure parity in tooling recommendations by listing Linux/macOS options alongside Windows tools.
  • Consider reordering sections so that platform-neutral or cross-platform methods are presented first.
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy ๐Ÿ”ง Windows Tools Windows First
Summary
The documentation provides explicit PowerShell instructions for enabling the change feed, including module installation and authentication steps, but does not offer equivalent guidance for Linux/macOS users (e.g., Bash, shell, or cross-platform scripting). Azure CLI is included, which is cross-platform, but PowerShell instructions are more detailed and prominent. Azure portal and Resource Manager template methods are also described, but no Linux-specific tools or patterns are mentioned. Azure Storage Explorer is referenced as a viewing tool, which is available cross-platform, but no Linux-native alternatives are suggested.
Recommendations
  • Add Bash/shell scripting examples for enabling the change feed, especially for authentication and module installation steps.
  • Clarify that Azure CLI commands work on Linux/macOS and provide any necessary environment setup instructions.
  • Mention cross-platform alternatives to PowerShell for scripting and automation (e.g., Bash, Python SDK).
  • Ensure that examples and instructions are presented in a neutral order (e.g., CLI first, then PowerShell) to avoid Windows-first perception.
  • Reference Linux-native tools for blob viewing (e.g., azcopy, SDKs, or third-party FOSS tools) alongside Azure Storage Explorer.
Storage Host a static website in Azure Storage ...es/storage/blobs/storage-blob-static-website-how-to.md
Medium Priority View Details →
Scanned: 2026-01-12 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. PowerShell is featured as a primary automation method, and instructions for using the Azure CLI reference opening Windows PowerShell as a command console. File path examples and instructions often use Windows-style paths (e.g., C:\temp\index.html) without Linux/macOS equivalents. There is no explicit mention of Linux/macOS terminals or shell environments, nor are there examples using Bash or Linux file paths. The PowerShell section assumes a Windows environment and does not discuss cross-platform alternatives.
Recommendations
  • Include explicit instructions and examples for Linux/macOS users, such as using Bash or Terminal instead of PowerShell.
  • Provide file path examples in both Windows (C:\...) and Linux/macOS (/home/user/...) formats.
  • Clarify that Azure CLI can be used from any OS and suggest opening a terminal or command prompt appropriate to the user's platform.
  • Mention cross-platform tools (e.g., AzCopy) and provide usage examples for Linux/macOS.
  • Add notes or tabs for Linux/macOS-specific steps where PowerShell is referenced, or suggest using Azure CLI as a cross-platform alternative.
Storage Static website hosting in Azure Storage .../articles/storage/blobs/storage-blob-static-website.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
๐Ÿ”ง Windows Tools Powershell Heavy Windows First
Summary
The documentation lists Windows-centric tools (Azure PowerShell, Azure Storage Explorer, Visual Studio Code extension) alongside cross-platform options, but does not provide explicit Linux/macOS examples or mention Linux-specific tools. PowerShell is highlighted as a primary method for uploading and managing content, and Windows tools are mentioned before Linux alternatives (e.g., Azure CLI). There is no explicit guidance for Linux/macOS users, nor are there bash or shell script examples.
Recommendations
  • Add explicit Linux/macOS examples for key tasks (e.g., using Azure CLI with bash/zsh, AzCopy on Linux).
  • Clarify which tools are cross-platform and which are Windows-only.
  • Provide step-by-step instructions or screenshots for Linux/macOS environments, especially for command-line operations.
  • List Azure CLI (which is cross-platform) before PowerShell in tool recommendations.
  • Mention Linux-native tools or patterns (e.g., shell scripting, integration with CI/CD on Linux).
Storage How to migrate your classic storage accounts to Azure Resource Manager ...ain/articles/storage/common/classic-account-migrate.md
Medium Priority View Details →
Scanned: 2026-01-12 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 consistently provides PowerShell-based examples and instructions for command-line operations, with no mention of Linux/macOS equivalents such as Azure CLI or Bash scripts. PowerShell is presented as the sole automation option, and Windows-centric tools and installation steps are described in detail. This creates friction for Linux/macOS users, who must seek out alternative methods or adapt PowerShell instructions themselves.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line instructions, especially for identifying, deleting, and migrating storage accounts.
  • Include Bash script snippets where appropriate for Linux/macOS users.
  • Clearly indicate cross-platform options and note which tools are available on all operating systems.
  • Reorder examples so that Azure CLI (cross-platform) is shown before or alongside PowerShell, or use tabs for both.
  • Provide links to Azure CLI installation and usage guides, similar to the PowerShell module installation instructions.
Storage We're retiring classic storage accounts on August 31, 2024 ...s/storage/common/classic-account-migration-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy ๐Ÿ”ง Windows Tools
Summary
The documentation page references PowerShell cmdlets multiple times, including a dedicated FAQ entry about legacy and modern PowerShell usage for managing storage accounts. There is no mention of Linux/macOS CLI tools (such as Azure CLI), Bash, or cross-platform scripting alternatives. The only tooling discussed for management and migration is PowerShell, which is traditionally associated with Windows environments, although it is now available cross-platform. No Linux-specific instructions, examples, or parity notes are provided.
Recommendations
  • Add explicit references and examples for Azure CLI commands for all migration and management operations, ensuring Linux/macOS users have clear guidance.
  • Include Bash scripting examples where relevant, especially for automation tasks.
  • Clarify that PowerShell is available cross-platform, but also provide parity for users who prefer native Linux/macOS tools.
  • Where PowerShell cmdlets are mentioned, provide equivalent Azure CLI commands side-by-side.
  • Add a note or section addressing Linux/macOS users and their migration workflow.
Storage Understand storage account migration from classic to Azure Resource Manager ...es/storage/common/classic-account-migration-process.md
Medium Priority View Details →
Scanned: 2026-01-12 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 migration via the Azure portal, PowerShell, or Azure CLI, but in the 'See also' and 'Validation' sections, PowerShell is mentioned before Azure CLI, and a specific link is provided for PowerShell migration steps before CLI. There are no explicit Linux/macOS-specific instructions or examples, and no mention of Bash or shell scripting. The documentation does not clarify cross-platform CLI usage or provide parity for Linux users in terms of examples or troubleshooting.
Recommendations
  • Ensure that Azure CLI examples are presented before or alongside PowerShell examples, especially in step-by-step migration guides.
  • Include explicit Bash/shell command examples for Linux/macOS users where relevant.
  • Add notes clarifying that Azure CLI is cross-platform and works on Linux/macOS, while PowerShell may require additional setup.
  • Provide troubleshooting steps or links for Linux/macOS environments, not just Windows/PowerShell.
  • Review and balance the order of tool mentions so that Windows-specific tools (PowerShell) do not appear to be the default or primary method.
Storage Enable and manage Azure Storage Analytics logs (classic) ...ticles/storage/common/manage-storage-analytics-logs.md
Medium Priority View Details →
Scanned: 2026-01-12 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 exhibits a notable Windows bias. PowerShell is the only CLI example provided, and instructions explicitly state to 'Open a Windows PowerShell command window.' There are no equivalent Bash, Azure CLI, or Linux/macOS shell examples. File paths and tool usage (e.g., AzCopy example uses Windows-style paths) are Windows-centric. The documentation does not mention or demonstrate how Linux/macOS users can perform these tasks, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, with explicit instructions for Linux/macOS terminals.
  • Provide Bash shell script equivalents for enabling and managing logs.
  • Use platform-neutral file paths in AzCopy examples, or show both Windows and Linux/macOS path formats.
  • Clarify that AzCopy and Azure CLI are cross-platform tools, and provide installation/use instructions for Linux/macOS.
  • Include notes or sections for Linux/macOS users, especially where PowerShell is referenced.
  • Avoid language like 'Open a Windows PowerShell command window'โ€”instead, refer to 'your preferred command-line interface.'