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 126-150 of 392 flagged pages
Storage GPv1 ZRS standard account retirement FAQ ...-zone-redundant-storage-migration-freq-asked-questions.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation references PowerShell and the Azure CLI as upgrade tools, but PowerShell is mentioned first and more prominently. There are no explicit Linux/macOS examples or tool recommendations (e.g., Bash, shell scripts), and the CLI is not described in detail. The upgrade process is described generically, but the emphasis on PowerShell and lack of Linux-specific guidance or parity examples creates a mild Windows bias.
Recommendations
  • Provide explicit Linux/macOS examples using Azure CLI (az) commands, including sample upgrade commands.
  • Mention Bash or shell scripting as alternatives for automation, alongside PowerShell.
  • Ensure CLI instructions are given equal prominence to PowerShell, or list CLI first when describing upgrade options.
  • Clarify that PowerShell is available cross-platform, but highlight CLI as the preferred tool for Linux/macOS users.
  • Add troubleshooting steps or notes relevant to Linux environments (e.g., authentication, environment setup).
GitHub Create Pull Request
Storage Configure an expiration policy for shared access signatures (SAS) .../main/articles/storage/common/sas-expiration-policy.md
Medium 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 provides configuration instructions for SAS expiration policy using the Azure portal, PowerShell, and Azure CLI. PowerShell examples and references are given before Azure CLI, and the PowerShell section is more detailed, including verification steps and tips. The documentation references PowerShell-specific cmdlets and patterns, which are primarily Windows-centric. There are no explicit Linux/macOS shell examples (e.g., Bash), nor is there mention of cross-platform scripting considerations. The Azure portal instructions are platform-neutral, but command-line guidance leans toward Windows/PowerShell.
Recommendations
  • Add explicit Bash examples for Azure CLI commands, demonstrating usage on Linux/macOS (e.g., with environment variables, quoting, etc.).
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Present Azure CLI instructions before PowerShell, or in parallel, to avoid Windows-first bias.
  • Include notes or links for installing and using Azure CLI on Linux/macOS.
  • Consider adding troubleshooting steps or tips relevant to Linux/macOS environments.
GitHub Create Pull Request
Storage Prevent authorization with Shared Key ...les/storage/common/shared-key-authorization-prevent.md
Medium 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 demonstrates a moderate Windows bias. While it provides Azure CLI examples (which are cross-platform), PowerShell is given its own dedicated section and is listed before the Azure CLI. Additionally, the documentation frequently references the Azure portal and Azure PowerShell, both of which are more familiar to Windows users. There are no explicit Linux/macOS-specific instructions or screenshots, and some linked resources (e.g., Storage Explorer, PowerShell) may default to Windows-centric guidance.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is natively cross-platform.
  • Explicitly mention that Azure CLI and Azure portal are supported on Linux/macOS.
  • Where referencing tools like Storage Explorer or Cloud Shell, clarify cross-platform compatibility and provide Linux/macOS-specific links or notes if behavior differs.
  • Add bash/zsh shell command examples where relevant (e.g., using curl or REST API calls).
  • Ensure screenshots and instructions for the Azure portal do not assume a Windows environment.
GitHub Create Pull Request
Storage Upgrade to a general-purpose v2 storage account ...ain/articles/storage/common/storage-account-upgrade.md
Medium 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 for Azure Storage accounts using the Azure portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, and PowerShell is a Windows-centric tool. There are no explicit Linux/macOS-specific instructions or examples, and the CLI example is generic. No Linux-specific tools or shell commands are mentioned, and installation instructions for Azure CLI do not reference Linux/macOS directly.
Recommendations
  • Add explicit Linux/macOS installation instructions or links for Azure CLI.
  • Provide bash or shell script examples for Linux/macOS users where appropriate.
  • Ensure Azure CLI instructions are presented before or alongside PowerShell, as CLI is cross-platform.
  • Clarify that Azure CLI works on Linux/macOS and provide troubleshooting tips for those platforms.
  • Consider including screenshots or references for Linux/macOS environments in portal instructions.
