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 76-100 of 1657 flagged pages
Storage Static website hosting in Azure Storage .../articles/storage/blobs/storage-blob-static-website.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation lists Windows-centric tools (PowerShell, Azure Storage Explorer, Visual Studio Code extension) and mentions PowerShell before Linux alternatives. While Azure CLI and AzCopy are cross-platform, the examples and tool recommendations lean toward Windows-first experiences. There are no explicit Linux shell (bash) or macOS-specific examples, and no mention of Linux-native tools or workflows.
Recommendations
  • Provide explicit Linux and macOS examples, such as bash commands for Azure CLI and AzCopy.
  • Clarify cross-platform support for each tool listed, indicating which are available on Linux/macOS.
  • Add screenshots or instructions for Linux environments (e.g., terminal usage, file upload via CLI).
  • Include parity in example tabs: if PowerShell is shown, also show Bash or Linux shell equivalents.
  • Mention Linux-native editors (e.g., VS Code on Linux) and workflows where appropriate.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific .NET configuration patterns (such as ServicePointManager and ThreadPool), providing only C#/.NET code samples, and omitting any mention of Linux-specific considerations or examples. There is no discussion of how these performance tuning options might differ or require adjustment on Linux, nor are there any Linux shell or cross-platform code samples. The guidance assumes a Windows/.NET environment throughout.
Recommendations
  • Include explicit notes about cross-platform behavior, especially how .NET's connection pooling and threading differ on Linux vs. Windows.
  • Add Linux-specific examples or considerations, such as how to monitor or tune .NET applications running on Linux (e.g., using dotnet CLI, system resource limits, ulimit, etc.).
  • Provide code samples or configuration guidance for Linux environments, such as running .NET Core on Linux, and mention any OS-specific caveats.
  • Reference cross-platform tools and patterns (e.g., dotnet CLI, environment variables) alongside or before Windows-specific APIs.
  • Clarify whether the recommendations (e.g., ServicePointManager.DefaultConnectionLimit) apply equally on Linux and Windows, and provide alternatives if not.
GitHub Create Pull Request
Storage Map a custom domain to an Azure Blob Storage endpoint ...n/articles/storage/blobs/storage-custom-domain-name.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently as a first-class method for command-line operations, and the term 'PowerShell command' is used even in the Azure CLI sections, which may confuse Linux users. The ordering of examples and instructions often places PowerShell before Azure CLI, subtly prioritizing Windows tooling. There are no explicit Linux shell examples or references to Linux-specific patterns, and the documentation does not clarify cross-platform compatibility for command-line instructions.
Recommendations
  • Use neutral language for command-line instructions (e.g., 'Run the following command' instead of 'Run the following PowerShell command') in Azure CLI sections.
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to better reflect cross-platform usage.
  • Explicitly state that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Add example shell commands for Linux/macOS environments where relevant (e.g., using Bash or zsh).
  • Clarify prerequisites for each command-line tool, including installation instructions for Linux/macOS users.
  • Avoid assuming use of Windows-specific tools or terminology unless necessary, and provide parity for Linux users.
GitHub Create Pull Request
Storage Quickstart: Azure Blob storage library - TypeScript ...ge/blobs/storage-quickstart-blobs-nodejs-typescript.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (cmd, PowerShell, Visual Studio Code) are mentioned before or alongside Linux equivalents, and examples for authentication and environment variable setup are presented with Windows commands first. PowerShell is given its own authentication section, while Bash/Linux is less emphasized and not given parity in tooling recommendations. Visual Studio Code is presented as the default editor, which is more common on Windows. Linux instructions are present but often secondary.
Recommendations
  • Present Linux and Windows instructions side-by-side, or in tabs, rather than listing Windows first.
  • Include Bash and Linux-native tooling (e.g., gedit, nano, vi) as alternatives to Visual Studio Code.
  • Provide parity for authentication examples, e.g., show Bash/Azure CLI sign-in as prominently as PowerShell.
  • Avoid assuming Visual Studio Code as the default editor; mention alternatives for Linux users.
  • Ensure all environment variable setup instructions are equally detailed for both Windows and Linux.
  • Consider adding a section or tab for MacOS where relevant.
