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 1076-1100 of 1657 flagged pages
Storage Container-level WORM policies for immutable blob data ...orage/blobs/immutable-container-level-worm-policies.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 in its examples and tool references. PowerShell commands (Remove-AzRmStorageContainer, Remove-AzStorageContainer) are mentioned first and described in detail, while Linux/macOS equivalents are not explicitly referenced. Although Azure CLI is mentioned, the explanation and ordering favor Windows/PowerShell tools, and there are no Bash or Linux-specific examples or guidance.
Recommendations
  • Add explicit Linux/macOS command-line examples, such as Bash scripts using Azure CLI.
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform parity.
  • Clarify that Azure CLI works on all platforms and provide installation/use instructions for Linux/macOS users.
  • Include notes or sections on using REST API calls directly, which are platform-agnostic.
  • Avoid referencing Windows-only tools (PowerShell) without also mentioning or demonstrating equivalent Linux/macOS workflows.
GitHub Create Pull Request
Storage Configure a lifecycle management policy ...storage/blobs/lifecycle-management-policy-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 First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided in detail, with multiple custom commands and object manipulation, while the Azure CLI example is minimal and lacks equivalent depth. The PowerShell section appears before the Azure CLI section, and the use of PowerShell-specific cmdlets and patterns may be unfamiliar or inaccessible to Linux/macOS users. There is no mention of Linux-specific tools or shell scripting, and the CLI example does not show how to construct the JSON policy file, which is a critical step for non-Windows users.
Recommendations
  • Provide equally detailed Azure CLI examples, including how to construct the JSON policy file using common Linux/macOS tools (e.g., echo, cat, nano, vi).
  • Include bash or shell scripting examples for Linux/macOS users, demonstrating policy creation and management.
  • Present CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Explicitly mention cross-platform compatibility and note that Azure CLI works on Linux/macOS/Windows.
  • Add troubleshooting notes or tips relevant to Linux/macOS environments.
GitHub Create Pull Request
Storage Known issues with NFS 3.0 in Azure Blob Storage ...age/blobs/network-file-system-protocol-known-issues.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions that static website configuration for NFS 3.0 enabled accounts can only be performed using PowerShell or Azure CLI, but does not specify Linux/macOS alternatives or give parity to those platforms. Additionally, the workaround for Windows NFS clients is described before any mention of Linux clients, and the only explicit workaround for Windows is to use WSL2 (a Linux environment on Windows), suggesting a Windows-first perspective.
Recommendations
  • Clarify that Azure CLI is cross-platform and provide explicit Linux/macOS command examples for static website configuration.
  • Include examples or references for mounting NFS shares from native Linux/macOS clients, not just WSL2.
  • Ensure that documentation does not imply PowerShell is the only option, and provide Bash or shell script equivalents where relevant.
  • Reorder sections to present Linux/macOS client support before Windows workarounds, reflecting the native compatibility of NFS with Unix-like systems.
GitHub Create Pull Request
Storage Configure object replication ...articles/storage/blobs/object-replication-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 Windows First
Summary
The documentation provides extensive PowerShell examples for configuring object replication, with file paths and commands that assume a Windows environment (e.g., use of C:\temp\json.txt and PowerShell cmdlets). PowerShell is featured as a primary automation method alongside Azure CLI, but the PowerShell examples use Windows-centric conventions. While Azure CLI examples are present and cross-platform, PowerShell is given equal or greater prominence, and file path examples are Windows-only. There are no explicit Linux/macOS shell examples, and REST API is marked as N/A for most tasks.
Recommendations
  • Add Bash/shell script examples for Linux/macOS users, especially for tasks involving file manipulation (e.g., saving JSON files).
  • Use platform-neutral file paths in examples (e.g., /tmp/json.txt or ./json.txt) or provide both Windows and Linux/macOS variants.
  • Clarify that PowerShell Core is available cross-platform, and provide guidance or examples for Linux/macOS PowerShell usage.
  • Explicitly mention that Azure CLI works on all major platforms and highlight any platform-specific considerations.
  • Where REST API is marked N/A, clarify if there are alternative programmatic approaches for non-Windows environments.