GitHub Create Pull Request
Storage Network Connections in Azure Storage Explorer ...in/articles/storage/common/storage-explorer-network.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation discusses proxy configuration in Azure Storage Explorer but does not provide OS-specific instructions or examples for Linux or macOS. The 'system proxy' section references Chromium's use of 'system network settings' without clarifying how users on Linux or macOS should configure these settings. Additionally, the guidance to 'try system proxy first' assumes familiarity with Windows-style system proxy configuration, and no Linux/macOS tools or patterns (such as GNOME/KDE proxy settings or environment variable management) are mentioned.
Recommendations
  • Add explicit instructions or links for configuring system proxy settings on Linux (e.g., GNOME, KDE, environment variables) and macOS (e.g., System Preferences > Network > Proxies).
  • Provide examples or screenshots for proxy configuration on non-Windows platforms.
  • Clarify how Chromium networking stack interacts with system proxy settings on Linux and macOS.
  • Mention common Linux/macOS tools or commands for setting environment variables (e.g., export HTTP_PROXY=...) and system-wide proxy settings.
GitHub Create Pull Request
Storage Azure Storage Analytics logging ...n/articles/storage/common/storage-analytics-logging.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is the only scripting example provided for filtering log blobs, with no equivalent shown for Bash, Azure CLI, or other Linux/macOS-friendly tools. References to storage browsing tools and programmatic access are generic, but the only concrete example is PowerShell. Additionally, example log entries repeatedly mention Windows-specific user agents (e.g., 'win32', 'Windows_NT'), and Windows tools (AzCopy, Azure Storage Explorer) are prominent in sample metadata and log entries. The order of tool mentions and examples tends to favor Windows-first approaches.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for log blob filtering and metadata inspection.
  • Explicitly mention and give examples for Linux/macOS-compatible tools (e.g., AzCopy for Linux, Azure CLI, REST API usage with curl/jq).
  • Balance user agent and tool references in log entry examples to include Linux/macOS environments.
  • When listing options for enabling Storage Analytics, mention Azure CLI and REST API before or alongside PowerShell.
  • Add a note clarifying that all operations can be performed cross-platform, and link to platform-specific guides where available.
GitHub Create Pull Request
Storage Initiate a storage account failover ...es/storage/common/storage-initiate-account-failover.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed PowerShell instructions and troubleshooting, including module installation and usage, which are specific to Windows environments. PowerShell is presented before Azure CLI, and there is a heavy emphasis on PowerShell commands, module management, and compatibility issues that are largely relevant to Windows users. There are no explicit Linux/macOS command-line examples (e.g., Bash), nor are there notes about platform differences for CLI usage. The Azure CLI instructions are present and sufficient for Linux/macOS users, but PowerShell receives more attention and detail.
Recommendations
  • Add explicit notes clarifying that Azure CLI commands work cross-platform (Windows, Linux, macOS), and highlight any platform-specific considerations.
  • Provide Bash shell examples for Azure CLI usage, including environment setup and command invocation, to demonstrate Linux parity.
  • Balance the level of detail between PowerShell and Azure CLI sections, ensuring troubleshooting and module installation guidance is equally robust for CLI users.
  • Consider mentioning that PowerShell Core is available on Linux/macOS, and provide installation steps if relevant.
  • List Azure CLI instructions before PowerShell, or present both options equally, to avoid Windows-first bias.
GitHub Create Pull Request
Storage AzCopy v10 configuration setting (Azure Storage) ...ge/common/storage-ref-azcopy-configuration-settings.md
Medium Priority View Details →
Scanned: 2026-01-12 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 moderate Windows bias. Windows-specific behaviors and instructions are frequently mentioned first, with PowerShell and CMD examples provided in detail, while Linux/macOS examples are less emphasized or grouped together. Some environment variables and features are described primarily in terms of their Windows behavior, and proxy configuration/bypass instructions are much more detailed for Windows than for Linux/macOS.
Recommendations
  • Present Linux/macOS examples before or alongside Windows examples, rather than after.
  • Expand Linux/macOS sections with equivalent detail, especially for proxy bypass instructions.
  • Clarify platform-specific behaviors for all environment variables, not just Windows.
  • Include shell-specific examples for Linux (e.g., bash, zsh) and macOS where relevant.
  • Avoid language that assumes Windows as the default platform (e.g., 'by default AzCopy on Windows...').
  • Ensure parity in troubleshooting and configuration guidance for non-Windows platforms.
