Storage

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

Bias Trend Over Time

Pages with Bias Issues

392 issues found
Showing 301-325 of 392 flagged pages
Storage Customer-managed keys for account encryption ...icles/storage/common/customer-managed-keys-overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. It references PowerShell as a tool for revoking customer-managed keys, listing it before Azure CLI, and does not provide explicit Linux/macOS-specific instructions or examples. There are no command-line examples or screenshots, but the mention of PowerShell without equal emphasis on Bash or Linux-native tools may create friction for non-Windows users.
Recommendations
  • When referencing tools for management tasks (e.g., revoking keys), list Azure CLI first or equally with PowerShell, as Azure CLI is cross-platform.
  • Provide explicit Bash/Linux/macOS command examples alongside PowerShell, especially for key management and configuration tasks.
  • Clarify that all procedures can be performed on Linux/macOS using Azure CLI, and link to relevant cross-platform guides.
  • Avoid implying PowerShell is the default or preferred tool unless necessary; highlight parity between platforms.
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
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents upgrade instructions using the Azure Portal, PowerShell, and Azure CLI. PowerShell (a Windows-centric tool) is given its own section and example, and is listed before Azure CLI. There are no Linux/macOS-specific shell examples (e.g., Bash), nor is there mention of cross-platform scripting considerations. The CLI example is generic, but PowerShell is highlighted, which may create a perception of Windows preference.
Recommendations
  • Add Bash or shell script examples for Linux/macOS users where appropriate.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Consider listing Azure CLI before PowerShell, as CLI is more platform-agnostic.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell is retained.
  • Add a note or section for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
Storage Check the Last Sync Time property for a storage account ...lob/main/articles/storage/common/last-sync-time-get.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for both PowerShell and Azure CLI, but PowerShell (a Windows-centric tool) is presented first and in greater detail, with explicit module installation instructions. There are no Linux/macOS-specific shell examples (e.g., Bash), nor is there mention of platform differences or parity. The Azure CLI example is cross-platform, but the ordering and emphasis favor Windows/PowerShell users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
  • Add Bash-specific examples or clarify that Azure CLI commands work natively on Linux/macOS terminals.
  • Include a note about platform compatibility for both PowerShell and Azure CLI.
  • If PowerShell is mentioned, clarify that PowerShell Core is available on Linux/macOS, or provide Bash alternatives.
  • Ensure installation instructions for Azure CLI are included or referenced for Linux/macOS users.
GitHub Create Pull Request
Storage Enable infrastructure encryption for double encryption of data ...les/storage/common/infrastructure-encryption-enable.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page presents PowerShell instructions before Azure CLI, and provides detailed PowerShell examples and references to PowerShell modules, which are primarily Windows-centric. The Azure portal instructions are platform-neutral, but the scripting examples and tool references favor Windows users by listing PowerShell first and in greater detail. There is no explicit mention of Linux/macOS-specific patterns or troubleshooting, and no Bash or shell script examples are provided.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Add Bash or shell script examples for Linux/macOS users, especially for verification steps.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide installation/troubleshooting links for those platforms.
  • Balance the depth of PowerShell and CLI instructions, ensuring both are equally detailed.
  • Consider adding a section on using REST API or SDKs for users who prefer non-Windows environments.
GitHub Create Pull Request
Storage Apply an Azure Resource Manager lock to a storage account .../main/articles/storage/common/lock-account-resource.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides step-by-step instructions for applying a Resource Manager lock using the Azure portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, and there is explicit mention of the Az PowerShell module, which is primarily used on Windows. No Linux-specific tools (such as Bash scripts or references to Linux shell environments) are mentioned, and the CLI example is generic but does not highlight Linux usage or parity. The documentation does not provide examples for Linux/macOS-specific environments, nor does it address platform differences in installation or usage of the CLI.
Recommendations
  • Provide Bash or shell script examples for Linux/macOS users, especially for Azure CLI usage.
  • Mention that Azure CLI is cross-platform and can be used on Linux/macOS, with links to installation guides for those platforms.
  • If PowerShell is referenced, clarify that PowerShell Core is available on Linux/macOS and provide installation instructions or examples for those platforms.
  • Consider listing Azure CLI examples before PowerShell to avoid implicit Windows-first bias.
  • Add notes or sections addressing any platform-specific considerations or troubleshooting tips for Linux/macOS users.