GitHub Create Pull Request
Storage Perform a point-in-time restore on block blob data ...articles/storage/blobs/point-in-time-restore-manage.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents examples for Azure portal, PowerShell, and Azure CLI in parallel tabs, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is described in detail. PowerShell examples are extensive and use Windows-specific patterns (e.g., Get-Date, backticks for line continuation). There are no Linux/macOS shell examples (e.g., Bash), nor is there mention of Linux-specific tools or patterns. The ordering of tabs is portal, PowerShell, then Azure CLI, subtly prioritizing Windows tools over cross-platform CLI usage.
Recommendations
  • Add Bash shell examples alongside Azure CLI, showing typical usage on Linux/macOS.
  • Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Consider reordering tabs to show Azure CLI before PowerShell, or clarify tool parity.
  • Avoid Windows-specific scripting patterns (like PowerShell's Get-Date) in generic examples; show equivalent Bash date handling.
  • Add a note for Linux/macOS users about prerequisites and environment setup for CLI usage.
GitHub Create Pull Request
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by exclusively mentioning WinSCP (a Windows SFTP client) in the client settings section, with no reference to Linux/macOS SFTP clients or their configuration. No Linux or cross-platform client examples or troubleshooting steps are provided, which may cause friction for users on non-Windows platforms.
Recommendations
  • Include configuration guidance for popular Linux/macOS SFTP clients (e.g., OpenSSH's sftp, FileZilla, Cyberduck).
  • Provide troubleshooting tips relevant to Linux/macOS environments.
  • List any client-specific limitations for Linux/macOS tools, similar to the WinSCP guidance.
  • Ensure that examples and recommendations are balanced between Windows and Linux/macOS tools.
GitHub Create Pull Request
Storage Quickstart: Azure Blob Storage library - C++ ...articles/storage/blobs/quickstart-blobs-c-plus-plus.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Project creation instructions and screenshots exclusively reference Visual Studio and Windows console applications, with no mention of Linux or cross-platform alternatives (e.g., CMake, Makefiles, or VS Code). The initial package installation command uses the Windows-specific 'vcpkg.exe', and environment variable setup instructions list Windows first, with Linux as a secondary note. Code snippets reference MSVC-specific logic, and there is no guidance for Linux/macOS users regarding project setup, compilation, or IDE usage.
Recommendations
  • Add explicit instructions for creating and building the project on Linux/macOS, including using CMake or other cross-platform build systems.
  • Include screenshots or guidance for popular cross-platform IDEs (e.g., VS Code, CLion) or command-line workflows.
  • Present environment variable setup instructions for Linux/macOS before or alongside Windows, not after.
  • Replace 'vcpkg.exe' with 'vcpkg' in installation commands and clarify usage on non-Windows platforms.
  • Provide code snippets and setup steps that are compiler-agnostic, or clearly document differences for GCC/Clang vs. MSVC.
GitHub Create Pull Request
Storage Authorize access to Azure Blob Storage for an SFTP client ...secure-file-transfer-protocol-support-authorize-access.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 examples for both PowerShell and Azure CLI, but PowerShell (a Windows-centric tool) is presented before Azure CLI in all code example sections. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell commands are shown with more step-by-step detail. While Azure CLI is cross-platform, the ordering and depth of PowerShell coverage suggest a Windows-first bias.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more universally available across platforms.
  • Add explicit Bash shell examples for Linux/macOS users, especially for tasks like generating SSH keys and scripting Azure CLI commands.
  • Clarify in the prerequisites or introduction that Azure CLI is recommended for Linux/macOS users.
  • Balance the depth of coverage between PowerShell and Azure CLI, ensuring parity in step-by-step instructions.
GitHub Create Pull Request
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. The Fiddler-based failure simulation is Windows-centric, as Fiddler is a Windows-only tool and no Linux/macOS alternatives are mentioned. In command-line examples, both Windows and Linux commands are provided, but Windows commands and tools (like 'ipconfig') are often mentioned first. The tutorial assumes familiarity with Windows patterns, such as 'elevated command prompt', and does not suggest cross-platform equivalents for all steps.
Recommendations
  • Include Linux/macOS alternatives to Fiddler, such as mitmproxy or similar proxy tools, with example scripts.
  • Present command-line instructions in parallel for Windows and Linux/macOS, or group them by platform for clarity.
  • Mention Linux/macOS tools (e.g., 'ifconfig', 'ip', 'route') before or alongside Windows tools, rather than after.
  • Clarify steps that require administrative privileges for both Windows and Linux/macOS users.
  • Add screenshots or instructions for Linux/macOS proxy tools where Fiddler is used for Windows.
GitHub Create Pull Request
Storage Enable and manage soft delete for containers ...articles/storage/blobs/soft-delete-container-enable.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 Missing Linux Example
Summary
The documentation provides detailed PowerShell instructions for enabling and managing container soft delete, which are specific to Windows environments. While Azure CLI instructions are included (which are cross-platform), PowerShell is presented before CLI, and there are no explicit Linux/macOS shell examples (e.g., bash, zsh) or notes on platform-specific differences. The template and portal instructions are platform-neutral, but the lack of Linux/macOS-specific guidance and the prioritization of PowerShell may create friction for non-Windows users.
Recommendations
  • Present Azure CLI instructions before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Include explicit bash/zsh examples for Linux/macOS users where relevant (e.g., showing CLI commands in a Linux terminal context).
  • Add notes clarifying that PowerShell instructions are primarily for Windows, and recommend CLI for Linux/macOS.
  • Ensure parity in troubleshooting and environment setup instructions for Linux/macOS (e.g., how to install Azure CLI on Linux).
GitHub Create Pull Request
Storage Example Azure role assignment conditions for Blob Storage ...n/articles/storage/blobs/storage-auth-abac-examples.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed Azure PowerShell examples for every scenario, including setup and testing, but does not offer equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or cross-platform scripting). All command-line instructions are PowerShell-centric, which is primarily a Windows tool, and there is no mention of Linux-native tools or workflows. This creates friction for non-Windows users who must translate PowerShell scripts to their environment.
Recommendations
  • Add Azure CLI examples for each scenario, showing equivalent commands for role assignment and condition testing.
  • Include Bash or shell script snippets where appropriate, especially for file operations and context setup.
  • Explicitly mention cross-platform alternatives and note any differences in syntax or behavior.
  • Provide guidance on using the Azure portal and REST API for users who prefer not to use PowerShell.
  • Add a section or note clarifying which instructions are platform-agnostic and which are Windows/PowerShell-specific.
GitHub Create Pull Request
Storage Use blob index tags to manage and find data on Azure Blob Storage ...in/articles/storage/blobs/storage-blob-index-how-to.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 consistently references Windows tools and patterns, such as PowerShell and Windows file paths, and often suggests Windows PowerShell as the default local shell for Azure CLI, even though CLI and AzCopy are cross-platform. Examples use Windows-style paths (e.g., C:\demo-file.txt) and mention Windows PowerShell before alternatives. There are no explicit Linux/macOS examples, nor are shell options like Bash or zsh mentioned. This creates friction for Linux/macOS users, though most commands are technically cross-platform.
Recommendations
  • Include Linux/macOS-specific examples, such as using Bash/zsh and Unix-style file paths (e.g., /home/user/demo-file.txt).
  • Replace references to 'Windows PowerShell' with 'your preferred shell' or mention Bash/zsh alongside PowerShell.
  • Add notes clarifying that Azure CLI and AzCopy commands work on Linux/macOS and provide installation links for those platforms.
  • Show example commands with both Windows and Unix-style file paths.
  • Explicitly state cross-platform compatibility for all tools and commands.
GitHub Create Pull Request
Storage Static website hosting in Azure Storage .../articles/storage/blobs/storage-blob-static-website.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation lists Windows-centric tools (PowerShell, Azure Storage Explorer, Visual Studio Code extension) alongside cross-platform options, but Windows tools are mentioned before Linux equivalents (e.g., Azure CLI). PowerShell is given equal prominence to CLI, and there are no explicit Linux/macOS-specific examples or guidance. The ordering and tool selection may create friction for Linux/macOS users, though most tasks can still be completed cross-platform.
Recommendations
  • Explicitly state that Azure CLI and AzCopy are cross-platform and provide example commands for Linux/macOS.
  • Reorder tool lists to mention cross-platform tools (Azure CLI, AzCopy) before Windows-specific ones (PowerShell, Storage Explorer).
  • Add a section or callout for Linux/macOS users, highlighting any differences or considerations (e.g., case sensitivity, CLI installation).
  • Provide example workflows for Linux/macOS environments, such as uploading files via CLI or AzCopy from a bash shell.
  • Clarify which tools are cross-platform and which are Windows-only in the checklist.
GitHub Create Pull Request
Storage Performance tuning for uploads and downloads with Azure Storage client library for .NET ...es/storage/blobs/storage-blobs-tune-upload-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 focuses exclusively on .NET and C# examples, with configuration guidance and code samples tailored to Windows environments (e.g., ServicePointManager, ThreadPool). There is no mention of Linux/macOS-specific considerations, nor are there examples or notes for running the Azure Storage client library in non-Windows environments. Windows-centric APIs and patterns are presented without Linux alternatives or parity.
Recommendations
  • Add notes or examples for running the Azure Storage client library on Linux/macOS, including any differences in networking, threading, or environment configuration.
  • Clarify whether APIs like ServicePointManager and ThreadPool behave identically on Linux and macOS, and provide guidance for those platforms if differences exist.
  • Include cross-platform code samples or highlight platform-agnostic approaches where possible.
  • Explicitly state platform requirements or limitations, if any, for the performance tuning options discussed.
GitHub Create Pull Request
Storage Change feed in Blob Storage ...ain/articles/storage/blobs/storage-blob-change-feed.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 Windows bias primarily in the section on enabling/disabling the change feed. PowerShell instructions are detailed and prominent, including module installation and authentication steps, while Linux/macOS equivalents (such as Bash or Azure CLI) are less emphasized. Azure portal and PowerShell are mentioned before CLI, and there is no mention of Linux-specific tools or shell environments. Azure CLI is provided, but the PowerShell section is more verbose and detailed, which may create friction for Linux/macOS users.
Recommendations
  • Expand Azure CLI instructions to include authentication steps and troubleshooting tips, matching the detail of the PowerShell section.
  • Add explicit Bash or shell examples for Linux/macOS users, including installation and usage notes for Azure CLI.
  • Reorder the enable/disable instructions to present Azure CLI before PowerShell, or present both together as equal options.
  • Mention cross-platform compatibility for Azure CLI and clarify that PowerShell is primarily for Windows users.
  • Include notes or links for Linux/macOS users on how to install and use Azure CLI and Azure Storage Explorer.
GitHub Create Pull Request
Storage Tutorial: Analyze blob inventory reports - Azure Storage ...orage/blobs/storage-blob-inventory-report-analytics.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a bias toward Windows environments by exclusively referencing Power BI Desktop, which is only available for Windows, and providing no alternative instructions or examples for Linux/macOS users. There are no mentions of cross-platform visualization tools or steps for running Power BI on non-Windows systems. Additionally, the instructions for downloading and opening files in Power BI assume a Windows workflow, and Windows tools are referenced before any Linux equivalents (which are absent).
Recommendations
  • Include instructions for visualizing data using cross-platform tools such as Power BI Service (web), Jupyter Notebooks, or open-source alternatives like Apache Superset or Grafana.
  • Explicitly mention that Power BI Desktop is Windows-only and provide guidance for Linux/macOS users, such as using Power BI Service or other visualization options.
  • Add examples or workflows for Linux/macOS users, especially for steps involving file downloads, data analysis, and visualization.
  • Consider providing CLI or browser-based alternatives for steps that currently require Windows-only applications.
GitHub Create Pull Request
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-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 demonstrates a moderate Windows bias. PowerShell is presented as a primary automation option, with explicit instructions to open a Windows PowerShell window and examples using Windows-style paths (e.g., C:\temp\index.html). Windows tools and terminology are referenced before Linux equivalents, and there is no mention of Linux/macOS alternatives for PowerShell commands. CLI instructions reference Windows PowerShell as a console option before mentioning generic consoles. There are no Bash or Linux/macOS-specific examples or notes, and the documentation does not clarify cross-platform compatibility for PowerShell commands.
Recommendations
  • Add explicit Bash/Linux/macOS examples for all CLI commands, including sample paths (e.g., /home/user/index.html).
  • Clarify that Azure CLI and AzCopy are cross-platform and provide instructions for running them on Linux/macOS.
  • Replace 'Open a Windows PowerShell command window' with 'Open a PowerShell command window' and note that PowerShell Core is available on Linux/macOS.
  • Include notes or sections on installing and using PowerShell on Linux/macOS, or link to relevant documentation.
  • Ensure that file path examples are shown for both Windows and Linux/macOS formats.
  • Where possible, avoid referencing Windows tools or terminology first; present cross-platform options equally.
GitHub Create Pull Request
Storage Encrypt and decrypt blobs using Azure Key Vault ...orage/blobs/storage-encrypt-decrypt-blobs-key-vault.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 demonstrates a notable Windows bias. Windows tools (Visual Studio, PowerShell, setx) are mentioned first or exclusively in multiple sections. PowerShell is given as a primary example for package installation and role assignment, with Linux alternatives present but less emphasized. Visual Studio is listed as a required tool, with only a brief mention of Visual Studio Code for Linux/macOS users. Some instructions (e.g., setting environment variables) provide Windows-specific commands first and more detailed guidance for Windows users. There is a lack of parity in example ordering and tool recommendations, and some steps (like project setup) assume a Windows-centric workflow.
Recommendations
  • Provide Linux/macOS examples alongside Windows examples in all sections, and present them with equal prominence.
  • List cross-platform tools (e.g., Visual Studio Code, JetBrains Rider) as alternatives to Visual Studio for project setup.
  • Avoid presenting Windows commands and tools first; alternate the order or present both together.
  • Include Bash and Azure CLI examples wherever PowerShell is used, and clarify which commands work on Linux/macOS.
  • Explicitly state platform requirements and alternatives for each step, especially for environment variable setup and package installation.
GitHub Create Pull Request
Storage Enable and manage blob versioning .../blob/main/articles/storage/blobs/versioning-enable.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 Missing Linux Example
Summary
The documentation provides detailed PowerShell examples alongside Azure CLI and portal instructions, but PowerShell is a Windows-centric tool and is presented as a primary automation method. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell instructions are given before Azure CLI in both main sections. The Azure CLI examples are cross-platform, but the lack of Linux-specific context or examples (such as Bash scripting or notes about CLI usage on Linux/macOS) creates a subtle Windows bias.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, showing usage in Linux/macOS environments.
  • Clarify that Azure CLI is cross-platform and provide notes or links for installing and using it on Linux/macOS.
  • Reorder examples so that Azure CLI (cross-platform) instructions appear before PowerShell (Windows-centric) instructions.
  • Include a brief note that PowerShell Core is available on Linux/macOS, if PowerShell examples are retained.
  • Consider adding a section or callout for Linux/macOS users, highlighting any platform-specific considerations.
GitHub Create Pull Request
Storage Use the Azure Storage resource provider to access management resources ...cles/storage/common/authorization-resource-provider.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation references Windows-centric tools (PowerShell, Azure classic CLI) and lists them before mentioning REST API usage. There are no explicit Linux/macOS command-line examples or references to cross-platform tools like Azure CLI. This creates a subtle bias favoring Windows users and may cause friction for Linux/macOS users seeking parity.
Recommendations
  • Add explicit examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • When listing management tools, mention Azure CLI first or alongside PowerShell and classic CLI.
  • Provide code snippets or walkthroughs for role assignment and resource management using Azure CLI.
  • Clarify which tools are cross-platform and which are Windows-only, to guide users appropriately.
GitHub Create Pull Request
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation mentions PowerShell cmdlets multiple times, including legacy and modern Azure PowerShell, as the primary example for managing storage accounts before and after migration. There is no mention of Linux/macOS equivalents such as Azure CLI, Bash, or REST API usage for these operations. The focus on PowerShell and lack of cross-platform tooling examples may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for all management operations, including migration, deletion, and configuration updates.
  • Explicitly mention that Azure CLI and REST API can be used from any platform (Linux, macOS, Windows) and provide links or examples.
  • Where PowerShell is referenced, add parallel instructions for Bash/CLI usage.
  • Clarify that all migration steps can be performed using cross-platform tools, not just PowerShell.
GitHub Create Pull Request
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides detailed PowerShell instructions for all migration steps but omits equivalent Azure CLI or Bash examples, which are preferred by many Linux/macOS users. PowerShell is presented as the sole scripting option, and Windows-centric tools and installation steps are described in detail. No Linux-specific guidance or parity is offered, and PowerShell examples are shown before mentioning Azure CLI as an alternative, which is only referenced in passing.
Recommendations
  • Add Azure CLI examples for each migration step alongside PowerShell, including commands for identifying, preparing, validating, aborting, and committing migrations.
  • Include Bash scripting examples where appropriate, or clarify cross-platform usage for Azure CLI.
  • Explicitly mention that Azure CLI is available on Linux/macOS and provide installation instructions or links.
  • Reorder examples so that Azure CLI and PowerShell are presented with equal prominence, or allow users to select their preferred platform first.
  • Add troubleshooting notes relevant to Linux/macOS environments, such as permission issues or CLI differences.
GitHub Create Pull Request
Storage Use geo-redundancy to design highly available applications ...b/main/articles/storage/common/geo-redundant-design.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. The only tool mentioned for testing retryable errors is Fiddler, which is Windows-only. No Linux/macOS alternatives (such as mitmproxy or curl) are suggested. All code and scripting examples are platform-neutral (C#), but the testing section lacks Linux/macOS parity.
Recommendations
  • Mention and provide examples for Linux/macOS-compatible tools (e.g., mitmproxy, curl, iptables) for simulating retryable errors.
  • Add a note clarifying that Fiddler is Windows-only and suggest cross-platform alternatives.
  • Include example scripts or command lines for Linux/macOS users to achieve the same testing outcomes.
  • Review future documentation to ensure parity in tool recommendations and examples for all major platforms.
GitHub Create Pull Request
Storage GPv1 ZRS standard account retirement FAQ ...-zone-redundant-storage-migration-freq-asked-questions.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation references PowerShell and Azure CLI as upgrade tools, but consistently mentions PowerShell first and does not provide explicit Linux/macOS command examples or guidance. The upgrade process is described as available via the Azure portal, CLI, or PowerShell, but PowerShell is highlighted in troubleshooting scenarios and is mentioned before CLI. There is no mention of Bash, shell, or Linux-specific patterns, and no example commands for Linux/macOS users.
Recommendations
  • Provide explicit Linux/macOS command examples using Azure CLI (az) and Bash.
  • When listing upgrade tools, mention Azure CLI before PowerShell or present both equally.
  • Clarify that Azure CLI is cross-platform and provide installation/use instructions for Linux/macOS.
  • Add troubleshooting steps or notes relevant to Linux/macOS users, not just PowerShell.
  • Include links to Azure CLI documentation for Linux/macOS.
GitHub Create Pull Request
Storage Enable and manage Azure Storage Analytics logs (classic) ...ticles/storage/common/manage-storage-analytics-logs.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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the only command-line scripting example provided, and it explicitly instructs users to open a 'Windows PowerShell command window'. There are no equivalent CLI or shell examples for Linux/macOS users (e.g., Azure CLI, Bash). The AzCopy example uses a Windows-style path ('C:\Logs\Storage') and does not show a Linux/macOS alternative. Windows tools and patterns (PowerShell, Windows paths) are mentioned exclusively or before any cross-platform options.
Recommendations
  • Add Azure CLI examples for all PowerShell command sections, showing how to enable and manage Storage Analytics logs via az storage commands.
  • Replace or supplement Windows-style file paths in AzCopy examples with Linux/macOS equivalents (e.g., '/home/user/Logs/Storage').
  • Clarify that AzCopy and Azure CLI are cross-platform and provide explicit instructions for Linux/macOS users.
  • Where PowerShell is referenced, note that Azure PowerShell can be run on Linux/macOS, or provide Bash/CLI alternatives.
  • Consider reordering examples so that cross-platform solutions (Azure CLI, REST API) are presented before or alongside Windows-specific tools.
GitHub Create Pull Request
← Previous Page 44 of 67 Next →