GitHub Create Pull Request
Storage Quickstart: Azure Blob storage library - JavaScript ...icles/storage/blobs/storage-quickstart-blobs-nodejs.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by listing Windows-specific consoles (cmd, PowerShell) before Bash when describing terminal usage, and by providing PowerShell authentication instructions alongside Azure CLI and Visual Studio Code. Visual Studio Code is referenced as the default editor, which is cross-platform but has stronger adoption on Windows. Environment variable setup instructions are provided for both Windows and Linux, but Windows instructions appear first. There are no Linux-specific tooling recommendations, and Windows tools are mentioned more frequently and earlier in the text.
Recommendations
  • List Bash or Linux terminals before or alongside Windows consoles (cmd, PowerShell) when describing command-line usage.
  • Provide authentication instructions for Bash/Azure CLI before PowerShell, or present all OS options in parallel tabs.
  • Include examples using popular Linux editors (e.g., nano, vim) for opening project files, or clarify that Visual Studio Code is cross-platform.
  • Alternate the order of Windows and Linux instructions for setting environment variables, or present them side-by-side.
  • Explicitly mention that all commands work on Linux/macOS as well as Windows, and provide troubleshooting tips for non-Windows platforms.
  • Consider including a section or note on using the Azure Developer CLI and Node.js on Linux/macOS, with links to platform-specific installation guides.
GitHub Create Pull Request
Storage We're retiring classic storage accounts on August 31, 2024 ...s/storage/common/classic-account-migration-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias, primarily through its repeated references to PowerShell cmdlets for management and migration tasks. The FAQ specifically discusses legacy and modern PowerShell cmdlets, with no mention of equivalent CLI or scripting options for Linux (such as Bash, Azure CLI, or REST API usage). Windows-centric tools and terminology (e.g., PowerShell, resource group naming conventions) are mentioned exclusively or before any cross-platform alternatives. There are no explicit Linux or cross-platform examples or instructions provided.
Recommendations
  • Add examples using Azure CLI (az) commands for all migration and management operations, alongside PowerShell examples.
  • Include references to REST API usage for migration and management, which is platform-agnostic.
  • Explicitly mention that all operations can be performed from Linux, macOS, or Windows, and provide sample commands/scripts for each.
  • Where PowerShell is referenced, also provide Bash or shell script equivalents.
  • Clarify that the Azure Portal and Azure CLI are fully supported on non-Windows platforms, and link to relevant cross-platform documentation.
GitHub Create Pull Request
Storage Encrypt and decrypt blobs using Azure Key Vault ...orage/blobs/storage-encrypt-decrypt-blobs-key-vault.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows tools and workflows, such as Visual Studio and PowerShell, and presenting Windows-specific instructions and examples before their Linux equivalents. PowerShell is featured heavily for package installation and role assignment, while Linux alternatives are mentioned but less detailed or secondary. The setup instructions and environment variable guidance also favor Windows, with Visual Studio as the primary editor and Windows command-line tools presented first.
Recommendations
  • Provide Linux and macOS examples alongside Windows instructions, ensuring parity in detail and clarity.
  • Include cross-platform code editor options (e.g., JetBrains Rider, Vim, Emacs) and highlight Visual Studio Code as a cross-platform editor.
  • Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform and preferred by many Linux users.
  • Expand Linux-specific instructions for environment variable setup, package installation, and project creation.
  • Avoid assuming Visual Studio as the default IDE; offer guidance for using other editors and command-line workflows.
  • Where possible, use generic 'console' or 'terminal' terminology instead of 'PowerShell window' or 'command prompt'.
GitHub Create Pull Request
Storage Quickstart: Azure Blob Storage library - .NET ...icles/storage/blobs/storage-quickstart-blobs-dotnet.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Visual Studio Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently presenting Visual Studio (Windows-only) instructions and screenshots before cross-platform .NET CLI alternatives. The setup and installation steps prioritize Visual Studio, and troubleshooting NuGet package sources references Windows-centric tools. While .NET CLI commands are cross-platform, there is little explicit guidance for Linux users (e.g., using Linux editors, file paths, or shell environments). No Linux-specific screenshots or examples are provided, and PowerShell/cmd are mentioned as console options before Bash. The documentation assumes familiarity with Windows development patterns and tools.
Recommendations
  • Present .NET CLI instructions before Visual Studio steps, or in parallel, to emphasize cross-platform parity.
  • Include explicit Linux examples, such as using Linux-native editors (e.g., nano, vim), and show file paths in Linux format.
  • Add screenshots for Linux environments (e.g., VS Code on Ubuntu) alongside Visual Studio images.
  • Mention Bash and Linux shells first or equally when listing console options.
  • Provide troubleshooting steps for NuGet and .NET CLI that address common Linux issues (e.g., permissions, package sources).
  • Clarify that all .NET CLI commands work on Linux and macOS, and highlight any OS-specific considerations.