GitHub Create Pull Request
Storage Configure passwordless connections between multiple services ...articles/storage/common/multiple-identity-scenarios.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Azure portal instructions and role assignment steps are presented in a generic way, but the local development section references Windows-centric tools (Visual Studio) before mentioning cross-platform alternatives (Azure CLI). The .NET code samples and next steps link to .NET resources first, which may reinforce a Windows-centric workflow. However, all code samples for application implementation are provided for multiple languages and platforms, including Linux-friendly options (Java, Python, Node.js, Spring). No critical steps are Windows-only, and Linux/macOS users can complete all tasks.
Recommendations
  • Explicitly mention cross-platform tools (such as Azure CLI) before or alongside Visual Studio in local development sections.
  • Add notes or links for Linux/macOS users on how to perform Azure portal steps using CLI or automation (e.g., az commands for identity and role assignment).
  • Balance references to .NET and Visual Studio with equivalent resources for other platforms in 'Next steps' and introductory sections.
  • Where screenshots or instructions reference Windows-specific UI, provide CLI or REST API alternatives.
GitHub Create Pull Request
Storage Change how a storage account is replicated ...b/main/articles/storage/common/redundancy-migration.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents Windows-centric tools and patterns, notably by listing PowerShell before Azure CLI in examples and scripts, and by providing detailed PowerShell scripting for batch operations. The use of PowerShell is emphasized, and Windows-style file paths are shown in examples. While Azure CLI is included and examples are provided, the overall structure and order favor Windows/PowerShell users, with Linux/macOS parity present but not prioritized.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, sometimes presenting CLI first.
  • Add explicit Bash script examples for batch operations, using Linux-style file paths and idioms.
  • Clarify that Azure CLI works cross-platform and highlight its usage for Linux/macOS users.
  • Where CSV file handling is shown, provide both Windows (PowerShell) and Linux (Bash/CLI) approaches side-by-side.
  • Avoid Windows-style file paths in CLI/Bash examples; use POSIX paths.
  • Consider adding a short section or note for Linux/macOS users, summarizing key differences or best practices.
GitHub Create Pull Request
Storage Create a resource instance network rule for Azure Storage .../common/storage-network-security-resource-instances.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed PowerShell examples for managing resource instance network rules, with PowerShell presented before Azure CLI. This ordering and emphasis may favor Windows users, as PowerShell is native to Windows and often preferred there. While Azure CLI examples are included and are cross-platform, there are no explicit Linux/macOS-specific notes, nor is there mention of Bash or shell scripting patterns.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Add notes clarifying that Azure CLI commands work on Linux, macOS, and Windows.
  • Include Bash/shell scripting examples or tips for Linux/macOS users where relevant.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell is to be used.
  • Consider adding troubleshooting or environment setup notes for Linux/macOS users.
GitHub Create Pull Request
Storage Create an Azure storage account ...main/articles/storage/common/storage-account-create.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all major tasks, ensuring Linux parity in command-line instructions. However, PowerShell instructions and references are consistently presented before Azure CLI equivalents, and PowerShell is mentioned as a primary method for deploying Bicep and ARM templates, which can create a perception of Windows-first bias. There are no sections that are Windows-only, and Linux/macOS users can complete all tasks using Azure CLI, Cloud Shell, or Terraform. No Windows-exclusive tools or patterns are used, and Cloud Shell (Bash) is highlighted as a cross-platform solution.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI first in some sections to avoid implicit prioritization.
  • Explicitly note that Azure CLI commands work on Linux/macOS and that Cloud Shell is available to all users, reinforcing cross-platform support.
  • Where PowerShell is referenced as a deployment method for Bicep/ARM templates, clarify that Azure CLI is equally supported and provide CLI examples first or side-by-side.
  • Consider adding a short section at the top stating that all command-line instructions are cross-platform unless otherwise noted.
