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 626-650 of 1657 flagged pages
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-nodejs.md ...icles/storage/blobs/storage-quickstart-blobs-nodejs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits mild Windows bias by listing Windows consoles (cmd, PowerShell) before Bash when describing how to open a console window, and by providing PowerShell and Windows-specific environment variable instructions before Linux equivalents. Visual Studio Code is referenced as the default editor, which is cross-platform but often associated with Windows. PowerShell authentication instructions are included alongside Azure CLI and VS Code, but Linux shell instructions are less emphasized. No Linux-specific tools or editors are suggested, and the overall flow assumes familiarity with Windows development environments.
Recommendations
  • List Bash (Linux/macOS) consoles before or alongside Windows consoles (cmd, PowerShell) when describing terminal usage.
  • Provide Linux/macOS instructions and examples in parallel with Windows instructions, not as secondary notes.
  • Include Linux/macOS-specific editor suggestions (e.g., Vim, Nano, or cross-platform alternatives) alongside Visual Studio Code.
  • When showing environment variable setup, present Linux/macOS and Windows instructions together, or default to platform-agnostic .env file usage.
  • Add explicit notes about cross-platform compatibility and highlight any differences in setup or usage between Windows and Linux/macOS.
  • Consider including screenshots or terminal output from Linux/macOS environments, not just Windows.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/upgrade-to-data-lake-storage-gen2-how-to.md ...rage/blobs/upgrade-to-data-lake-storage-gen2-how-to.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting PowerShell instructions before Azure CLI, referencing Windows PowerShell as the default shell for command-line examples, and mentioning Windows-specific tools and patterns (e.g., 'Open a Windows PowerShell command window'). Linux equivalents (such as Bash) are not explicitly mentioned, and the CLI section suggests using PowerShell as the local shell even for Azure CLI commands. There are no Bash-specific instructions or examples, and the documentation does not address Linux users directly.
Recommendations
  • Add explicit Bash/Linux shell instructions and examples alongside PowerShell, especially for Azure CLI usage.
  • When referencing command-line usage, mention both Windows PowerShell and Bash/Terminal for cross-platform parity.
  • Avoid phrases like 'Open a Windows PowerShell command window' as the default; instead, use 'Open your preferred command-line shell (PowerShell, Command Prompt, or Bash/Terminal)'.
  • Ensure that all CLI commands are shown in a way that works on both Windows and Linux/macOS, and note any platform-specific differences.
  • Include troubleshooting or validation steps that are relevant for Linux environments (e.g., file path conventions, permissions).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blobs-tune-upload-download.md ...es/storage/blobs/storage-blobs-tune-upload-download.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation focuses exclusively on .NET and provides examples and guidance that are tailored to Windows environments. It references Windows-specific APIs (e.g., ServicePointManager, ThreadPool) and does not mention or provide examples for Linux environments, such as configuring .NET Core on Linux, using Linux shell commands, or addressing Linux-specific performance considerations. The lack of Linux-specific guidance and examples may make it harder for Linux developers to apply the recommendations.
Recommendations
  • Include examples and guidance for configuring .NET applications on Linux, such as adjusting connection limits and thread pool settings in Linux environments.
  • Mention any differences in behavior or performance tuning when running .NET on Linux versus Windows, especially regarding networking and threading.
  • Provide Linux shell or bash equivalents for any Windows-specific instructions, where applicable.
  • Clarify whether the recommendations (e.g., ServicePointManager.DefaultConnectionLimit) apply to .NET Core/.NET 5+ on Linux, and if not, provide Linux-appropriate alternatives.
  • Add notes or sections addressing common Linux deployment scenarios (e.g., running in containers, using systemd, file system differences) that may impact performance tuning.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/customer-managed-keys-configure-cross-tenant-existing-account.md ...r-managed-keys-configure-cross-tenant-existing-account.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for configuring cross-tenant customer-managed keys using the Azure portal, PowerShell, and Azure CLI. The PowerShell example is presented before the Azure CLI example, and there are no explicit Linux shell (bash) examples or notes about cross-platform usage for CLI commands. The PowerShell section assumes familiarity with Windows tooling, and there is no mention of Linux-specific considerations or alternative scripting environments.