GitHub Create Pull Request
Storage Quickstart: Azure Blob Storage library - Java ...rticles/storage/blobs/storage-quickstart-blobs-java.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias, primarily by listing Windows and PowerShell tools or commands before their Linux or Bash equivalents, and by referencing Windows file paths in output examples. While Bash and Linux instructions are present, Windows tools and patterns are often mentioned first, and PowerShell is given a dedicated tab in the project creation step. Output examples use Windows-style paths (e.g., C:\QuickStarts\blob-quickstart), and environment variable instructions list Windows (setx) before Linux (export).
Recommendations
  • Alternate the order of Windows and Linux/Bash instructions throughout the documentation, or present them side-by-side to avoid privileging one platform.
  • Use platform-agnostic language and file paths in output examples where possible, or provide both Windows and Linux path examples.
  • Ensure that all command-line instructions and environment variable setup steps are equally detailed for both Windows and Linux users.
  • Where tabs are used for PowerShell and Bash, consider making Bash the default or randomizing the default tab to avoid always privileging Windows.
  • Review all screenshots and code snippets for platform-specific references and provide Linux equivalents where appropriate.
GitHub Create Pull Request
Storage Quickstart: Deploy a static website on Azure Storage using Terraform ...e/blobs/storage-quickstart-static-website-terraform.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but it lists Azure CLI first and then Azure PowerShell, which is a common pattern but may suggest a slight Windows-first approach. However, there are no explicit Linux shell (bash) examples, nor any mention of Linux-specific tools or workflows. The use of PowerShell examples and lack of Linux shell commands (e.g., bash) may make the documentation less accessible to Linux users.
Recommendations
  • Add explicit bash/Linux shell examples alongside Azure CLI and PowerShell, especially for command-line tasks.
  • Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide sample commands in bash syntax.
  • If PowerShell is shown, also show equivalent bash commands for parity.
  • Mention cross-platform compatibility in prerequisites and instructions to ensure Linux users feel supported.
GitHub Create Pull Request
Storage Upgrade Azure Blob Storage with Azure Data Lake Storage capabilities ...rage/blobs/upgrade-to-data-lake-storage-gen2-how-to.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by consistently referencing Windows PowerShell as the primary shell 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 or instead of Linux equivalents. There is no mention of Linux shells (e.g., Bash) or cross-platform PowerShell Core, and no explicit Linux-specific instructions or examples are provided. The documentation assumes a Windows environment for command-line operations, which may exclude or confuse Linux users.
Recommendations
  • Explicitly mention that PowerShell cmdlets can be run in PowerShell Core on Linux/macOS, not just Windows PowerShell.
  • Instruct users to open a terminal (e.g., Bash, zsh, PowerShell Core) on Linux/macOS, not just 'Windows PowerShell'.
  • Provide Linux/macOS-specific instructions or notes for installing and using Azure CLI and PowerShell modules.
  • Avoid referring to 'command console application such as Windows PowerShell' as the only example; include Bash and other terminals.
  • Add examples or screenshots showing Linux/macOS environments where appropriate.
  • Clarify that Azure CLI commands are cross-platform and can be run in any shell.
GitHub Create Pull Request
Storage Enable and manage blob versioning .../blob/main/articles/storage/blobs/versioning-enable.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and referencing Windows-centric tooling (PowerShell, Az.Storage module) before Linux alternatives. While Azure CLI is included, there are no explicit Linux shell (bash) examples, nor are Linux-specific considerations or patterns mentioned. The ordering and depth of PowerShell coverage suggest a prioritization of Windows users. No Linux-native tools or scripts are referenced, and the CLI examples use variable syntax that is ambiguous between Windows and Linux shells.
Recommendations
  • Add explicit bash/Linux shell examples for Azure CLI commands, using Linux environment variable syntax and shell conventions.
  • Clarify cross-platform compatibility for CLI commands, including notes on differences in variable usage and authentication between Windows and Linux.
  • Include references to Linux-native scripting and automation approaches, such as bash scripts or cron jobs for blob management.
  • Balance the ordering of examples so that Azure CLI (cross-platform) is presented before PowerShell, or provide equal prominence.
  • Mention installation steps for Azure CLI and PowerShell on both Windows and Linux, highlighting platform-specific instructions.
  • Where PowerShell is referenced, note its availability on Linux and provide guidance for Linux users.
