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 226-250 of 392 flagged pages
Storage Require secure transfer to ensure secure connections ...cles/storage/common/storage-require-secure-transfer.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed PowerShell examples and instructions before CLI examples, which may indicate a Windows-first bias. The PowerShell section is more verbose, with installation and connection steps, while the CLI section is more concise. There are no Linux/macOS-specific instructions or examples, and PowerShell is a Windows-centric tool, though it is available on other platforms. The CLI examples are cross-platform, but the prominence and detail of PowerShell may create friction for Linux/macOS users.
Recommendations
  • Add explicit Linux/macOS instructions for Azure CLI installation and usage.
  • Clarify that Azure CLI is cross-platform and recommend it as the default for non-Windows users.
  • Provide parity in example detail between PowerShell and CLI sections (e.g., include authentication steps for CLI).
  • Consider reordering sections to present CLI examples before PowerShell, or present both side-by-side.
  • Mention that PowerShell Core is available on Linux/macOS, if relevant, and provide installation links.
GitHub Create Pull Request
Storage Azure data transfer options for large datasets, moderate to high network bandwidth ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-large-dataset-moderate-high-network.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools and patterns, such as Robocopy and Azure PowerShell, without mentioning Linux/macOS equivalents. Examples and tool lists prioritize Windows tools (Robocopy, PowerShell) and do not provide parity for Linux users (e.g., rsync, bash, Linux CLI usage). There are no explicit Linux/macOS examples or guidance, which may create friction for non-Windows users.
Recommendations
  • Include Linux/macOS equivalents for all Windows-specific tools mentioned (e.g., suggest rsync or cp as alternatives to Robocopy).
  • Provide example commands for AzCopy, Azure CLI, and REST API usage on Linux/macOS, including shell syntax.
  • Explicitly mention cross-platform compatibility for tools like AzCopy and Azure CLI, and clarify installation steps for Linux/macOS.
  • Add a section or table column indicating OS compatibility for each tool.
  • Avoid listing Windows tools (Robocopy, PowerShell) first or exclusively; balance examples and recommendations for all platforms.
GitHub Create Pull Request
Storage Authorize access for AzCopy with a service principal ...mmon/storage-use-azcopy-authorize-service-principal.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Linux and Windows examples for environment variable setup, but consistently uses PowerShell for prompts and sensitive variable input, even in generic sections. Windows-specific tools (e.g., Export-PfxCertificate) are referenced for certificate export, and PowerShell syntax is shown for secure variable input without equivalent Linux/bash alternatives. In some sections, Windows/PowerShell examples or terminology appear first or exclusively, creating friction for Linux/macOS users.
Recommendations
  • Provide bash/Linux equivalents for secure variable input (e.g., using 'read -s' for secrets) alongside PowerShell examples.
  • Reference cross-platform certificate export tools or provide Linux/macOS instructions for exporting certificates, not just Export-PfxCertificate.
  • Ensure that generic examples (e.g., setting environment variables, prompts) show both bash and PowerShell syntax, or use tabs for parity.
  • Avoid using PowerShell-specific syntax in sections not explicitly marked as Windows-only.
  • Where possible, mention Linux/macOS tools and workflows before or alongside Windows tools.
GitHub Create Pull Request
Storage Call REST API operations with Shared Key authorization .../main/articles/storage/common/storage-rest-api-auth.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by centering its prerequisites and workflow around Visual Studio (a Windows-first IDE), referencing Windows-specific tools like Fiddler, and providing only C# code samples intended for use in Visual Studio. There are no Linux/macOS-specific instructions, alternative IDEs, or cross-platform code samples (e.g., Python, curl, or bash). The guidance assumes a Windows development environment and omits mention of Linux/macOS equivalents for development, debugging, or REST API calls.
Recommendations
  • Add instructions for setting up the sample application on Linux/macOS, including alternative IDEs (e.g., VS Code, JetBrains Rider) and .NET Core CLI usage.
  • Provide code samples in cross-platform languages (e.g., Python, curl, bash) to demonstrate REST API calls outside of C#/Visual Studio.
  • Mention Linux/macOS-compatible network debugging tools (e.g., Wireshark, tcpdump, mitmproxy) alongside Fiddler.
  • Clarify that the REST API can be called from any platform and provide explicit steps or references for non-Windows environments.
  • Include notes on installing .NET Core SDK and running the sample from the command line on Linux/macOS.