GitHub Create Pull Request
Storage Azure data transfer options for small datasets with low to moderate network bandwidth ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-small-dataset-low-moderate-network.md
Medium 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 lists Azure PowerShell as a primary scripting/programmatic tool alongside AzCopy and Azure CLI, but does not mention Linux/macOS equivalents (e.g., Bash scripting, shell integration) or provide parity in examples. PowerShell is a Windows-centric tool, and its mention before Azure CLI (which is cross-platform) suggests a Windows-first bias. No explicit Linux/macOS examples or tools are highlighted in the scripting section.
Recommendations
  • Explicitly mention Bash/shell scripting as a supported method for Linux/macOS users when discussing programmatic/scripting tools.
  • Provide example commands for both PowerShell and Bash/Azure CLI to illustrate parity.
  • Reorder the scripting/programmatic tools section to list cross-platform tools (AzCopy, Azure CLI) before Windows-centric tools (PowerShell).
  • Clarify that Azure CLI and AzCopy are fully supported on Linux/macOS and provide links to installation guides for those platforms.
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-12 00:00
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, Azure PowerShell) and links to Windows VM configuration guides before or instead of Linux equivalents. The instructions for enabling managed identity on VMs link only to Windows VM guides, and the use of PowerShell is prominent throughout. Azure CLI is shown for Linux, but the Windows example uses PowerShell and a different login type, which may confuse users. There are no explicit Linux VM setup instructions or parity in referenced guides.
Recommendations
  • Add links and instructions for configuring managed identities on Linux VMs, not just Windows VMs.
  • Ensure that referenced guides and quickstarts include both Linux and Windows VM scenarios.
  • Provide parity in environment variable examples, especially for Azure CLI usage on Windows (not just PowerShell).
  • Clarify differences in AZCOPY_AUTO_LOGIN_TYPE values between platforms and explain why they differ.
  • Include notes or sections for macOS users where relevant.
  • Avoid using Windows/PowerShell terminology as the default; present Linux/macOS options first or side-by-side.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-centric tools and patterns (e.g., Robocopy, Azure PowerShell) are mentioned, and examples or references to Linux/macOS equivalents are missing. Windows tools are listed first in tables and descriptions, while Linux-native options (e.g., rsync, bash, Linux file systems) are not discussed. There is no guidance for Linux/macOS users on how to perform offline or online transfers, nor are cross-platform command examples provided.
Recommendations
  • Include Linux/macOS equivalents for file copy operations, such as mentioning rsync, cp, or scp alongside Robocopy.
  • Provide explicit examples for AzCopy usage on Linux/macOS, including installation and command-line syntax.
  • Mention that Azure CLI and AzCopy are cross-platform, and clarify any OS-specific limitations or steps.
  • Add guidance for using offline transfer devices (Data Box family) with Linux/macOS, including supported file systems and mounting instructions.
  • Balance tables and descriptions by listing cross-platform tools first or in parallel, rather than Windows-specific tools.
  • Add troubleshooting notes or links for Linux/macOS users, especially for device drivers, file system compatibility, and permissions.
