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 451-475 of 1657 flagged pages
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/authorization-resource-provider.md ...cles/storage/common/authorization-resource-provider.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by listing Windows-centric tools (PowerShell, Azure classic CLI) before mentioning REST API, and omitting explicit Linux or cross-platform CLI examples. The code samples section does not reference command-line usage, and the instructions for assigning roles mention PowerShell and the Azure classic CLI (both Windows-focused) before REST API, with no mention of the cross-platform Azure CLI. There are no Linux-specific or cross-platform shell examples, and the documentation implicitly prioritizes Windows tools and patterns.
Recommendations
  • Add explicit instructions and examples for using the cross-platform Azure CLI (az), which is widely used on Linux and macOS.
  • Include bash or shell script examples alongside PowerShell, especially for common management tasks.
  • Reorder tool mentions to list cross-platform options (Azure CLI, REST API) before Windows-specific tools (PowerShell, classic CLI).
  • Clarify that all management operations can be performed from Linux, macOS, and Windows, and provide parity in examples.
  • Add a section or note highlighting cross-platform support and linking to installation guides for Azure CLI on Linux/macOS.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/classic-account-migration-overview.md ...s/storage/common/classic-account-migration-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. It references PowerShell cmdlets multiple times, including legacy and modern versions, and discusses their support status. There is no mention of Linux-specific tools or command-line interfaces (such as Azure CLI, Bash, or scripting examples for Linux/macOS). The migration and management instructions implicitly assume the use of PowerShell, which is traditionally a Windows-centric tool, and do not provide parity for Linux users. Additionally, the support instructions and examples do not mention Linux workflows or alternatives.
Recommendations
  • Add Azure CLI examples for migration and management tasks alongside PowerShell instructions.
  • Explicitly mention that Azure CLI and REST API can be used from Linux/macOS for all management operations.
  • Include Bash scripting examples for common migration and management scenarios.
  • Clarify that all steps can be performed from Linux, macOS, or Windows, and provide links to cross-platform tool documentation.
  • Avoid referencing only PowerShell cmdlets when discussing supported/unsupported tooling; mention Azure CLI and other cross-platform options.
GitHub Create Pull Request
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias. Windows-specific tools (cmd, PowerShell, Visual Studio Code) are mentioned before or alongside Bash, and PowerShell is given its own authentication example tab. Visual Studio Code is referenced as the default editor, and Windows environment variable instructions precede Linux equivalents. There is no explicit Linux example for editors or shell usage, and some instructions assume familiarity with Windows tooling.
Recommendations
  • Provide equal prominence to Linux and macOS tools and workflows, such as recommending editors like Vim, Nano, or VS Code for Linux.
  • Include Bash and Linux terminal examples before or alongside Windows (cmd/PowerShell) examples.
  • Add authentication instructions for Bash/Azure CLI as a first-class tab, not just PowerShell.
  • Clarify that Visual Studio Code is cross-platform, and suggest alternatives for Linux users.
  • Ensure environment variable setup instructions for Linux/macOS are presented with equal visibility and detail as Windows.
  • Avoid listing Windows tools (cmd, PowerShell) before Bash in generic instructions.
  • Where possible, add screenshots or walkthroughs using Linux environments.
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-09 00:34
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 consistently referencing Windows PowerShell as the default command-line environment, especially in the PowerShell section ("Open a Windows PowerShell command window"). Windows tools and terminology (e.g., 'command console application such as Windows PowerShell') are mentioned before Linux equivalents, and there is no explicit mention or example of using Bash or Linux terminals for Azure CLI or PowerShell. The documentation does not provide parity for Linux users in terms of environment setup or command execution context.
Recommendations
  • Explicitly mention that Azure CLI and PowerShell can be used from Bash/Linux/macOS terminals, not just Windows PowerShell.
  • Provide example commands for opening a Bash terminal or using Azure CLI/PowerShell on Linux/macOS.
  • Avoid phrases like 'Open a Windows PowerShell command window'—instead, use 'Open your preferred terminal (Windows PowerShell, Bash, etc.)'.
  • Add notes or sections for Linux/macOS users, including installation and usage instructions for Azure CLI and PowerShell on those platforms.
  • Ensure that screenshots and walkthroughs do not exclusively show Windows environments.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/versioning-enable.md .../blob/main/articles/storage/blobs/versioning-enable.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples and instructions, listing PowerShell before Azure CLI in each section, and referencing Windows-centric tools (PowerShell, Az.Storage module). There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific patterns or tools. The Azure CLI examples are present, but PowerShell is consistently presented first, and there is no parity for Linux command-line environments or scripting.