GitHub Create Pull Request
Storage Create an account that supports customer-managed keys for tables and queues ...ticles/storage/common/account-encryption-key-create.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides examples for Azure portal, PowerShell, Azure CLI, and ARM templates. PowerShell is featured prominently, with detailed instructions and examples, and is listed before Azure CLI in both creation and verification sections. PowerShell is a Windows-centric tool, and its prominence, along with explicit installation instructions, reflects a Windows bias. There are no Linux shell-specific examples (e.g., Bash scripts), nor is there mention of Linux-native tools or patterns. Azure CLI is cross-platform, but PowerShell's priority and depth of coverage suggest a Windows-first approach.
Recommendations
  • Add Bash shell examples for Linux users, especially for scripting and automation tasks.
  • List Azure CLI examples before PowerShell, as CLI is more platform-neutral and widely used on Linux.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide installation instructions for Linux.
  • Reduce the emphasis on PowerShell or balance it with equivalent Linux-native scripting examples.
  • Include troubleshooting or verification steps using Bash/Unix tools where possible.
GitHub Create Pull Request
Storage Upgrading Azure Blob Storage to Azure Data Lake Storage ...les/storage/blobs/upgrade-to-data-lake-storage-gen2.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific tools (AzCopy, Storage Explorer), and mentions PowerShell commands before Azure CLI commands when listing SDKs and command-line options. The Hadoop driver is called 'Windows Azure Storage Blob driver (WASB)', which is a legacy, Windows-named component. There are no explicit Linux shell or bash examples, nor are Linux-native tools (e.g., shell scripts, Linux file utilities) mentioned. The order of mentioning PowerShell before CLI may imply a Windows-first approach.
Recommendations
  • Provide Linux/bash examples alongside or before PowerShell examples, especially for command-line operations.
  • Mention cross-platform tools explicitly (e.g., AzCopy is available for Linux and macOS, not just Windows).
  • Clarify that Azure CLI and SDKs are cross-platform and provide usage examples for Linux environments.
  • When listing command-line options, alternate the order or group them as 'cross-platform' rather than 'PowerShell first'.
  • Reference Linux-native tools or patterns where appropriate, such as scripting with bash or using Linux file utilities for migration scenarios.
  • Avoid legacy Windows-centric terminology (e.g., WASB) without noting its cross-platform context or alternatives.
GitHub Create Pull Request
Storage Use the Azure Storage resource provider to access management resources ...cles/storage/common/authorization-resource-provider.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing Windows-centric tools (PowerShell, Azure classic CLI) before mentioning platform-neutral or Linux-friendly alternatives. There are no explicit Linux shell (bash/az CLI) examples or references, and PowerShell is highlighted as a primary method for role assignment. The absence of Linux-specific instructions or parity in tool recommendations may hinder Linux users.
Recommendations
  • Include az CLI examples for role assignment and management operations, with explicit bash syntax.
  • List platform-neutral or Linux-friendly tools (az CLI, REST API) before or alongside Windows-specific tools like PowerShell.
  • Add a section or note clarifying cross-platform support and providing links to Linux/macOS installation guides for Azure CLI.
  • Ensure code samples and walkthroughs demonstrate both PowerShell and bash/az CLI usage for common tasks.
GitHub Create Pull Request
Storage How to migrate your classic storage accounts to Azure Resource Manager ...ain/articles/storage/common/classic-account-migrate.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for command-line operations, with no equivalent Azure CLI or Bash examples for Linux/macOS users. Windows-centric tools (PowerShell, Service Management module) are mentioned and detailed before any cross-platform alternatives. There is no guidance or code for Linux-native workflows, and the documentation assumes familiarity with Windows/PowerShell environments.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, including listing, deleting, and migrating classic storage accounts.
  • Explicitly mention that Azure CLI is cross-platform and provide installation links and usage instructions for Linux/macOS users.
  • Include Bash script snippets or guidance for users who prefer shell scripting on Linux.
  • Ensure that references to tools and modules do not assume a Windows environment; clarify platform compatibility for each tool.
  • Consider reordering sections so that cross-platform tools (Azure CLI) are presented before or alongside Windows-specific tools (PowerShell).