GitHub Create Pull Request
Storage Manage account access keys ...articles/storage/common/storage-account-keys-manage.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for all key management tasks, ensuring Linux parity in command-line instructions. However, PowerShell examples are given before Azure CLI in every section, and PowerShell is a Windows-centric tool. There is no mention of Linux-specific tools or patterns, nor are Linux/macOS users explicitly addressed. The use of PowerShell as the first example and its prominence may create a subtle Windows-first bias.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to reflect its cross-platform nature.
  • Explicitly mention that Azure CLI works on Linux/macOS, and provide installation links or guidance for those platforms.
  • Add a brief note clarifying that PowerShell Core is available on Linux/macOS, if relevant, or recommend Azure CLI for non-Windows users.
  • Consider including a section or callout for Linux/macOS users, highlighting any platform-specific considerations.
GitHub Create Pull Request
Storage Choose an Azure solution for data transfer ...torage/common/storage-choose-data-transfer-solution.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates minor Windows bias by listing PowerShell examples before Azure CLI in the 'Next steps' section and mentioning Azure PowerShell as a scriptable tool before Azure CLI in the main content. No Linux-specific tools or examples are highlighted, but CLI options are present. The bias is subtle and does not prevent Linux/macOS users from completing tasks, as cross-platform tools like AzCopy and Azure CLI are referenced.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples in 'Next steps', sometimes listing CLI first.
  • Explicitly mention that AzCopy and Azure CLI are cross-platform and suitable for Linux/macOS users.
  • Provide links to Linux/macOS-specific quickstarts or documentation where available.
  • Add a brief note clarifying that Azure PowerShell is available on Linux/macOS, or suggest Bash scripting as an alternative.
GitHub Create Pull Request
Storage Introduction to Azure Storage - Cloud storage on Azure ...b/main/articles/storage/common/storage-introduction.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific tools (PowerShell) are mentioned before cross-platform alternatives (Azure CLI), and Windows terminology (SMB, drive letters) is used more frequently and often first. While Linux/macOS support is acknowledged (e.g., NFS, SFTP, Azure Storage Explorer), examples and tool references tend to prioritize Windows or mention Windows tools first. No critical Linux/macOS functionality is missing, but the ordering and emphasis may create friction for non-Windows users.
Recommendations
  • Present Azure CLI examples and references before or alongside Azure PowerShell, as CLI is cross-platform.
  • Explicitly mention Linux/macOS compatibility for all tools and APIs, especially in sections discussing scripting and automation.
  • Provide sample usage scenarios or examples for Linux/macOS environments (e.g., mounting Azure Files with NFS on Linux, using AzCopy on Linux).
  • Balance protocol references (SMB/NFS) so that Linux/macOS protocols are not secondary.
  • Avoid Windows-centric terminology (e.g., 'drive letter') or provide equivalent Linux/macOS context (e.g., mount points).
GitHub Create Pull Request
Storage Set the default public network access rule: Azure Storage .../common/storage-network-security-set-default-access.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents PowerShell instructions before Azure CLI, which may be interpreted as a Windows-first bias. PowerShell is a Windows-centric tool, though it is cross-platform now, but the documentation does not clarify this. There are no Linux/macOS-specific examples or notes, and no mention of shell environments or platform-specific considerations for Azure CLI usage.
Recommendations
  • Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI first to reflect its cross-platform nature.
  • Explicitly state that PowerShell Core is available on Linux/macOS, and provide installation links for those platforms.
  • Add notes or examples for Linux/macOS users, such as shell environment considerations (e.g., quoting, authentication).
  • Include a short table comparing tool availability and platform support.
  • Clarify that Azure CLI is natively supported on Linux/macOS and is often preferred for cross-platform automation.