Recommendations
  • Add bash and Linux shell examples alongside PowerShell, especially for Azure CLI usage.
  • Alternate the order of examples so that Azure CLI (cross-platform) is listed before PowerShell.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary environment setup instructions for Linux users.
  • Where PowerShell modules are referenced, provide equivalent instructions for bash or other Linux shells if possible.
  • Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., avoid referencing Windows-only features or terminology).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/account-encryption-key-create.md ...ticles/storage/common/account-encryption-key-create.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides examples for Azure portal, PowerShell, Azure CLI, and ARM templates. PowerShell is featured prominently, with detailed instructions and examples, and is mentioned before Azure CLI in both creation and verification sections. PowerShell is a Windows-centric tool, and its inclusion and ordering may indicate a Windows bias. There are no Linux shell-specific examples (e.g., Bash scripts), and no mention of Linux-native tools or patterns. Azure CLI is cross-platform, but the absence of explicit Linux context or parity (such as Bash scripting or Linux package installation notes) reinforces the bias.
Recommendations
  • Add explicit Bash shell examples for Azure CLI usage, showing Linux-style command usage and scripting.
  • Include installation instructions for Azure CLI on Linux, not just a generic link.
  • Reorder examples so that Azure CLI (cross-platform) appears before PowerShell, or present them side-by-side.
  • Mention that PowerShell Core is available on Linux, if PowerShell examples are retained, and provide Linux installation instructions.
  • Consider adding notes or examples for Linux users, such as using environment variables or shell scripting for automation.
  • Ensure that all instructions and screenshots are platform-neutral or provide alternatives for Linux environments.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for command-line operations, omitting equivalent Azure CLI or Bash examples that would be more familiar to Linux and macOS users. The use of PowerShell is presented as the sole scripting option, and Windows-centric tools and installation steps (such as PowerShellGet and PowerShell modules) are described in detail. No Linux-specific instructions, shell commands, or parity examples are provided, and PowerShell is consistently mentioned before Azure CLI, which is only referenced briefly at the end.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, including listing, deleting, and migrating storage accounts.
  • Include Bash shell commands where appropriate, especially for tasks that can be performed via REST API or Azure CLI.
  • Provide installation and usage instructions for Azure CLI on Linux and macOS, not just PowerShell modules.
  • Ensure that Azure CLI is mentioned as a first-class option for automation and scripting, not just as an afterthought.
  • Add screenshots or walkthroughs for Linux environments where relevant, such as using Azure CLI in a terminal.
  • Clearly indicate cross-platform compatibility for all tools and commands, and avoid assuming a Windows-only environment.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/classic-account-migration-process.md ...es/storage/common/classic-account-migration-process.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently mentioning PowerShell and Windows-centric migration tools before Azure CLI or cross-platform alternatives. References to migration steps and supporting articles prioritize PowerShell examples, and there is a lack of explicit Linux or Bash examples. The documentation does not provide parity in instructions or tooling for Linux users, and Windows tools/patterns are referenced more prominently.