Recommendations
  • Add explicit bash/Linux shell examples for Azure CLI commands, including environment variable usage and command syntax.
  • Mention cross-platform compatibility for Azure CLI, clarifying that CLI commands work on Linux, macOS, and Windows.
  • Consider providing examples using bash scripts or referencing Linux environments where appropriate.
  • Reorder examples so that Azure CLI (which is cross-platform) appears before PowerShell, or present both in parallel.
  • Add a note clarifying that PowerShell Core is available on Linux and macOS, if PowerShell examples are retained.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/classic-account-migrate.md ...ain/articles/storage/common/classic-account-migrate.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by providing only PowerShell examples for command-line operations, referencing Windows-centric tools (PowerShell, Service Management module), and omitting equivalent Linux/Unix shell (Bash/Azure CLI) instructions. The PowerShell examples are presented as the sole scripting option, with no parity for Linux users. Azure CLI is mentioned only in passing, with no concrete examples or migration steps shown using it.
Recommendations
  • Add step-by-step Azure CLI examples for all migration operations (listing classic accounts, deleting disk artifacts, migrating accounts, aborting/committing migration).
  • Present Azure CLI instructions alongside PowerShell, not only as a reference link.
  • Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and provide guidance for Linux users.
  • Where PowerShell modules are referenced, include equivalent Azure CLI commands and installation instructions.
  • Ensure screenshots and UI references do not assume a Windows environment (e.g., avoid PowerShell-specific UI elements).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/upgrade-to-data-lake-storage-gen2.md ...les/storage/blobs/upgrade-to-data-lake-storage-gen2.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. It references Windows-centric tools (AzCopy, PowerShell), and mentions PowerShell and Azure CLI commands for management, but does not provide Linux-specific examples or mention Linux-native tools. The WASB driver is called 'Windows Azure Storage Blob driver' and is referenced before the ABFS driver, which is more cross-platform. There are no explicit Linux command-line or scripting examples, and Windows tools are mentioned first or exclusively in several places.
Recommendations
  • Include Linux-specific examples and tools, such as Bash scripts or Linux command-line usage for Azure CLI.
  • Mention cross-platform capabilities of AzCopy and Azure CLI, and provide usage examples for both Windows and Linux environments.
  • Reference the ABFS driver as the default for Hadoop workloads, and clarify its cross-platform nature.
  • Add explicit guidance or examples for Linux users, such as file permission management or integration with Linux-based analytics tools.
  • Ensure that documentation for SDKs, CLI, and PowerShell is presented in a platform-neutral order, or with parallel examples for Windows and Linux.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/includes/azure-storage.md ...main/articles/storage/common/includes/azure-storage.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) is standard, but there are no explicit Linux shell (bash/zsh) or scripting examples, nor any mention of Linux-specific tools or usage patterns. The ordering of examples consistently places Azure CLI before PowerShell, which is positive for Linux parity, but the lack of Linux shell script examples or references to Linux environments (such as piping CLI output to jq, or running in bash) means Linux users may not see their workflows represented.