GitHub Create Pull Request
Storage Authorize access for AzCopy with a user identity ...e/common/storage-use-azcopy-authorize-user-identity.md
Medium 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 provides both Linux (bash) and Windows (PowerShell) examples for environment variable setup, but Windows/PowerShell is consistently presented alongside or before Linux, and PowerShell is the only shell shown for Azure PowerShell integration. Azure PowerShell is highlighted as a primary method, which is Windows-centric, and there are no macOS-specific notes or bash/zsh equivalents for PowerShell commands. The documentation assumes familiarity with Windows tools and patterns, and Linux/macOS users may need to adapt instructions.
Recommendations
  • Present Linux/bash examples before Windows/PowerShell examples to avoid implicit prioritization.
  • Add explicit macOS guidance, especially for environment variable setup and shell differences.
  • For Azure PowerShell integration, clarify cross-platform support and provide bash/zsh equivalents where possible.
  • Note any platform-specific limitations (e.g., secret store support) more prominently.
  • Ensure parity in troubleshooting steps and links for both Linux and Windows users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively provides a Windows 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 example uses a Windows file path and does not address how Linux users could perform the same task.
Recommendations
  • Add an equivalent example using Azure CLI or Bash script for Linux/macOS users.
  • Use cross-platform file path examples or clarify how to adapt file paths for different operating systems.
  • Explicitly mention that the PowerShell script can be run on PowerShell Core on Linux/macOS, if applicable.
  • Include notes or links to documentation for Linux/macOS users on how to install and use Azure PowerShell or CLI.
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-12 00:00
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 examples and does not provide equivalent Linux/macOS examples (e.g., '/home/user/myTextFile.txt'). Windows paths are shown exclusively, and the guidance for quoting paths prioritizes Windows (cmd.exe) in tips, but does not offer concrete Linux/macOS examples. This creates friction for non-Windows users who must mentally translate examples to their platform.
Recommendations
  • Provide parallel examples for Linux/macOS, using POSIX-style paths (e.g., '/home/user/myTextFile.txt') alongside Windows examples.
  • Explicitly mention Linux/macOS shells (bash, zsh) in tips about quoting, and show both single-quote and double-quote usage in context.
  • Where path separators or conventions differ, call out the differences and provide guidance.
  • Consider alternating the order of examples or grouping by platform to avoid Windows-first bias.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias in several areas. The log review example uses PowerShell's Select-String in both Linux and Windows tabs, omitting the standard Linux tools (e.g., grep). Environment variable examples use PowerShell syntax for Windows and bash for Linux, but the log review section does not provide a native Linux command. The documentation refers to Windows-specific paths and tools first or exclusively in some places.
Recommendations
  • Provide Linux-native command examples (e.g., use 'grep UPLOADFAILED ./logfile.log' for log review on Linux/macOS).
  • Ensure that Linux/macOS tools are mentioned and demonstrated alongside or before Windows tools where appropriate.
  • Clarify path conventions for Linux/macOS (e.g., use $HOME/.azcopy) and avoid Windows-centric phrasing.
  • Review all examples to ensure parity and usability for Linux/macOS users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides examples only for PowerShell and .NET, both of which are primarily Windows-centric. There are no Linux/macOS-specific instructions or code samples (e.g., Bash, curl, Python, OpenSSL). The verification step recommends Fiddler, a Windows-only tool, without mentioning Linux/macOS alternatives. The structure and examples assume a Windows environment, creating friction for non-Windows users.
Recommendations
  • Add examples for configuring TLS in common Linux/macOS environments, such as Bash scripts, curl, Python, or Java.
  • Include instructions for verifying TLS version using cross-platform tools like Wireshark, tcpdump, or OpenSSL.
  • Present examples for multiple platforms side-by-side, or clearly indicate platform-specific steps.
  • Explicitly mention OS requirements and alternatives for non-Windows users.
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-12 00:00
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 setting environment variables, but consistently uses PowerShell syntax for interactive prompts and variable setting, even in generic examples. Windows-specific tools (e.g., Export-PfxCertificate) are referenced for certificate management, and PowerShell is used for secure input, with no equivalent Linux/macOS guidance (e.g., using 'read -s' in Bash). In some sections, Windows/PowerShell examples or instructions appear before Linux equivalents, and interactive examples are PowerShell-only.
Recommendations
  • Provide Bash (Linux/macOS) equivalents for interactive variable setting, such as using 'read -s' for secure input.
  • Include Linux/macOS certificate export instructions (e.g., using 'openssl') alongside Windows/PowerShell guidance.
  • Ensure that examples and instructions for Linux/macOS appear with equal prominence and detail as Windows/PowerShell examples.
  • When referencing tools, mention cross-platform alternatives (e.g., 'openssl' for certificate management).
  • Avoid using PowerShell-only syntax in generic examples; provide platform-specific tabs or sections.