Recommendations
  • Ensure that Azure CLI (cross-platform) examples are presented alongside or before PowerShell examples.
  • Explicitly mention Bash or Linux shell usage where relevant, and provide sample commands for Linux environments.
  • Avoid referencing PowerShell or Windows-specific tools as the default or primary method; present them as one of several options.
  • Include troubleshooting and migration guidance for Linux users, such as common issues encountered in Bash or Linux environments.
  • Review linked articles to ensure Linux parity in step-by-step instructions and screenshots.
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-09 00:34
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 given before the Azure CLI example, and there is no mention of Linux-specific shell usage or alternative scripting environments. The CLI example uses Bash syntax, but there is no explicit reference to Linux or guidance for Linux users. There are no examples for Linux-native tools or environments beyond Azure CLI, and no mention of platform-specific differences or considerations.
Recommendations
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide platform-specific notes if needed.
  • Provide examples using Bash or other Linux-native shells, and clarify any differences in environment setup or command usage between Windows and Linux.
  • Consider including references to Linux package managers for installing Azure CLI (e.g., apt, yum) and PowerShell Core on Linux, if relevant.
  • If PowerShell is mentioned, clarify that PowerShell Core is cross-platform and provide installation instructions for Linux.
  • Avoid listing PowerShell examples before CLI examples, or alternate the order to avoid implicit prioritization of Windows tools.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/configure-network-routing-preference.md ...storage/common/configure-network-routing-preference.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 prominently as a primary automation example, and is presented before Azure CLI in each example section. The use of PowerShell commands and terminology (e.g., 'Set-AzStorageAccount', 'Get-AzSubscription') caters to Windows users, while Linux-native tools or shell examples are not mentioned. Although Azure CLI is included, there is no explicit guidance for Linux users, nor are bash or shell scripting patterns shown. The portal instructions are platform-neutral, but the command-line guidance leans toward Windows-first approaches.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implicit prioritization of Windows tools.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide bash shell scripting examples where appropriate.
  • Add notes or links for Linux users on installing and using Azure CLI, including usage in native terminals.
  • Where PowerShell is used, clarify its cross-platform availability, or provide equivalent bash examples for Linux users.
  • Review terminology to avoid Windows-centric phrasing (e.g., 'console' vs. 'terminal', 'PowerShell' vs. 'shell').
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/customer-managed-keys-configure-cross-tenant-new-account.md ...stomer-managed-keys-configure-cross-tenant-new-account.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for configuring cross-tenant customer-managed keys using the Azure Portal, PowerShell, and Azure CLI. PowerShell is featured prominently as a primary scripting example, which is typically associated with Windows environments. There are no explicit examples or guidance for Linux shell scripting (e.g., Bash) or automation using Linux-native tools. The Azure CLI example is present, but it does not clarify platform parity or address Linux-specific nuances. The documentation does not mention or demonstrate Linux-specific workflows, and PowerShell is listed before Azure CLI, reinforcing a Windows-first approach.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for Azure CLI commands, including environment setup and variable usage.
  • Clarify that Azure CLI is cross-platform and provide notes or examples for both Windows (CMD/PowerShell) and Linux (Bash) usage.
  • Consider reordering the examples to present Azure CLI before PowerShell, as CLI is more commonly used in Linux environments.
  • Mention any platform-specific considerations (e.g., authentication, environment variables, file paths) for Linux users.
  • Include a section or note on how to perform these steps in a Linux environment, possibly referencing automation scripts or tools commonly used in Linux.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references upgrade procedures using the Azure portal, CLI, or PowerShell, but consistently mentions PowerShell before CLI and does not provide explicit Linux or Bash examples. PowerShell is a Windows-centric tool, and its prominence may suggest a Windows bias. There are no examples or guidance tailored for Linux users, such as Bash scripts or Linux-specific CLI usage patterns.
Recommendations
  • Provide explicit Bash/Azure CLI examples for Linux users alongside PowerShell instructions.
  • When listing upgrade methods, alternate or randomize the order of PowerShell and CLI, or mention CLI first to avoid Windows-first bias.
  • Include notes or links to Linux-specific documentation or troubleshooting for common upgrade scenarios.
  • Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux (Bash) environments.
  • Add a section addressing upgrade steps for users on macOS and Linux, ensuring parity with Windows guidance.
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-09 00:34
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 scripted method, which is Windows-centric. The CLI example is given, but there is no explicit mention of Linux/macOS environments, nor are Bash or shell script examples provided. The order of examples places PowerShell before CLI, subtly prioritizing Windows tooling. No Linux-specific tools or considerations are discussed.
Recommendations
  • Add explicit Bash/shell script examples for Linux/macOS users, especially for Azure CLI usage.
  • Clarify that Azure CLI commands work cross-platform and provide guidance for installation/use on Linux/macOS.
  • Consider reordering examples to present Azure CLI before PowerShell, or present both together to avoid implicit prioritization.
  • Mention any platform-specific considerations (e.g., authentication, environment setup) for Linux/macOS users.
  • If relevant, reference Linux-native automation tools (e.g., shell scripting, cron) for migration scenarios.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/manage-storage-analytics-logs.md ...ticles/storage/common/manage-storage-analytics-logs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 configuration, explicitly instructing users to open a Windows PowerShell window, and referencing Windows-style file paths (e.g., 'C:\Logs\Storage') in AzCopy examples. There are no equivalent examples for Linux or cross-platform shells (such as Bash or Azure CLI), and Windows tools and patterns are mentioned exclusively or before any alternatives.