Recommendations
  • Add explicit bash/zsh shell script examples using Azure CLI, demonstrating usage in Linux environments.
  • Include notes or examples showing how to process Azure CLI output with Linux tools (e.g., jq, grep, awk) for further filtering or automation.
  • Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, while Azure PowerShell is primarily Windows-focused.
  • Consider adding a 'Linux' or 'macOS' tab for examples, or at least a section on running queries in Linux environments.
  • Where PowerShell is referenced, clarify its cross-platform availability, but also provide parity for Linux-native scripting.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/general-purpose-version-1-zone-redundant-storage-upgrade-process.md ...rpose-version-1-zone-redundant-storage-upgrade-process.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides upgrade instructions using the Azure Portal, PowerShell, and Azure CLI. PowerShell is highlighted as a primary command-line method, which is Windows-centric, and is presented before Azure CLI. There are no explicit Linux shell/bash examples, nor is there mention of Linux-specific tooling or usage patterns. The CLI example is generic, but the lack of bash/shell context and omission of Linux-specific notes or troubleshooting constitutes a subtle Windows bias.
Recommendations
  • Add explicit bash/shell examples for Azure CLI, including usage in Linux/macOS terminals.
  • Mention that Azure CLI is cross-platform and provide installation or usage notes for Linux users.
  • Consider including Linux-specific troubleshooting tips or notes where relevant.
  • Present Azure CLI examples before PowerShell, or side-by-side, to avoid Windows-first ordering.
  • Reference Linux tools (e.g., curl, jq) if relevant for scripting or automation.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/general-purpose-v-1-zone-redundant-storage-migration-freq-asked-questions.md ...-zone-redundant-storage-migration-freq-asked-questions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation frequently mentions PowerShell and the Azure portal as upgrade methods, with Azure CLI listed alongside but not emphasized. There are no explicit Linux-specific examples or references to Bash/Shell scripting, and the order of tool presentation often places PowerShell or portal before CLI. No Linux tools or patterns are described, and no example commands are provided for either platform.
Recommendations
  • Provide explicit upgrade examples using Azure CLI (with Bash syntax) and PowerShell, ensuring both are shown in parallel.
  • When listing upgrade methods, alternate or randomize the order of PowerShell and CLI, or explicitly state that both Windows and Linux users are supported.
  • Add a section or callout for Linux users, clarifying that Azure CLI is fully supported on Linux/macOS and providing sample commands.
  • Avoid implying that PowerShell is the primary or preferred method; clarify that CLI is cross-platform.
  • Include troubleshooting steps or tips relevant to Linux environments (e.g., shell differences, authentication methods).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-disaster-recovery-guidance.md ...s/storage/common/storage-disaster-recovery-guidance.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias in its tooling recommendations and example references. When discussing manual data copy as a failover alternative and high availability best practices, it mentions AzCopy and Azure PowerShell as the primary tools, with no mention of Linux-native equivalents or CLI usage. Azure PowerShell is a Windows-centric tool, and AzCopy, while cross-platform, is often associated with Windows workflows. The documentation does not provide explicit Linux or Azure CLI examples, nor does it mention Linux-specific considerations for disaster recovery operations.
Recommendations
  • Include Azure CLI examples alongside or before Azure PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly state that AzCopy is available for Linux and macOS, and provide installation and usage instructions for those platforms.
  • Reference Linux shell scripting or automation patterns for disaster recovery operations, such as using Bash scripts with Azure CLI.
  • Mention Linux-specific considerations for VM failover and disk management, such as handling ext4/xfs filesystems or leveraging Linux backup tools.
  • Ensure that all tooling recommendations are presented in a platform-neutral order, or alternate between Windows and Linux tools to avoid implicit prioritization.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/infrastructure-encryption-enable.md ...les/storage/common/infrastructure-encryption-enable.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and referencing PowerShell modules before Azure CLI examples. PowerShell, a Windows-native tool, is featured prominently, and installation instructions for Azure PowerShell are included. There are no examples using Linux-native tools (such as Bash scripts or REST API via curl), nor is there any mention of Linux-specific workflows or considerations. The Azure CLI section is present, but PowerShell is listed before it, and both are presented as tabs, with PowerShell as the first code example after the portal instructions.