GitHub Create Pull Request
Storage Authorize access for AzCopy with a managed identity ...ommon/storage-use-azcopy-authorize-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for environment variable configuration, but consistently references Windows-specific tools (PowerShell, Windows VM configuration) and links to Windows VM setup guides before or instead of Linux equivalents. Azure PowerShell is highlighted as a primary authentication method, and the use of PowerShell syntax is prevalent. There is a lack of parity in references to Linux VM configuration and Linux-native authentication tooling, and Windows terminology (e.g., 'system-wide managed identity on your VM' with links to Windows VM docs) is used throughout.
Recommendations
  • Add explicit references and links to Linux VM managed identity configuration guides alongside Windows VM links.
  • Ensure that Linux examples are presented with equal prominence and detail as Windows/PowerShell examples.
  • Include Bash shell examples for all environment variable and authentication steps, not just PowerShell.
  • Mention Linux-native secret stores (e.g., GNOME Keyring, KWallet) and provide troubleshooting steps for Linux users where AzCopy login may fail due to missing keyring.
  • Clarify that AzCopy works cross-platform and note any OS-specific caveats or requirements.
  • Avoid using Windows terminology as the default (e.g., 'system-wide managed identity on your VM') and instead use OS-neutral phrasing.
GitHub Create Pull Request
Storage Download blobs from Azure Blob Storage by using AzCopy v10 ...es/storage/common/storage-use-azcopy-blobs-download.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style paths (e.g., 'C:\myDirectory\myTextFile.txt') in all command examples, and does not provide any Linux/macOS path examples (such as '/home/user/myTextFile.txt'). While there are notes about quoting differences between shells, all concrete examples use Windows paths and directory conventions. No Linux or macOS-specific examples or guidance are provided.
Recommendations
  • Provide parallel examples using Linux/macOS file paths (e.g., '/home/user/myTextFile.txt') alongside Windows examples.
  • Explicitly mention and show how to run AzCopy commands in bash/zsh shells, including quoting and path conventions.
  • Add a section or note clarifying cross-platform usage, with sample commands for Linux/macOS users.
  • Ensure that all examples show both Windows and Linux/macOS variants where file paths or shell behavior differ.
GitHub Create Pull Request
Storage Find errors & resume jobs with logs in AzCopy (Azure Storage) ...rticles/storage/common/storage-use-azcopy-configure.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. In the 'Review the logs for errors' section, the only example provided for both Linux and Windows uses the PowerShell 'Select-String' command, which is not natively available on most Linux distributions. No Linux-native alternative (such as 'grep') is given. Additionally, the Windows example is shown first in some sections, and tips about quoting are Windows-centric. Other sections do provide both Windows and Linux environment variable examples, but the lack of Linux-native log parsing commands is a notable omission.
Recommendations
  • Provide Linux-native command examples (e.g., use 'grep UPLOADFAILED ./logfile.log' for log parsing on Linux/macOS).
  • Ensure Linux/macOS examples are shown before or alongside Windows examples, not after.
  • Clarify when commands are PowerShell-specific and offer alternatives for bash/zsh.
  • Expand tips to cover Linux/macOS shell quoting conventions equally.
GitHub Create Pull Request
Storage Use AzCopy v10 in scripts and scheduled transfers ...rticles/storage/common/storage-use-azcopy-in-script.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides both Linux and Windows examples for scheduling AzCopy tasks, but Windows tools (Schtasks) are described in greater detail, with parameter breakdowns and additional links. Windows-specific scripting considerations (escaping characters in .cmd files) are covered, while Linux equivalents (e.g., escaping in bash scripts) are not mentioned. The order of presentation sometimes puts Windows tools and patterns first or gives them more explanation. There is also a minor focus on PowerShell/Command Prompt for Windows, but no Linux shell scripting nuances.
Recommendations
  • Provide equal detail for Linux scheduling tools (e.g., explain cron parameters and link to official cron documentation).
  • Add a section on escaping special characters in Linux shell scripts, similar to the Windows batch file guidance.
  • Ensure that both Linux and Windows examples are presented with similar depth and clarity.
  • Include macOS-specific notes if there are differences from Linux.
  • When mentioning tools, provide cross-platform alternatives or note parity.