Recommendations
  • Add equivalent Azure CLI and/or Bash examples for all PowerShell command-line instructions, ensuring Linux and macOS users have clear guidance.
  • Use cross-platform language when referring to command-line windows (e.g., 'Open a terminal window' instead of 'Open a Windows PowerShell command window').
  • Include Linux/macOS file path examples (e.g., '~/logs/storage') alongside Windows paths in AzCopy and other relevant examples.
  • Mention cross-platform tools (such as Azure CLI and AzCopy) before or alongside Windows-specific tools, and clarify their availability on all major platforms.
  • Where .NET code is shown, consider referencing SDKs or code samples in other languages commonly used on Linux (e.g., Python, Java) if appropriate.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing Windows-centric tools (Visual Studio) and patterns (Azure portal UI, .NET/ASP.NET as the primary example app), and by omitting explicit Linux-specific instructions or examples (such as Bash, Linux service hosting, or Linux-native developer tools). While cross-platform SDK code samples are provided, local development guidance and tool references prioritize Windows environments and tools, with no mention of Linux equivalents or parity in developer experience.
Recommendations
  • Include explicit Linux development instructions, such as using Bash, VS Code, or other Linux-native tools for local development.
  • Reference Linux hosting scenarios (e.g., Azure Linux App Service, Ubuntu VM) equally alongside Windows hosting environments.
  • Provide screenshots and instructions for Azure CLI usage in Bash or Linux terminals, not just Azure portal UI.
  • Mention Linux authentication patterns (e.g., using Azure CLI on Linux, environment variables setup in Linux shells) in local development sections.
  • Add troubleshooting notes or tips for common Linux-specific issues (such as file permissions, environment variable configuration, or package installation).
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently presents Windows-centric tools and workflows first (Azure portal, PowerShell), with PowerShell examples and scripts provided in detail. Linux-specific instructions, such as Bash scripting or Linux-native tools, are not present. The CLI examples are platform-neutral, but there is no explicit mention of Linux environments or parity with Windows. There are no examples using Linux shell scripting, nor references to Linux-specific considerations (e.g., file paths, shell differences).
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample Bash scripts for Linux users alongside PowerShell scripts.
  • Include Linux/Bash-specific instructions and examples, such as using Bash arrays, loops, and file paths, especially in sections that currently only show PowerShell scripts for batch operations.
  • Clarify cross-platform compatibility for tools like AzCopy and Azure CLI, and provide usage notes for Linux environments (e.g., handling CSV files, line endings).
  • Where PowerShell is referenced, also provide equivalent Bash or shell script examples for common tasks.
  • Add notes or sections highlighting any differences or considerations for Linux users (e.g., authentication, environment setup, file system paths).
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a moderate Windows bias. Examples and instructions for disabling Shared Key authorization are presented first for the Azure portal (a GUI tool most commonly used on Windows), followed by PowerShell (a Windows-centric tool), and only then Azure CLI and ARM templates. References to Azure Storage Explorer and AzCopy link to Windows-specific tabs or instructions. There are no explicit Linux shell (bash) examples, and PowerShell is given prominence over CLI. The documentation does not mention Linux-specific considerations or alternative tools, and screenshots are from the Windows version of the Azure portal.
Recommendations
  • Provide explicit Linux/bash examples alongside PowerShell, especially for command-line operations.
  • Ensure that Azure CLI instructions are presented before or alongside PowerShell, as CLI is cross-platform.
  • Include notes or links for using Azure Storage Explorer and AzCopy on Linux/macOS, not just Windows.
  • Use neutral language and screenshots that do not imply Windows as the default platform.
  • Where relevant, mention any platform-specific differences or requirements 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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation consistently provides PowerShell examples and references the Az.Storage PowerShell module, which is primarily used on Windows. PowerShell examples are given equal prominence to Azure CLI, but there is no mention of Bash, Linux shell, or cross-platform scripting alternatives. The use of PowerShell as a primary scripting example and the lack of explicit Linux/Bash examples or notes about platform compatibility indicate a Windows bias. Additionally, PowerShell is mentioned before Azure CLI in most sections, reinforcing a Windows-first approach.