GitHub Create Pull Request
Storage Copy blobs between Azure storage accounts with AzCopy v10 ...ticles/storage/common/storage-use-azcopy-blobs-copy.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation consistently mentions Windows Command Shell (cmd.exe) in every example tip, specifying that single quotes are used in all shells except Windows, which requires double quotes. However, all command examples are shown with single quotes, which is correct for Linux/macOS shells but not for Windows cmd.exe. There are no PowerShell-specific examples, nor are Windows tools or patterns prioritized beyond quoting conventions. Linux/macOS users are not missing any functionality, but Windows users may need to mentally adapt the examples.
Recommendations
  • Provide explicit Windows cmd.exe examples using double quotes alongside the single-quote examples for Linux/macOS.
  • Add a short section or table summarizing quoting conventions for common shells (bash, zsh, PowerShell, cmd.exe).
  • Consider including PowerShell examples if relevant, or clarify that the examples work in PowerShell as shown.
  • Make it clear in each example which shell the syntax applies to, reducing ambiguity for Windows users.
GitHub Create Pull Request
Storage Grant limited access to data with shared access signatures (SAS) ...b/main/articles/storage/common/storage-sas-overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in the 'Get started with SAS' section, where PowerShell is the first example given for creating a user delegation SAS, and no equivalent Bash or Linux shell example is provided. The rest of the page is largely platform-neutral, focusing on concepts and SDKs available cross-platform. However, the prioritization of PowerShell and lack of explicit Linux shell examples may create friction for Linux/macOS users.
Recommendations
  • Add Bash or Linux shell examples for SAS creation, especially for user delegation SAS, to match the PowerShell example.
  • Alternate the order of examples so that Azure CLI (which is cross-platform) appears before PowerShell, or group them together as 'command-line' options.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide links to installation instructions for non-Windows platforms.
  • Review referenced articles to ensure Linux/macOS parity in step-by-step instructions and screenshots.
GitHub Create Pull Request
Storage Azure Storage encryption for data at rest .../articles/storage/common/storage-service-encryption.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page displays minor Windows bias by referencing BitLocker encryption as a comparison for Azure Storage encryption and linking to the Windows-specific Cryptography API: Next Generation (CNG) for further information about cryptographic modules. These references may be less relevant or familiar to Linux/macOS users, and no equivalent Linux/macOS technologies or documentation are mentioned. However, the page does not provide platform-specific command-line examples or instructions, and the SDK/library guidance is cross-platform.
Recommendations
  • When comparing Azure Storage encryption, mention Linux/macOS equivalents such as LUKS or dm-crypt alongside BitLocker to provide parity for non-Windows users.
  • Provide links to cross-platform or Linux/macOS cryptographic documentation (e.g., OpenSSL, GnuPG, or general AES/FIPS resources) in addition to or instead of Windows-specific CNG documentation.
  • Clarify that Azure Storage encryption is platform-agnostic and does not require any OS-specific configuration or tools.
  • If referencing OS-specific technologies, do so in a way that is inclusive of all major platforms.
GitHub Create Pull Request
Storage Copy from Google Cloud Storage to Azure Storage with AzCopy ...cles/storage/common/storage-use-azcopy-google-cloud.md
Low Priority View Details →
Scanned: 2026-01-12 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. Windows-specific instructions (e.g., environment variable setting) are listed first, and there is a tip about quoting conventions that prioritizes Windows Command Shell (cmd.exe). The documentation references Windows tools and patterns, such as 'set' for environment variables and double quotes for cmd.exe, before mentioning Linux/macOS equivalents. However, all core AzCopy commands are cross-platform and examples are generic, so Linux/macOS users can complete the tasks without major friction.
Recommendations
  • List Linux/macOS instructions before or alongside Windows instructions, or present them in parallel for parity.
  • When discussing quoting conventions, mention Bash/zsh (Linux/macOS) first or equally with Windows cmd.exe.
  • Add explicit notes confirming that AzCopy commands work identically on Linux/macOS, and link to installation instructions for those platforms.
  • Include example shell commands for Linux/macOS (e.g., Bash) where relevant, such as scripting or automation scenarios.