GitHub Create Pull Request
Storage Copy or move data to Azure Storage by using AzCopy v10 ...main/articles/storage/common/storage-use-azcopy-v10.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation generally presents AzCopy as a cross-platform tool, but there is a subtle Windows bias. The only explicit example command uses a Windows-style path (C:\local\path), and no Linux/macOS path example is provided. In the SAS token section, the example command is Windows-centric. In download instructions, Windows links are listed before Linux and macOS, and zip file decompression is explained for Windows/macOS, while Linux users are told to consult their own documentation. There are no PowerShell-specific examples or Windows-only tools mentioned, but the ordering and example choices favor Windows users.
Recommendations
  • Provide parallel example commands using Linux/macOS path syntax (e.g., /home/user/path) alongside Windows examples.
  • Alternate or randomize the order of OS download links, or group them by platform rather than listing Windows first.
  • Include explicit instructions or examples for decompressing tar files on Linux (e.g., using 'tar -xvf').
  • Where command syntax differs (e.g., path separators), clarify with notes or side-by-side examples.
  • Ensure all example commands and shell usage are shown for both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh).
GitHub Create Pull Request
Storage Configure Transport Layer Security (TLS) for a client application ...n/transport-layer-security-configure-client-version.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias: all code examples are for PowerShell and .NET (both primarily Windows-centric), with no Linux/macOS shell or programming language examples. The verification step recommends Fiddler, a Windows-only tool, without mentioning Linux/macOS alternatives. No guidance is provided for configuring TLS in common Linux environments or tools.
Recommendations
  • Add examples for configuring TLS in Linux/macOS environments, such as Bash scripts, Python, or Java.
  • Include instructions for setting TLS versions using common Linux tools (e.g., curl, openssl, Python requests).
  • Mention cross-platform network traffic analysis tools (e.g., Wireshark, tcpdump) alongside Fiddler.
  • Present examples for both Windows and Linux/macOS side-by-side, or alternate which platform is shown first.
GitHub Create Pull Request
Storage Migrate to Transport Layer Security (TLS) 1.2 for Azure Blob Storage ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-migrate-to-TLS2.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Quick Tips and examples focus on Windows OS versions and .NET Framework, with no mention of Linux/macOS equivalents. Tools listed (Fiddler, Visual Studio, PowerShell) are Windows-centric, and guidance for enabling TLS 1.2 is primarily for Windows environments. There are no instructions or examples for Linux/macOS clients, nor references to common Linux tools or configuration patterns.
Recommendations
  • Add explicit guidance for Linux and macOS users, including how to verify and enforce TLS 1.2 in common environments (e.g., OpenSSL, curl, wget, Python, Java).
  • Include Linux/macOS-specific quick tips, such as default TLS versions in major distributions and how to update OpenSSL or system libraries.
  • List cross-platform tools for TLS analysis (e.g., openssl s_client, curl --tlsv1.2) alongside Windows tools.
  • Provide code/configuration examples for popular Linux/macOS programming languages and frameworks.
  • Reorder sections or examples so that Windows and Linux/macOS are presented with equal prominence.
GitHub Create Pull Request
Storage Create multiple Azure Elastic SAN volumes in a batch ...storage/elastic-san/elastic-san-batch-create-sample.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively provides a PowerShell script for batch creation of Azure Elastic SAN volumes, with no mention of Linux/macOS alternatives (such as Bash, Azure CLI, or cross-platform scripting). The file path example and tooling are Windows-centric, and there is no guidance for users on non-Windows platforms.
Recommendations
  • Add equivalent examples using Azure CLI and/or Bash scripts for Linux/macOS users.
  • Include notes on how to adapt file paths for Linux/macOS (e.g., /home/user/ElasticSan/TestCsv3.csv).
  • Mention cross-platform tools and scripting options, and clarify any platform-specific requirements.
  • Provide guidance on installing and using Azure PowerShell on Linux/macOS, if PowerShell is required.
GitHub Create Pull Request
Storage Configure Service Endpoints for Azure Elastic SAN ...elastic-san/elastic-san-configure-service-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI, but there are no explicit Linux/macOS shell examples (e.g., bash), and variable syntax in CLI examples uses Windows-style ($Var) rather than POSIX-style (Var=Value). PowerShell is mentioned before CLI in several places, and instructions for installing Azure PowerShell are listed before Azure CLI. There are no references to Linux-specific tools or shell environments, and no guidance for Linux/macOS users regarding shell syntax differences.
Recommendations
  • Add explicit bash/zsh shell examples for Azure CLI commands, using POSIX variable syntax (e.g., RgName="ResourceGroupName") instead of $RgName.
  • Include notes or sections clarifying differences in variable usage between Windows (PowerShell) and Linux/macOS (bash/zsh) environments.
  • Ensure CLI examples use cross-platform compatible syntax and avoid PowerShell-specific conventions.
  • Present CLI and PowerShell instructions in parallel, or alternate their order, rather than consistently listing PowerShell first.
  • Add references to Linux/macOS prerequisites (e.g., bash, zsh, or terminal usage) where relevant.