Recommendations
  • Add explicit Bash/Linux shell examples alongside PowerShell and Azure CLI, especially for command-line operations.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Include notes about platform compatibility for PowerShell commands, e.g., that PowerShell Core is available on Linux/macOS, but Az.Storage is most commonly used on Windows.
  • Consider reordering examples so that Azure CLI (the most cross-platform tool) appears before PowerShell.
  • Reference Linux tools or scripting patterns where appropriate, and avoid assuming PowerShell as the default scripting environment.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is consistently presented as a primary method for scripting and automation, with detailed examples and instructions. In sections describing deployment via Bicep and ARM templates, PowerShell is mentioned before Azure CLI, and PowerShell commands are given first. The use of PowerShell-specific modules and installation instructions further reinforces the Windows-centric approach. While Azure CLI (which is cross-platform) is covered thoroughly and Cloud Shell is highlighted as Bash-based, the overall structure and ordering of examples and instructions tend to prioritize Windows/PowerShell tools over Linux-native or cross-platform alternatives.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first in some sections to avoid implicit prioritization of Windows tools.
  • Explicitly mention that Azure CLI and Cloud Shell Bash are fully supported on Linux and macOS, and provide links to installation guides for those platforms.
  • Where PowerShell installation is described, also include instructions for installing Azure CLI on Linux and macOS.
  • In Bicep and ARM template deployment instructions, present Azure CLI and PowerShell examples side-by-side, or clarify that both are equally supported.
  • Consider including a short section or note on using Bash scripts for automation, especially for Linux users.
  • Review images and screenshots to ensure they do not exclusively depict Windows environments or PowerShell terminals.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-account-keys-manage.md ...articles/storage/common/storage-account-keys-manage.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided for every operation, and PowerShell is referenced before Azure CLI in all code sample sections. The use of PowerShell as a primary scripting example is more familiar to Windows users, while Linux users typically prefer Bash or other shells. There are no explicit Bash script examples (other than Azure CLI commands), and no mention of Linux-specific tools or patterns. The Azure portal is platform-neutral, but the scripting guidance leans toward Windows-centric tools and ordering.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to better support Linux users.
  • Explicitly mention that Azure CLI commands can be run in Bash on Linux/macOS, and provide sample Bash scripts where appropriate.
  • Add notes or links for Linux/macOS users on installing and using Azure CLI and PowerShell Core (pwsh), clarifying cross-platform support.
  • Include troubleshooting or environment setup tips for Linux/macOS users (e.g., shell differences, authentication methods).
  • Consider providing examples using REST API or SDKs in languages popular on Linux (Python, Node.js) for advanced scenarios.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. PowerShell is the only command-line example provided for interacting with log blobs, with no equivalent shown for Bash, Azure CLI, or Linux scripting. References to tools and user agents in log samples are predominantly Windows-based (e.g., 'win32', 'Windows_NT'), and Microsoft Azure Storage Explorer is mentioned without noting cross-platform support. The order of mention for enabling logging lists PowerShell before Azure CLI, and there are no explicit Linux or macOS instructions or examples.