Recommendations
  • Add explicit Bash/Linux shell examples using Azure CLI, showing command execution in a Linux environment.
  • Include REST API examples using curl to demonstrate platform-agnostic automation.
  • Reorder code tabs so that Azure CLI (cross-platform) appears before PowerShell, or randomize tab order.
  • Mention that Azure CLI is available natively on Linux and macOS, and provide installation instructions for those platforms.
  • Where possible, avoid referencing Windows-specific tools (such as PowerShell) as the primary automation method.
  • Add notes or sections highlighting Linux and macOS compatibility for all procedures.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/shared-key-authorization-prevent.md ...les/storage/common/shared-key-authorization-prevent.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Windows-centric tools and workflows first or exclusively, such as the Azure portal, PowerShell, and Resource Graph Explorer. PowerShell is given a dedicated example, and references to Storage Explorer and AzCopy link to Windows-specific instructions. There is a lack of explicit Linux or cross-platform alternatives, especially in example commands and tool usage, and the Azure portal (a browser-based tool often associated with Windows environments) is repeatedly emphasized. No Linux shell or scripting examples (e.g., Bash) are provided, and there is no mention of Linux-specific nuances or parity for tools like Storage Explorer or AzCopy.
Recommendations
  • Include explicit Linux/Bash examples alongside PowerShell, especially for CLI commands and scripting.
  • Clarify cross-platform availability for tools such as AzCopy and Storage Explorer, and provide links or instructions for Linux/macOS usage.
  • When listing tools or workflows, avoid presenting Windows-centric options first; instead, use a neutral or platform-agnostic order.
  • Add notes or sections on Linux-specific considerations, such as file paths, authentication methods, and installation instructions for CLI tools.
  • Where screenshots or instructions reference the Azure portal, clarify that it is browser-based and accessible from any OS.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-initiate-account-failover.md ...es/storage/common/storage-initiate-account-failover.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently with detailed installation and usage instructions, including troubleshooting for older PowerShell versions and module management. Windows-specific tooling (PowerShell) is discussed in greater depth than the Azure CLI, with more step-by-step guidance and troubleshooting. PowerShell is listed before Azure CLI in most sections, and there are no explicit Linux shell (bash) or cross-platform scripting examples. The CLI section is less detailed and does not address platform-specific nuances (e.g., Linux package managers, shell environments).
Recommendations
  • Add explicit Linux/bash examples for Azure CLI commands, including instructions for common Linux distributions (e.g., Ubuntu, CentOS) and macOS.
  • Include troubleshooting steps for Azure CLI installation on Linux and macOS, similar to the PowerShell troubleshooting provided for Windows.
  • Balance the depth of guidance between PowerShell and Azure CLI, ensuring CLI instructions are as detailed as PowerShell, including module/extension management and environment setup.
  • Mention cross-platform compatibility for both PowerShell (via PowerShell Core) and Azure CLI, and provide links or notes for users on non-Windows systems.
  • Consider adding a table or section comparing PowerShell and Azure CLI usage across platforms, highlighting any differences or caveats for Linux/macOS users.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-account-get-info.md ...in/articles/storage/common/storage-account-get-info.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation consistently presents PowerShell examples and references before Azure CLI, and relies heavily on PowerShell commands and modules (Az.Storage), which are most commonly used on Windows. There is no mention of Linux-specific tools, shell environments, or alternative scripting approaches, and no explicit Bash or Linux shell examples. The documentation assumes familiarity with PowerShell, which may disadvantage Linux users.