GitHub Create Pull Request
Storage Understand storage account migration from classic to Azure Resource Manager ...es/storage/common/classic-account-migration-process.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by consistently mentioning PowerShell and the Azure portal as migration tools before the Azure CLI, and by linking to PowerShell-specific migration guides ahead of CLI equivalents. There are no explicit Linux or bash shell examples, nor references to Linux-native tooling or patterns. The documentation assumes familiarity with Windows-centric tools and omits parity for Linux users.
Recommendations
  • Present Azure CLI and bash examples alongside or before PowerShell examples to ensure Linux parity.
  • Explicitly mention Linux/macOS compatibility for all migration steps and tools.
  • Add references to Linux-native documentation or guides for storage account migration.
  • Include sample commands for both PowerShell and bash/Azure CLI in migration instructions.
  • Avoid listing Windows tools or portals first unless there is a technical reason; alternate order or clarify cross-platform support.
GitHub Create Pull Request
Storage Configure cross-tenant customer-managed keys for an existing storage account ...r-managed-keys-configure-cross-tenant-existing-account.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed examples 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 Linux shell (bash) or cross-platform scripting examples beyond Azure CLI, and PowerShell is presented before Azure CLI. There is no mention of Linux-specific tools or workflows, nor any guidance for users on Linux systems regarding PowerShell Core compatibility or alternative approaches.
Recommendations
  • Add explicit bash shell examples for Azure CLI commands, demonstrating usage on Linux/macOS.
  • Clarify that Azure CLI is cross-platform and provide installation instructions for Linux/macOS alongside Windows.
  • Mention PowerShell Core compatibility on Linux/macOS if PowerShell examples are retained, or provide bash equivalents.
  • Ensure that scripting examples do not assume a Windows environment (e.g., avoid Windows-specific variables or paths).
  • Consider presenting Azure CLI examples before PowerShell, as CLI is more universally available across platforms.
GitHub Create Pull Request
Storage Configure cross-tenant customer-managed keys for a new storage account ...stomer-managed-keys-configure-cross-tenant-new-account.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step 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 examples (e.g., Bash, zsh). The CLI example is generic but does not clarify Linux compatibility or provide Linux-specific guidance. There are no references to Linux tools or patterns, and the documentation implicitly assumes familiarity with PowerShell, which is traditionally a Windows-centric tool.
Recommendations
  • Provide explicit Bash or Linux shell examples alongside PowerShell, especially for Azure CLI usage.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and note any OS-specific considerations.
  • Reorder examples to present Azure CLI (cross-platform) before PowerShell (Windows-centric) to reduce perceived Windows-first bias.
  • Add notes or links for installing and using Azure CLI on Linux and macOS.
  • Where PowerShell is referenced, mention that PowerShell Core is available cross-platform, and provide installation instructions for Linux/macOS if relevant.
GitHub Create Pull Request
Storage Customer-managed keys for account encryption ...icles/storage/common/customer-managed-keys-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. It references PowerShell as a method for revoking access to customer-managed keys, listing it before Azure CLI and without mentioning Linux shell equivalents. Additionally, in the section about managed disk encryption, the link for Windows is listed before the Linux link, suggesting a Windows-first approach. There are no explicit Linux/Bash examples or references to Linux-specific tooling throughout the page.
Recommendations
  • Provide explicit Bash or Linux shell examples alongside PowerShell, especially for key management and revocation tasks.
  • List Azure CLI and Bash examples before or alongside PowerShell to avoid Windows-first ordering.
  • Ensure parity in tooling references by mentioning cross-platform tools (like Azure CLI) first and clarifying their availability on Linux, macOS, and Windows.
  • Add a note or section highlighting cross-platform compatibility and usage patterns for Linux users.
  • In the managed disk encryption section, present Windows and Linux links together or in alphabetical order to avoid perceived prioritization.
GitHub Create Pull Request
Storage Configure network routing preference ...storage/common/configure-network-routing-preference.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently as a primary automation example, and Windows-centric tools and patterns (such as PowerShell cmdlets and terminology) are presented before Linux equivalents. The Azure CLI examples are present, but PowerShell is consistently listed before CLI, and there is no mention of Bash scripting, Linux shell environments, or cross-platform nuances. The documentation does not address platform-specific differences or provide Linux-specific guidance, which may hinder parity for Linux users.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to avoid implicit prioritization of Windows tools.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide guidance for running these commands in Bash or other Linux shells.
  • Include example snippets for Bash scripting or Linux shell usage where appropriate, especially for automation scenarios.
  • Add notes or sections highlighting any platform-specific differences, such as authentication workflows, environment setup, or file path conventions.
  • Review terminology to ensure it is not Windows-centric (e.g., avoid exclusive references to PowerShell or Windows tools unless necessary).