Recommendations
  • Add equivalent Azure CLI and Bash examples for listing and filtering log blobs, including metadata access, to complement the PowerShell snippet.
  • Explicitly mention that Azure Storage Explorer is cross-platform, and provide examples or screenshots for Linux/macOS usage.
  • When listing options for enabling logging, alternate or randomize the order of PowerShell and Azure CLI, or group them together as 'command-line tools', to avoid Windows-first ordering.
  • Include log entry examples that feature Linux/macOS user agents and tools (e.g., azcopy on Linux, Azure CLI on macOS) to balance the representation.
  • Add a section or note on how Linux/macOS users can perform common tasks (such as accessing the $logs container, viewing metadata, etc.) using native tools or scripts.
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-09 00:34
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 alongside the Azure portal and Azure CLI, with detailed PowerShell instructions and references to installing/configuring PowerShell. The PowerShell example is given before the Azure CLI example, and there is no mention of Linux-specific tools, shell environments, or alternative command-line patterns (e.g., Bash, scripting on Linux/macOS). The installation instructions for Azure CLI are generic, but the PowerShell section is more detailed and assumes a Windows-centric workflow. No Linux-specific examples or considerations are provided.
Recommendations
  • Add explicit Bash/Linux/macOS shell examples for Azure CLI usage, including common patterns for scripting upgrades.
  • Mention that Azure CLI works cross-platform and provide installation instructions for Linux/macOS alongside Windows.
  • Include notes or examples for automating upgrades using Bash scripts or other Linux-native tools.
  • Ensure that CLI examples are presented before or alongside PowerShell examples to avoid Windows-first ordering.
  • Reference Linux and macOS environments in the prerequisites and instructions, not just Windows/PowerShell.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page frequently references Windows-centric tools and patterns, such as Azure PowerShell and AzCopy, without providing equivalent Linux or cross-platform examples. Windows tools are mentioned first or exclusively in several sections, and there is a lack of explicit Linux command-line or scripting guidance. This may make it harder for Linux users to follow disaster recovery procedures or leverage best practices using their preferred environments.
Recommendations
  • Provide explicit Linux and cross-platform CLI examples alongside PowerShell, such as Azure CLI commands for all operations.
  • Mention AzCopy as a cross-platform tool and provide installation and usage instructions for Linux/macOS, not just Windows.
  • When listing tools (e.g., AzCopy, Azure PowerShell), always include Azure CLI and/or REST API examples, and avoid listing Windows tools first.
  • Add sample scripts or command lines for Linux environments (bash, shell) for common tasks like copying data, checking sync time, or managing failover.
  • Clarify that most Azure Storage operations can be performed from any OS, and link to cross-platform documentation where possible.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed PowerShell instructions, including module installation and troubleshooting steps specific to PowerShell 5.1, which is primarily a Windows environment. PowerShell examples are more extensive than Azure CLI, and Windows-specific tooling (PowerShellGet) is mentioned. The order of presentation places PowerShell before Azure CLI, potentially signaling a Windows-first approach. There are no explicit Linux shell (bash) examples or references to Linux-specific considerations, and the CLI instructions do not mention Linux package managers or shell environments.
Recommendations
  • Add explicit bash/Linux shell examples for Azure CLI commands, including installation steps using apt, yum, or other Linux package managers.
  • Clarify that Azure CLI commands work cross-platform and provide troubleshooting steps for common Linux environments.
  • Balance the depth of PowerShell and CLI sections, ensuring CLI instructions are as detailed as PowerShell, including extension management and environment-specific notes.
  • Mention cross-platform alternatives to PowerShell (such as bash scripts) and provide links or examples where appropriate.
  • Reorder sections or add notes to emphasize platform neutrality, e.g., by presenting CLI and PowerShell in parallel or stating that both are supported on Windows, Linux, and macOS.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-install-azurite.md ...ain/articles/storage/common/storage-install-azurite.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Windows-specific paths (e.g., c:\azurite), focusing on Visual Studio and Visual Studio Code (Windows-centric tools), and omitting Linux/macOS equivalents for file paths, commands, and environment setup. All command-line examples use Windows-style paths, and there are no instructions or examples for Linux or macOS users, such as using /home/user/azurite or /tmp/azurite, nor are there mentions of Linux package managers or shell commands. The location of the Azurite executable is only described for Windows installations of Visual Studio. Docker volume mounting examples also use Windows paths. No PowerShell-specific commands are present, but the overall pattern prioritizes Windows environments and tools.
Recommendations
  • Add Linux/macOS-specific examples for all command-line instructions, using POSIX-style paths (e.g., /home/user/azurite) alongside Windows paths.
  • Include instructions for finding the Azurite executable when installed via npm or other methods on Linux/macOS.
  • Provide guidance for running Azurite on Linux/macOS, including common shell commands and environment setup.
  • Update Docker examples to show both Windows and Linux volume mounting syntax.
  • Mention Linux/macOS package managers (e.g., Homebrew, apt) if applicable for installing prerequisites like Node.js.
  • Clarify that Azurite is cross-platform and explicitly address platform differences where relevant.
GitHub Create Pull Request
← Previous Page 19 of 67 Next →