Recommendations
  • Add Bash-specific examples for Azure CLI commands, including common Linux shell usage patterns (e.g., piping, jq for JSON parsing).
  • Explicitly mention that Azure CLI is cross-platform and provide examples of running commands in Bash or other Linux shells.
  • Where PowerShell is referenced, clarify that PowerShell Core is available on Linux, or provide equivalent Bash alternatives.
  • Include notes or sections for Linux users, highlighting any differences in environment setup, authentication, or command syntax.
  • Avoid presenting PowerShell examples before Azure CLI or alternate Linux-friendly tools; consider alternating or leading with CLI/Bash examples.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/lock-account-resource.md .../main/articles/storage/common/lock-account-resource.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell instructions before Azure CLI, referencing the Az PowerShell module, and providing detailed PowerShell examples. The PowerShell section is given prominence and detail, while Linux-native tools or shell examples are not mentioned. Although Azure CLI is cross-platform, there is no explicit mention of Linux environments, nor are there bash or shell-specific notes or examples. The portal instructions are platform-neutral, but the command-line guidance leans toward Windows/PowerShell.
Recommendations
  • Add explicit Linux/bash shell examples alongside Azure CLI commands, including notes about running CLI commands in Linux environments.
  • Present Azure CLI instructions before PowerShell, or clarify that CLI is cross-platform and suitable for Linux/macOS users.
  • Include references to running Azure CLI in native Linux terminals, and mention installation steps for Linux users if relevant.
  • Avoid exclusive mention of Windows tools (e.g., Az PowerShell module) without Linux equivalents or alternatives.
  • Consider adding a 'Linux' or 'macOS' tab for command-line instructions to ensure parity and clarity for non-Windows users.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-account-upgrade.md ...ain/articles/storage/common/storage-account-upgrade.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a primary upgrade method, providing detailed PowerShell instructions and commands, and referencing Windows-centric tools (PowerShell) before Linux equivalents. The PowerShell section is more prominent than the Azure CLI section, and there is no mention of Bash, Linux shell, or cross-platform scripting alternatives. Installation instructions for PowerShell are included, while Linux-specific instructions or examples are missing.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI usage, including installation and usage on Linux/macOS.
  • Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more widely used on Linux/macOS.
  • Include notes or links for Linux/macOS users on how to install and use Azure CLI and relevant tools.
  • Balance the documentation by providing parity in detail and troubleshooting steps for both PowerShell and CLI methods.
  • Consider referencing automation via ARM templates or REST API, which are platform-neutral.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/redundancy-migration.md ...b/main/articles/storage/common/redundancy-migration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents Windows-centric tools and patterns first, notably PowerShell, and provides detailed PowerShell scripts and usage examples. The Azure portal (a GUI, often used on Windows) is also emphasized. While Azure CLI examples are present and generally cross-platform, there is a clear tendency to list PowerShell before CLI, and scripting examples are more elaborate for PowerShell. There are no Linux-specific shell examples (e.g., Bash scripts), nor is there mention of Linux-native tools or patterns beyond the CLI. No explicit Linux bias or parity is shown.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI first to better support Linux users.
  • Provide equivalent Bash scripting examples for batch operations, especially where PowerShell scripts are shown.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide guidance for Linux users where appropriate.
  • Reference Linux-native tools (e.g., shell scripting, cron for automation) where relevant, especially in manual migration scenarios.
  • Ensure screenshots and GUI instructions are not Windows-specific (e.g., avoid showing Windows-only UI elements or file paths).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-account-create.md ...main/articles/storage/common/storage-account-create.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. PowerShell (a Windows-centric tool) is consistently presented as a primary method for scripting and automation, with detailed examples and instructions. In sections covering Bicep and ARM templates, PowerShell is mentioned before Azure CLI, and PowerShell scripts are provided first. The use of PowerShell is emphasized for tasks such as deploying templates and deleting resources, and installation instructions for the Azure PowerShell module are detailed. While Azure CLI (cross-platform) is also covered thoroughly, the ordering and prominence of PowerShell and Windows tools suggest a preference for Windows environments. There are no explicit Linux-only examples, and Linux-specific tooling or patterns (e.g., bash scripting, environment variables, package managers) are not highlighted.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples so that CLI (cross-platform) is sometimes presented first.
  • Explicitly mention that Azure CLI commands work natively on Linux and macOS, and provide installation instructions for these platforms.
  • Include Linux-specific notes, such as using bash scripts, environment variables, or package managers (apt, yum) for installing Azure CLI.
  • Where PowerShell scripts are shown, also provide equivalent bash scripts for Linux users, especially in Bicep and ARM template deployment sections.
  • Highlight that Azure Cloud Shell defaults to Bash and is accessible from any OS, not just Windows.
  • Add troubleshooting or usage tips for Linux users, such as file permissions, shell differences, or common issues encountered on non-Windows systems.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-encryption-key-model-get.md ...les/storage/common/storage-encryption-key-model-get.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for the Azure portal (web UI), PowerShell, and Azure CLI. PowerShell is highlighted as a primary scripting method, which is Windows-centric. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or patterns. The CLI example is generic, but the PowerShell example is given before the CLI, suggesting a Windows-first approach. There is no mention of cross-platform scripting or how to perform the same operation in a Linux shell environment.