GitHub Create Pull Request
Storage Use clustered applications on Azure Elastic SAN ...cles/storage/elastic-san/elastic-san-shared-volumes.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions Windows Server Failover Cluster (WSFC) as the first example of a cluster manager, with Pacemaker (Linux) only as a secondary mention. There are no concrete examples, scripts, or step-by-step instructions for either platform, but the ordering and emphasis suggest a Windows-first bias. No Linux-specific tools, commands, or patterns are described, and there are no examples for Linux users to follow.
Recommendations
  • Provide explicit step-by-step examples for both Windows (WSFC) and Linux (Pacemaker) cluster setups.
  • Include sample scripts or commands for Linux environments, such as using 'sg_persist' or other SCSI-3 PR utilities.
  • Ensure that Linux tools and workflows are described with equal detail and prominence as Windows equivalents.
  • Consider alternating the order of Windows and Linux mentions, or grouping them together to avoid perceived prioritization.
GitHub Create Pull Request
Storage Troubleshoot Azure Elastic SAN ...ticles/storage/elastic-san/elastic-san-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides both Windows and Linux troubleshooting steps, but there are several instances of Windows bias. Windows tools (iscsicli, mpclaim, PowerShell scripts) are mentioned explicitly and sometimes before their Linux equivalents. Windows-specific instructions and links are often given first, and PowerShell usage is highlighted for parameter changes. Linux examples are present, but Windows patterns and terminology are more prominent.
Recommendations
  • Ensure Linux and Windows instructions/examples are presented in parallel, with equal prominence.
  • When listing tools or scripts, alternate which platform is mentioned first, or present them side-by-side.
  • Provide Linux-specific command examples (e.g., for session limits, configuration changes) with the same detail as Windows.
  • Avoid referencing PowerShell or Windows portal options exclusively; always include the Linux CLI or configuration file equivalent.
  • Where scripts are linked, ensure Linux scripts are as visible and accessible as Windows scripts.
  • Consider adding macOS troubleshooting steps if supported.
GitHub Create Pull Request
Storage Best practices for disaster recovery with Azure File Sync ...ile-sync/file-sync-disaster-recovery-best-practices.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page for Azure File Sync disaster recovery best practices demonstrates a notable Windows bias. It references Windows-specific tools and patterns (such as Volume Shadow Copy Service, Previous Versions tab, and PowerShell) without mentioning Linux/macOS equivalents or alternatives. All operational examples and instructions assume a Windows environment, with no guidance for Linux or macOS users. This creates friction for non-Windows users attempting to implement disaster recovery solutions.
Recommendations
  • Explicitly state platform requirements and limitations for Azure File Sync (e.g., if agent/server endpoint is Windows-only).
  • If Linux/macOS support exists, provide equivalent instructions and examples for those platforms.
  • Where Windows-specific tools (VSS, Previous Versions, PowerShell) are mentioned, clarify their platform scope and suggest Linux/macOS alternatives (e.g., rsync, LVM snapshots, cron jobs for backup).
  • Add a section outlining disaster recovery strategies for organizations using non-Windows file servers, or clarify that Azure File Sync is not supported on those platforms.
  • Ensure parity in example ordering, presenting cross-platform options or noting platform exclusivity.
GitHub Create Pull Request
Storage Configure Azure File Sync network endpoints ...es/storage/file-sync/file-sync-networking-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Azure File Sync is described as a solution for 'Windows file servers,' and most conceptual explanations and examples assume Windows as the primary platform. PowerShell is heavily featured, with detailed scripts and output shown for Windows. Some sections, such as testing private endpoints for Storage Sync Service, only provide PowerShell instructions and outputs, with no equivalent Linux/macOS CLI or shell examples. The Azure CLI is supported for most tasks, but in at least one critical area (disabling Storage Sync Service public endpoint), the CLI is not supported and users are directed to PowerShell, which is Windows-centric. Output samples are often shown for Windows, and references to 'Windows file servers' reinforce the platform bias.
Recommendations
  • Provide equivalent Linux/macOS examples for all PowerShell-only instructions, especially for testing and verification steps.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and offer alternatives where possible.
  • Explicitly mention limitations of Azure CLI for Linux/macOS users and suggest workarounds or roadmap for parity.
  • Include output samples from Linux/macOS terminals alongside Windows examples.
  • Acknowledge that Azure File Sync is currently Windows-only, but ensure networking documentation is inclusive for all platforms where possible.