GitHub Create Pull Request
Storage Upload files to Azure Blob storage by using AzCopy v10 ...cles/storage/common/storage-use-azcopy-blobs-upload.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style file paths (e.g., 'C:\myDirectory\myTextFile.txt') in all examples and does not provide any Linux/macOS equivalents (e.g., '/home/user/myTextFile.txt'). While there are tips about quoting differences between shells, all concrete examples are Windows-centric, which may confuse or slow down Linux/macOS users.
Recommendations
  • Provide parallel examples for Linux/macOS using POSIX-style paths (e.g., '/home/user/myTextFile.txt').
  • Alternate the order of examples so that Linux/macOS examples are shown first or side-by-side with Windows examples.
  • Add a section explicitly addressing Linux/macOS usage, including common shell differences and path conventions.
  • Clarify wildcard usage and path separators for Linux/macOS users.
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-12 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 provides both Linux and Windows examples for scheduling AzCopy tasks, but Windows tools (Schtasks, batch file escaping) are described in greater detail and with more context. Windows scheduling is covered after Linux, but the Windows section includes more explanation and links to Microsoft documentation. There is a section on escaping special characters in batch files, but no equivalent advice for Linux shell scripts. The Jenkins section only mentions Linux. Overall, Windows tools and patterns are described more thoroughly, and Linux users may find less guidance for edge cases.
Recommendations
  • Add a section on escaping special characters in Linux shell scripts (e.g., handling %, &, etc. in bash).
  • Provide equivalent detail for Linux scheduling (e.g., explain cron parameters as done for Schtasks).
  • Include troubleshooting tips for Linux scripts, similar to the batch file advice.
  • Balance the depth of explanation between Windows and Linux examples.
  • Mention macOS explicitly if supported, and provide examples.
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-12 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 notable Windows bias. Quick Tips and examples focus primarily on Windows OS versions and .NET Framework, with no mention of Linux/macOS equivalents. Tools and troubleshooting steps reference Windows-centric utilities (Fiddler, PowerShell, WinHTTP), and most linked guides are for Windows environments. There are no explicit Linux/macOS instructions or examples for configuring TLS 1.2, nor are Linux tools or patterns mentioned.
Recommendations
  • Add guidance for Linux/macOS users, including how to verify and configure TLS 1.2 support in common environments (e.g., OpenSSL, curl, wget, Python, Java).
  • Include Linux/macOS examples in relevant sections, such as checking TLS version support and updating libraries.
  • Mention Linux/macOS default TLS support (e.g., most modern distributions enable TLS 1.2 by default) alongside Windows notes.
  • List cross-platform tools for troubleshooting TLS (e.g., OpenSSL s_client, curl, Wireshark) in addition to Windows tools.
  • Ensure parity in linked resources, providing Linux/macOS-specific guides where possible.
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-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 moderate Windows bias. PowerShell examples are consistently provided alongside Azure CLI, with PowerShell listed first in most code tabs. Variable assignment syntax in CLI examples uses Windows-style ($Var=...) rather than POSIX/Bash style (Var=...), which may confuse Linux/macOS users. There is no explicit mention of Linux/macOS shell usage or differences, and no Bash-specific guidance or troubleshooting. The documentation assumes familiarity with PowerShell and Windows conventions, and does not provide parity for Linux/macOS users in terms of example ordering or shell-specific notes.
Recommendations
  • Provide Bash-specific CLI examples using POSIX variable assignment (e.g., VarName="value") and usage.
  • Alternate the ordering of PowerShell and CLI examples, or default to CLI first, as CLI is cross-platform.
  • Add explicit notes or sections for Linux/macOS users, clarifying shell differences and any required environment setup.
  • Where PowerShell is mentioned, clarify that it is available cross-platform, but provide Bash alternatives for Linux/macOS.
  • Review variable assignment and scripting conventions to ensure they are compatible with Bash/zsh/fish shells.
  • Consider adding troubleshooting or FAQ sections for common Linux/macOS issues.
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-12 00:00
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) listed second. However, there are no platform-specific examples, scripts, or tooling references for either Windows or Linux. The lack of concrete examples or instructions for Linux users (e.g., Pacemaker configuration, SCSI-3 PR commands on Linux) creates friction for non-Windows users.
Recommendations
  • Provide step-by-step examples for both Windows (WSFC) and Linux (Pacemaker) cluster setups.
  • Include sample commands or scripts for managing SCSI-3 Persistent Reservations on Linux (e.g., using sg_persist or similar tools).
  • Balance the order of platform mentions, or group them together to avoid implicit prioritization.
  • Add troubleshooting or best practices sections for both Windows and Linux cluster managers.