GitHub Create Pull Request
Storage GPv1 ZRS standard account retirement FAQ ...-zone-redundant-storage-migration-freq-asked-questions.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation 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. The upgrade instructions and troubleshooting sections refer to PowerShell and CLI together, but PowerShell—a Windows-specific tool—is mentioned first, and there are no Linux-specific command examples or guidance. This ordering and lack of Linux parity may unintentionally signal a Windows-centric bias.
Recommendations
  • Explicitly provide Linux/Bash examples for upgrade procedures using Azure CLI.
  • When listing tools, alternate or randomize the order (e.g., 'CLI or PowerShell') or mention CLI first to avoid Windows-first bias.
  • Include notes or examples for Linux users, such as common shell commands or troubleshooting steps specific to Bash environments.
  • Add a section or FAQ entry addressing upgrade steps for Linux/macOS users, including any platform-specific considerations.
  • Ensure parity in troubleshooting guidance, e.g., if PowerShell is mentioned, also provide equivalent CLI/Bash instructions.
GitHub Create Pull Request
Storage How to upgrade a General Purpose v1 (GPv1) with ZRS redundancy account to GPv2 ...rpose-version-1-zone-redundant-storage-upgrade-process.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides upgrade instructions using the Azure portal, PowerShell, and Azure CLI. PowerShell is presented as a primary scripted method, which is Windows-centric, and no explicit Linux shell (bash) example is given. The CLI example is generic, but the lack of a Linux-specific context or example (such as bash scripting or explicit mention of Linux environments) suggests a Windows-first bias. There is no mention of Linux tools or patterns, and PowerShell is listed before Azure CLI.
Recommendations
  • Add explicit Linux/bash examples alongside PowerShell, showing how to run the Azure CLI command in a Linux shell.
  • Mention that Azure CLI is cross-platform and provide context for both Windows and Linux users.
  • Consider listing Azure CLI before PowerShell, as it is platform-agnostic and more commonly used in Linux environments.
  • Include troubleshooting or environment-specific notes for Linux users (e.g., installation, authentication differences).
GitHub Create Pull Request
Storage Enable infrastructure encryption for double encryption of data ...les/storage/common/infrastructure-encryption-enable.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides examples for enabling infrastructure encryption using the Azure portal, PowerShell, Azure CLI, and ARM templates. PowerShell is given a dedicated section with detailed examples, and the Azure CLI section is present but less emphasized. The documentation references PowerShell modules and commands, which are primarily Windows-centric, and lists PowerShell before Azure CLI, which is more cross-platform. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tooling or patterns. The Azure portal instructions are platform-neutral, but the command-line guidance leans toward Windows/PowerShell usage.
Recommendations
  • Add explicit bash shell examples for Azure CLI usage, demonstrating commands in a Linux environment.
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
  • Consider listing Azure CLI before PowerShell in the documentation to reflect its cross-platform nature.
  • Reference installation instructions for Azure CLI on Linux and macOS, not just Windows.
  • Avoid assuming PowerShell as the default scripting environment; mention alternatives where appropriate.
  • If relevant, provide guidance for using REST API or SDKs from Linux environments.
GitHub Create Pull Request
Storage Customer intent: "As a cloud administrator, I want to query storage accounts based on specific case-insensitive or case-sensitive tags, so that I can efficiently manage and locate resources in my environment." ...main/articles/storage/common/includes/azure-storage.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation 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 common. However, the documentation does not provide any Linux-specific shell examples (such as Bash scripts or usage in native Linux environments), nor does it mention Linux tools or patterns. The ordering of examples is Azure CLI first (cross-platform), then PowerShell (Windows-centric), then Portal, which is neutral. There is no explicit Windows-only tool usage, but the lack of Linux-specific examples or discussion of Linux shell integration represents a subtle bias.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, demonstrating how to use az graph query in a Linux shell environment.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any necessary notes about authentication or environment differences.
  • Consider mentioning or linking to documentation about installing and using Azure CLI on Linux.
  • If PowerShell is included, also mention PowerShell Core (pwsh), which is cross-platform, and clarify usage on Linux/macOS.
  • Review for any assumptions about the user's operating system and make instructions OS-agnostic where possible.
GitHub Create Pull Request
← Previous Page 4 of 67 Next →