GitHub Create Pull Request
Storage Enable access to Azure file shares using OAuth over REST ...ob/main/articles/storage/files/authorize-oauth-rest.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and instructions are provided in detail, with explicit step-by-step guidance and command samples. Windows-centric tools (PowerShell, AzCopy, Storage Explorer) are mentioned before their Linux/macOS equivalents, and the PowerShell section precedes the Azure CLI section. There are no Linux/macOS-specific examples or notes about platform differences, and the CLI instructions do not address Linux/macOS nuances or alternative shell usage.
Recommendations
  • Add explicit Linux/macOS examples for Azure CLI, including shell-specific notes (e.g., bash, zsh).
  • Mention cross-platform tools (AzCopy, Storage Explorer) with installation and usage notes for Linux/macOS.
  • Reorder sections so that platform-neutral or cross-platform tools (CLI, SDKs) are presented before Windows-specific tools like PowerShell.
  • Include troubleshooting notes or caveats for Linux/macOS users, such as file path conventions and authentication differences.
  • Clarify that PowerShell Core is available on Linux/macOS and provide installation instructions if PowerShell examples are retained.
GitHub Create Pull Request
Storage Data Protection Overview for Azure Files ...ticles/storage/files/files-data-protection-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell is given its own section and is listed before Azure CLI and REST API. The use of Azure File Sync—a Windows Server-only tool—is recommended for hybrid cloud backups, with no mention of Linux alternatives. There are no explicit Linux/macOS examples or references to Linux-specific tools or workflows, and the documentation does not clarify cross-platform compatibility for backup and restore operations.
Recommendations
  • Add explicit Linux/macOS examples for backup and restore operations, especially using Azure CLI and REST API.
  • Clarify the cross-platform compatibility of Azure Files features and tools.
  • Mention that Azure File Sync is Windows Server-only and suggest alternative approaches for Linux file servers (e.g., rsync to Azure Files, third-party backup tools, or native NFS support).
  • Ensure that CLI examples are shown before or alongside PowerShell examples to avoid Windows-first impression.
  • Include a section on mounting and backing up Azure Files from Linux systems, covering both SMB and NFS scenarios.
GitHub Create Pull Request
Storage Use Managed Identities with Azure Files (preview) ...ain/articles/storage/files/files-managed-identities.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. Windows and PowerShell examples are presented first and in greater detail, especially in the initial setup and configuration sections. The use of PowerShell is emphasized for core resource creation and management tasks, with Linux CLI examples only appearing later and in separate tabs. Windows-specific tools (e.g., AzFilesSmbMIClient, PowerShell modules) are described in depth, while Linux equivalents are mentioned but with less prominence. The documentation also notes that system assigned managed identities are not supported on Linux, which is an Azure platform limitation rather than documentation bias.
Recommendations
  • Provide Azure CLI or Bash examples for resource creation and configuration alongside PowerShell, especially in the 'Configure the managed identity access property on your storage account' section.
  • Present Windows and Linux instructions in parallel or with equal prominence, rather than defaulting to Windows-first ordering.
  • Include explicit guidance for Linux users in troubleshooting and client library integration sections, matching the detail given for Windows.
  • Where possible, avoid assuming PowerShell as the default tool and offer cross-platform alternatives.
  • Clarify Azure platform limitations (e.g., system assigned managed identities on Linux) as product constraints, not documentation gaps.
GitHub Create Pull Request
Storage Data Redundancy in Azure Files ...s/blob/main/articles/storage/files/files-redundancy.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell is presented before Azure CLI in the region supportability section, and the PowerShell example is significantly more detailed. Windows-specific tools and patterns (such as Azure File Sync with Windows file server) are referenced as primary solutions for geo-redundancy with SSD file shares. While Linux parity is addressed via Azure CLI and mentions of AzCopy, Windows tools and workflows are generally described first and in greater detail.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell, with equal detail and explanation.
  • Expand Linux/macOS guidance for geo-redundancy scenarios, including explicit instructions for using AzCopy and mounting Azure Files on Linux.
  • Include references to Linux file servers and NFS-based disaster recovery workflows, not just Windows File Sync.
  • Ensure all scripts and examples are available for both platforms, and clarify any platform-specific limitations.
  • Add links to Linux/macos-specific documentation where relevant.