Recommendations
  • Add explicit bash shell examples for Azure CLI usage, showing how Linux users can check the encryption key model.
  • Mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Consider providing examples in both PowerShell and bash side-by-side, or clarify which environments each example targets.
  • Avoid presenting PowerShell before CLI unless there is a clear reason; consider leading with CLI for broader cross-platform relevance.
  • Reference Linux and macOS environments where appropriate, and note any differences in command usage or output.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/multiple-identity-scenarios.md ...articles/storage/common/multiple-identity-scenarios.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily in its use of Windows-centric terminology, tools, and patterns. The instructions for enabling managed identities and assigning roles are exclusively shown using the Azure Portal UI, which is most commonly used on Windows. There is no mention of Linux-specific tools or command-line alternatives (such as Azure CLI or PowerShell scripts) for these administrative steps. Additionally, local development guidance references Visual Studio and Azure CLI, but does not provide parity for Linux development environments (e.g., VS Code, Bash). There are no explicit Linux shell or cross-platform command-line examples for identity or role assignment, and the documentation does not mention Linux-specific considerations for environment variables, authentication, or package management.
Recommendations
  • Add Azure CLI and/or PowerShell command examples for enabling managed identities and assigning roles, with explicit notes on cross-platform compatibility.
  • Include instructions for performing identity and role assignment tasks using command-line tools on both Windows and Linux.
  • Reference cross-platform development tools (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
  • Clarify environment variable usage and setup for Linux shells (Bash, Zsh) as well as Windows (CMD, PowerShell).
  • Explicitly mention that all code samples are cross-platform and provide notes or links for Linux-specific setup where relevant.
  • Add troubleshooting notes for common Linux authentication issues (e.g., Azure CLI login, permissions, package installation).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-analytics-logging.md ...n/articles/storage/common/storage-analytics-logging.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. PowerShell is the only scripting example provided for blob filtering, with no equivalent Bash, Azure CLI, or Linux shell example. References to client tools in log entries (e.g., 'win32', 'Windows_NT') and specific mention of PowerShell for metadata access reinforce a Windows-centric approach. Windows tools and patterns are mentioned before or instead of Linux alternatives, and there is a lack of explicit Linux or cross-platform guidance/examples.
Recommendations
  • Provide equivalent Azure CLI and Bash examples alongside PowerShell snippets for blob filtering and metadata access.
  • Mention cross-platform tools (e.g., Azure CLI, azcopy, Storage Explorer for macOS/Linux) explicitly and equally.
  • Include sample log entries generated from Linux/macOS clients to balance the examples.
  • Rephrase instructions to avoid implying PowerShell/Windows is the default or preferred environment.
  • Add guidance for Linux users on accessing and managing logs, including common shell commands and tools.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-migration-tools.md ...ain/articles/storage/common/storage-migration-tools.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows-centric tools and scenarios (such as Azure File Sync for Windows file servers) are described in detail and introduced before Linux/NFS equivalents. Windows protocols and tools (SMB, PowerShell, Robocopy) are mentioned more prominently and earlier than Linux alternatives (NFS, Rsync, DistCP), and examples or guidance for Linux environments are less detailed or absent. The documentation also highlights Windows-specific features (NTFS permissions, Windows Server protocols) without equivalent coverage for Linux file systems or migration patterns.
Recommendations
  • Provide equal detail and step-by-step examples for Linux/NFS migration scenarios, including guidance for common Linux file servers and file systems.
  • Include Linux command-line examples (e.g., Rsync, DistCP) alongside Windows/PowerShell examples, and clarify their usage for Azure migration.
  • Mention Linux tools and protocols (NFS, Rsync, etc.) before or alongside Windows equivalents in each relevant section.
  • Expand coverage of metadata and permissions preservation for Linux file systems (e.g., POSIX ACLs) to match the detail given for NTFS.
  • Add explicit recommendations and best practices for Linux-based environments, including troubleshooting and performance considerations.
  • Ensure graphical and programmatic tool sections mention Linux compatibility and provide Linux-specific instructions where appropriate.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/security-restrict-copy-operations.md ...es/storage/common/security-restrict-copy-operations.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples and instructions before Azure CLI, and omitting any explicit Linux or Bash shell examples. The PowerShell module is referenced directly, and there is no mention of Linux-specific tools or workflows. While Azure CLI is cross-platform, the lack of Bash or Linux shell examples and the ordering of PowerShell before CLI suggest a preference for Windows environments.
Recommendations
  • Add explicit Bash/Linux shell examples for configuring AllowedCopyScope using Azure CLI, including sample commands and environment notes.
  • Reorder the example tabs so that Azure CLI (cross-platform) appears before PowerShell, or present both equally.
  • Mention that Azure CLI commands work on Linux, macOS, and Windows, and provide installation instructions for Linux.
  • Include references to Linux-native tools (e.g., curl, jq) for interacting with Azure REST APIs, if relevant.
  • Avoid language that implies PowerShell is the primary or preferred method, and clarify parity between platforms.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-network-security-ip-address-range.md ...ge/common/storage-network-security-ip-address-range.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed PowerShell examples for managing Azure Storage IP 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 references to installing Azure PowerShell indicate a Windows-centric approach, with less emphasis on Linux-native workflows.
Recommendations
  • Add Bash and Linux shell examples where appropriate, especially for scripting tasks.
  • Include guidance on using Azure CLI from Linux/macOS terminals, clarifying cross-platform usage.
  • Consider presenting Azure CLI examples before PowerShell, as CLI is natively cross-platform.
  • Mention that Azure CLI can be used on Windows, Linux, and macOS, and provide installation instructions for each.
  • If PowerShell is included, clarify that PowerShell Core is available on Linux/macOS and provide relevant instructions.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-network-security-virtual-networks.md ...ge/common/storage-network-security-virtual-networks.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides detailed instructions for creating Azure Storage virtual network rules using the Azure Portal, PowerShell, and Azure CLI. The PowerShell section is prominent and detailed, reflecting a Windows-centric approach. PowerShell examples and terminology appear before Azure CLI (which is more cross-platform), and there is no mention of Linux-specific shell usage or considerations. The documentation assumes familiarity with PowerShell and Windows tools, potentially disadvantaging Linux users.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide shell-specific notes where relevant (e.g., bash syntax for variable assignment).
  • Add examples using bash/zsh for Azure CLI commands, including variable assignment and command chaining.
  • Clarify that PowerShell is primarily a Windows tool, but also available cross-platform, and provide links to installation instructions for Linux/macOS.
  • Consider reordering sections so that Azure CLI (cross-platform) appears before PowerShell, or present both approaches in parallel.
  • Add troubleshooting notes or tips for Linux users (e.g., file permissions, environment setup) where relevant.
GitHub Create Pull Request
← Previous Page 26 of 67 Next →