GitHub Create Pull Request
Storage Copy data from Amazon S3 to Azure Storage by using AzCopy .../main/articles/storage/common/storage-use-azcopy-s3.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by listing Windows credential-setting commands first and providing both PowerShell and Command Prompt examples, while Linux/macOS are only given a single export example. Additionally, guidance on quoting in command shells prioritizes Windows (cmd.exe) before mentioning other platforms. However, all AzCopy usage examples are platform-agnostic, and Linux/macOS users can complete all tasks.
Recommendations
  • Present Linux/macOS and Windows credential-setting commands in parallel, or alternate which platform is listed first.
  • Include shell-specific examples for Linux/macOS (e.g., bash, zsh) where relevant, not just generic 'export'.
  • Clarify quoting requirements for Linux/macOS shells (e.g., bash, zsh) alongside Windows cmd.exe, and consider listing Linux/macOS guidance first or equally.
  • Where PowerShell is mentioned, provide equivalent Linux/macOS shell commands if any advanced scripting is shown.
GitHub Create Pull Request
Storage Transfer data to or from Azure Files by using AzCopy v10 ...in/articles/storage/common/storage-use-azcopy-files.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Path Examples Windows Shell Notes
Summary
The documentation provides both Windows (SMB) and Linux (NFS) examples for all major AzCopy operations, using tabbed sections for parity. However, Windows-style paths (e.g., C:\myDirectory) and Windows command shell quoting conventions are consistently presented first in syntax and tips. Notes about shell quoting focus on Windows (cmd.exe) before mentioning Linux/macOS shells. There is a slight preference for Windows examples, but Linux/NFS usage is well covered and explicitly supported where relevant.
Recommendations
  • Alternate the order of Windows and Linux examples so that Linux/NFS is shown first in some sections.
  • Include explicit macOS examples or notes where relevant, especially for quoting and path conventions.
  • Add a summary table at the top indicating platform support for each scenario.
  • Make shell quoting notes more neutral, e.g., 'Use single quotes in most shells; use double quotes in Windows cmd.exe.'
  • Where possible, use generic placeholder paths (e.g., <local-directory-path>) in syntax blocks before showing OS-specific examples.
GitHub Create Pull Request
Storage Optimize the performance of AzCopy v10 with Azure Storage ...articles/storage/common/storage-use-azcopy-optimize.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for setting environment variables, but Windows (cmd.exe and PowerShell) is mentioned first in tips and examples. The tip about quoting uses Windows as the exception, and the Windows example uses PowerShell syntax, which may not be familiar to all Windows users. Linux-specific optimization is mentioned only briefly. Overall, Linux parity is reasonable, but Windows is subtly prioritized in example ordering and tips.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which platform is shown first.
  • Clarify Windows command shell differences (cmd.exe vs PowerShell) and provide examples for both, as PowerShell syntax is not universal for Windows users.
  • Expand Linux/macOS-specific optimization tips, such as filesystem considerations or shell nuances.
  • Ensure all tips and notes mention both platforms equally, rather than treating Windows as the default or exception.
GitHub Create Pull Request
Storage Best practices for configuring an Elastic SAN ...cles/storage/elastic-san/elastic-san-best-practices.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Image Bias
Summary
The documentation generally provides parity between Windows and Linux, offering configuration guidance and examples for both platforms. However, there is a consistent pattern of presenting Windows instructions and screenshots before Linux equivalents, and Windows-specific tools (PowerShell, Registry Editor, iSCSI Initiator app) are referenced directly, sometimes with more detail or visual aids. Linux instructions are present and fairly comprehensive, but often appear after Windows sections and lack equivalent visual walkthroughs.
Recommendations
  • Alternate the order of Windows and Linux sections, or present them side-by-side to avoid implicit prioritization.
  • Provide equivalent screenshots and GUI walkthroughs for Linux where applicable (e.g., updating iSCSI initiator name).
  • Reference Linux-native tools and commands with equal detail and clarity as Windows tools.
  • Include links to Linux documentation or man pages for advanced configuration, similar to the Windows MPIO cmdlet reference.
  • Ensure introductory sections mention Linux and macOS explicitly, not just Windows.
  • Where PowerShell is referenced, also mention Bash/CLI alternatives upfront.