GitHub Create Pull Request
Storage SMB file shares in Azure Files ...blob/main/articles/storage/files/files-smb-protocol.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 a moderate Windows bias. Windows scenarios and tools (PowerShell, registry edits, Set-SmbClientConfiguration) are mentioned first and in greater detail, especially for advanced SMB features and security configuration. PowerShell is the primary scripting example, and Windows-specific troubleshooting steps are provided, while equivalent Linux/macOS guidance is missing. There are no examples for configuring SMB Multichannel or SMB security settings on Linux/macOS clients, nor discussion of Linux-specific SMB client behaviors or limitations.
Recommendations
  • Add Linux and macOS client configuration examples for SMB Multichannel and SMB security settings, including how to select encryption ciphers and protocol versions using smb.conf or mount options.
  • Include troubleshooting steps for older Linux distributions or Samba versions, analogous to the Windows registry/patch guidance.
  • Discuss Linux/macOS SMB client compatibility, including minimum Samba versions required for features like SMB Multichannel and encryption.
  • Present cross-platform examples in parallel (Windows, Linux, macOS) rather than Windows-first.
  • Reference Linux/macOS tools (e.g., smbclient, mount.cifs, Samba configuration) where PowerShell or Windows tools are used.
GitHub Create Pull Request
Storage Develop for Azure Files with .NET ...icles/storage/files/storage-dotnet-how-to-use-files.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the 'Work with Azure Files using System.IO' section, where all code examples use Windows-style paths (e.g., Z:\file-share) and reference mounting SMB shares on Windows. No Linux/macOS path examples or code snippets are provided, despite Azure Files supporting SMB/NFS on Linux. While links to Linux mounting guides are present, practical .NET code examples for Linux/macOS environments are missing.
Recommendations
  • Add equivalent code examples using Linux/macOS path formats (e.g., '/mnt/file-share') alongside Windows examples.
  • Explicitly mention that the System.IO approach works on Linux/macOS if the share is mounted, and provide sample mounting commands and code.
  • Where file system operations are shown, clarify any OS-specific differences (e.g., path separators, permissions).
  • Ensure that examples and explanations do not assume Windows as the default environment.
GitHub Create Pull Request
Storage What's New in Azure Files and Azure File Sync ...cs/blob/main/articles/storage/files/files-whats-new.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Files and Azure File Sync exhibits a moderate Windows bias. Windows tools (PowerShell, Windows Server) and terminology are frequently mentioned, often before Linux equivalents. Many new features and enhancements reference Windows Server or PowerShell management, with Linux alternatives either omitted or mentioned later. Some sections (e.g., Azure File Sync agent via Azure Arc) are Windows-only, and examples or instructions for Linux are sparse or missing, especially for sync scenarios.
Recommendations
  • Ensure all management instructions (e.g., agent installation, sync setup) include Linux equivalents or clarify platform limitations.
  • Provide Linux-specific examples for Azure CLI, REST API, and NFS features where only PowerShell or Windows tools are referenced.
  • When listing new features, explicitly state Linux/macOS compatibility and provide parity guidance.
  • Avoid listing Windows tools or terminology before Linux alternatives unless there is a technical reason.
  • Add links to Linux/macOS documentation where relevant, especially for SMB/NFS mounting, authentication, and backup.
GitHub Create Pull Request
Storage Improve SMB Azure File Share Performance ...cs/blob/main/articles/storage/files/smb-performance.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Windows and Linux coverage for SMB Multichannel, including a Linux mount example and supported kernel versions. However, Windows configuration and verification steps are more detailed, with PowerShell commands and Windows-specific tools (robocopy, diskspd.exe) featured prominently. Registration instructions for features use Azure PowerShell only, with no Linux CLI or Bash alternatives. Windows documentation is referenced more frequently and is listed as a next step, while Linux equivalents are not. Performance testing examples use Windows tools exclusively.
Recommendations
  • Add equivalent Linux CLI commands for feature registration (e.g., using Azure CLI or Bash).
  • Include Linux-based performance testing examples (e.g., using fio or dd) alongside diskspd.exe and robocopy.
  • Provide Linux-specific troubleshooting and verification steps for SMB Multichannel (e.g., checking mount status, kernel flags, or using smbstatus).
  • Reference Linux documentation or community resources in the 'Next steps' section.
  • Balance the order of presentation so Linux and Windows instructions/examples are shown together or alternately, rather than Windows first.
GitHub Create Pull Request
← Previous Page 10 of 16 Next →