GitHub Create Pull Request
Storage Troubleshoot Azure Elastic SAN ...ticles/storage/elastic-san/elastic-san-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page shows moderate Windows bias. Windows-specific tools (iscsicli, mpclaim, PowerShell scripts) are mentioned in several troubleshooting steps, sometimes before Linux equivalents. Some sections provide only Windows examples or scripts, while Linux alternatives are referenced but less detailed. PowerShell is used for parameter changes, with CLI alternatives for Linux mentioned but not always equally explained. Windows session limits and troubleshooting steps are described in detail, while Linux-specific limits and commands are less emphasized.
Recommendations
  • Ensure Linux commands and tools (e.g., iscsiadm, multipath) are presented with equal detail and prominence as Windows tools.
  • Provide Linux/macOS script examples and troubleshooting steps wherever Windows PowerShell scripts are referenced.
  • List Linux and Windows steps side-by-side or in parallel sections, rather than Windows first.
  • Clarify session limits and configuration parameters for Linux VMs as thoroughly as for Windows.
  • Include explicit macOS guidance if relevant, or state its support status.
GitHub Create Pull Request
Storage Backup Azure Elastic SAN volumes .../articles/storage/elastic-san/elastic-san-snapshots.md
Medium 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, such as PowerShell, before Linux-friendly alternatives like Azure CLI. Windows-specific mechanisms (e.g., Volume Shadow Service) are described in detail, while Linux equivalents (e.g., fsfreeze) are mentioned briefly and with less context. All code examples are provided for PowerShell and Azure CLI, but PowerShell is always listed first, and there are no bash or shell script examples. Application-consistent backup guidance is richer for Windows than Linux.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to better support Linux/macOS users.
  • Expand the Linux section on coordinated backups to include more detail and examples, such as using fsfreeze, LVM snapshots, or other Linux-native tools.
  • Provide bash/shell script examples for common operations alongside PowerShell and CLI.
  • Clarify that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
  • Offer guidance for application-consistent backups on Linux, similar to the Windows VSS coverage.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. It references Windows-specific tools and patterns such as Volume Shadow Copy Service (VSS), Previous Versions tab, and PowerShell for enabling features. There are no examples or guidance for Linux or macOS users, nor are cross-platform backup or restore methods discussed. The instructions and terminology assume a Windows Server environment, leaving Linux/macOS users without clear guidance for disaster recovery with Azure File Sync.
Recommendations
  • Add explicit guidance for Linux and macOS users, including supported backup and restore strategies.
  • Provide examples using Linux tools (e.g., rsync, cron, native snapshot utilities) for on-premises backup.
  • Clarify whether Azure File Sync agent or server endpoint functionality is available on Linux/macOS, and if not, state this clearly.
  • If PowerShell is required, offer equivalent CLI or REST API instructions for cross-platform use.
  • Reorder examples to present cross-platform or cloud-first solutions before Windows-specific tools.
GitHub Create Pull Request
← Previous Page 6 of 16 Next →