GitHub Create Pull Request
Storage Connect Azure Elastic SAN to Azure Kubernetes over iSCSI ...rticles/storage/elastic-san/elastic-san-connect-aks.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation lists both Azure PowerShell (Windows-centric) and Azure CLI for retrieving volume information, but PowerShell is mentioned first and given a full example before the CLI. The prerequisites also mention Azure PowerShell before Azure CLI. No Linux/macOS-specific tools or instructions are provided, but the CLI is cross-platform and included. All other steps use Kubernetes-native tools and YAML, which are platform-agnostic.
Recommendations
  • List Azure CLI before Azure PowerShell in prerequisites and examples, as CLI is cross-platform.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide installation links for those platforms.
  • Add a note clarifying that PowerShell is primarily for Windows users, while CLI is recommended for Linux/macOS.
  • Consider including a Linux/macOS shell example for retrieving volume information (e.g., using az CLI in bash).
GitHub Create Pull Request
Storage Delete an Azure Elastic SAN ...ain/articles/storage/elastic-san/elastic-san-delete.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by presenting Windows/Powershell instructions and scripts before Linux equivalents in the 'Disconnect volumes from clients' section. PowerShell examples are consistently shown first in all deletion command sections, with Azure CLI (cross-platform) examples following. However, Linux instructions and CLI examples are present and complete, so Linux/macOS users are not blocked.
Recommendations
  • Alternate the order of examples, sometimes showing Azure CLI (Linux/macOS-friendly) commands before PowerShell.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Ensure parity in detail and clarity between Windows and Linux instructions/scripts.
  • Consider grouping platform-neutral instructions together, or providing a summary table for both platforms.
GitHub Create Pull Request
Storage GlusterFS to Azure Files Migration Guide ...in/articles/storage/files/glusterfs-migration-guide.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation generally maintains parity between Windows and Linux, but Windows examples, tools, and troubleshooting steps are consistently presented first. Windows-specific tools (Robocopy) are highlighted before Linux equivalents (rsync/fpsync), and PowerShell/Windows command-line examples are more detailed. Some sections, such as mounting NFS shares on Windows, require WSL, which is a workaround rather than native support.
Recommendations
  • Alternate the order of Windows and Linux sections to avoid consistently prioritizing Windows.
  • Provide equally detailed examples and explanations for Linux tools (e.g., fpsync usage, advanced rsync options).
  • Include troubleshooting steps for Linux tools with the same depth as Windows (e.g., common rsync errors and solutions).
  • Explicitly mention Linux/macOS support in introductory sections to reinforce parity.
  • Where WSL is required for NFS on Windows, clarify limitations and suggest native Linux/macOS as alternatives.
GitHub Create Pull Request
Storage Introduction to Azure Files ...n/articles/storage/files/storage-files-introduction.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific tools (PowerShell, Azure File Sync) are mentioned before or more prominently than Linux/macOS equivalents. PowerShell is referenced as a primary scripting tool, and Windows scenarios (such as Azure File Sync) are described in detail, while Linux/macOS alternatives are less emphasized. However, the page does acknowledge Linux and macOS compatibility and provides links to platform-specific guides.
Recommendations
  • Mention Linux and macOS tooling (e.g., Bash scripts, mount commands) alongside PowerShell when discussing scripting and automation.
  • Provide equal detail for Linux/macOS scenarios, such as mounting shares, using NFS, and managing shares via CLI.
  • Highlight cross-platform tools (e.g., Azure CLI, Storage Explorer) before platform-specific ones.
  • Add examples or references for Linux/macOS equivalents to Azure File Sync, or clarify if such functionality is unavailable.
  • Ensure that platform-specific guides are listed in a neutral order (e.g., alphabetical or grouped by protocol) rather than Windows-first.
GitHub Create Pull Request
← Previous Page 13 of 16 Next →