Storage
688
Total Pages
395
Linux-Friendly Pages
293
Pages with Bias
42.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
1657 issues found
Showing 301-325 of 1657 flagged pages
Storage
Azure Storage Geo Priority Replication
...rage/common/storage-redundancy-priority-replication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently alongside the Azure CLI, and example scripts for both new and existing account operations use PowerShell syntax and variable conventions (e.g., `$rgname`, `$newAccountName`) even in CLI examples. There is no mention of Linux-specific shell usage (such as Bash), nor are there examples tailored for Linux environments (e.g., using export for environment variables, or showing CLI commands in Bash syntax). The login command 'Connect-AzAccount' is shown in CLI sections, which is a PowerShell command and not valid in Bash/Linux. No Linux-specific tools or patterns are referenced.
Recommendations
- Provide explicit Bash/Linux shell examples for Azure CLI commands, using export or local variable assignment (e.g., export RGNAME=...) and removing PowerShell-specific syntax.
- Clarify login instructions for Azure CLI on Linux (e.g., use 'az login' instead of 'Connect-AzAccount').
- Ensure variable assignment and scripting examples in CLI sections use syntax compatible with Linux shells.
- Add notes or tabs for Linux users where operational steps differ from Windows/PowerShell.
- Review and update screenshots or instructions to include Linux terminal usage where appropriate.
Create Pull Request
Storage
Call REST API operations with Shared Key authorization
.../main/articles/storage/common/storage-rest-api-auth.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a clear Windows bias. It exclusively uses C# code samples and references Visual Studio as the required development environment, with no mention of Linux alternatives or cross-platform editors. The only tool recommended for inspecting HTTP requests is Fiddler, a Windows-centric application, and there are no examples or guidance for Linux users (e.g., using curl, VS Code, or Linux network sniffers). The documentation does mention that REST APIs are platform-agnostic, but all practical guidance and examples are tailored to Windows development workflows.
Recommendations
- Add equivalent code samples in a cross-platform language (e.g., Python, JavaScript, or shell scripts using curl) to demonstrate REST API calls from Linux or macOS.
- Include instructions for setting up the development environment on Linux, such as using VS Code, JetBrains Rider, or command-line tools.
- Suggest Linux-compatible tools for inspecting HTTP requests and responses, such as Wireshark, tcpdump, or curl with verbose output.
- Explicitly state that the sample application can be run on Linux using .NET Core, and provide steps for doing so.
- Balance references to Windows-specific tools (Visual Studio, Fiddler) with Linux/macOS alternatives.
- Consider reordering sections so that cross-platform options are presented before or alongside Windows-specific instructions.
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
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (Robocopy), listing AzCopy and Azure PowerShell before Azure CLI, and omitting explicit Linux usage examples or recommendations. There is no mention of Linux-native tools or commands for offline transfer, and the examples and setup instructions implicitly assume a Windows environment.
Recommendations
- Include explicit Linux examples for data transfer, such as using rsync or dd for copying data to Data Box devices.
- Mention Azure CLI before or alongside Azure PowerShell in tool lists, and clarify cross-platform support.
- Add guidance for preparing disks and file systems on Linux for Azure Import/Export and Data Box workflows.
- Reference Linux-compatible tools and commands for both online and offline transfers.
- Provide parity in screenshots and walkthroughs for Linux environments, not just Windows.
Storage
AzCopy v10 configuration setting (Azure Storage)
...ge/common/storage-ref-azcopy-configuration-settings.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows commands (CMD and PowerShell) are listed before Linux/macOS equivalents, with more detail and multiple options for Windows (CMD and PowerShell) but only a single example for Linux/macOS. Proxy configuration and bypass instructions are Windows-centric, with explicit commands for Windows and only a brief note for Linux/macOS. Some environment variable descriptions (e.g., AZCOPY_CACHE_PROXY_LOOKUP, AZCOPY_PARALLEL_STAT_FILES) reference Windows-specific behavior or optimizations, and the documentation generally assumes Windows as the default platform.
Recommendations
- Present Linux and macOS examples before or alongside Windows examples to avoid ordering bias.
- Provide equivalent detail for Linux/macOS commands, including shell variants (bash, zsh, etc.) and edge cases.
- Explicitly mention platform-specific behaviors for all supported OSes, not just Windows.
- Include troubleshooting and optimization tips for Linux/macOS environments, similar to those provided for Windows.
- Clarify when defaults or behaviors differ between platforms, and provide guidance for Linux/macOS users.
- Add examples for bypassing proxies on Linux/macOS, rather than only stating to leave the variable unset.
Storage
Grant limited access to data with shared access signatures (SAS)
...b/main/articles/storage/common/storage-sas-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell examples before Azure CLI examples in the 'Get started with SAS' section, and by referencing PowerShell and the Azure portal as primary tools for generating SAS tokens. There is a lack of explicit Linux shell (bash) or cross-platform command-line examples, and PowerShell is highlighted before CLI, which is more platform-neutral. No Linux-specific tools or patterns are mentioned, and the documentation does not provide parity for Linux users in terms of example ordering or tool coverage.
Recommendations
- Ensure Azure CLI examples are listed before or alongside PowerShell examples, as CLI is available on both Windows and Linux.
- Add explicit bash/shell examples for SAS creation and usage, especially in the 'Get started with SAS' section.
- Reference cross-platform tools (such as AzCopy, Azure CLI) before Windows-specific tools (PowerShell, portal) when discussing SAS generation.
- Include notes or sections on how Linux users can perform equivalent operations, and clarify that Azure CLI and SDKs are platform-neutral.
- Review all example links and ensure Linux parity in documentation coverage and ordering.
Storage
Authorize access for AzCopy with a managed identity
...ommon/storage-use-azcopy-authorize-managed-identity.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates some Windows bias. References to enabling managed identity on VMs consistently link to Windows VM instructions, with no mention or link to Linux VM equivalents. Environment variable examples are provided for both Linux and Windows, but the Windows examples use PowerShell syntax and are presented in parallel tabs, which is good. However, in the Azure CLI section, the Windows example uses PowerShell variables and a different login type ('PSCRED') compared to Linux ('AZCLI'), with no explanation of the difference or parity. The documentation also references Azure PowerShell as a primary tool for authorization, which is Windows-centric, and provides more detail for PowerShell than for Bash or other shells. There is no mention of Linux-specific VM configuration steps, nor are there links to Linux VM managed identity setup guides.
Recommendations
- Add explicit links and instructions for enabling managed identities on Linux VMs, not just Windows VMs.
- Clarify differences between 'AZCLI' and 'PSCRED' login types and ensure both Linux and Windows users understand which to use.
- Provide parity in examples for Bash and PowerShell, and explain any differences in behavior or requirements between platforms.
- Include references to Linux tools and workflows where appropriate, such as using Bash scripts or Linux credential stores.
- Ensure that all screenshots and UI instructions are applicable to both Windows and Linux environments, or provide alternatives.
Storage
Authorize access for AzCopy with a service principal
...mmon/storage-use-azcopy-authorize-service-principal.md
High Priority
View Details →
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 and tools (e.g., Read-Host, $Env:) for sensitive variable input and certificate export. References to Windows-specific tooling (Export-PfxCertificate) are present, and secure input examples are only shown in PowerShell. In sections without explicit OS tabs, PowerShell is used by default, and Windows certificate store/export guidance is given before Linux equivalents. There is limited coverage of Linux-native secure input or certificate handling.
Recommendations
- Provide Linux shell equivalents for secure input (e.g., using 'read -s' in bash) alongside PowerShell examples.
- Include Linux-native certificate export and handling instructions (e.g., using openssl) before or alongside Windows/PowerShell guidance.
- When showing environment variable setting, offer both bash and PowerShell examples in all relevant sections, not just in OS-tabbed blocks.
- Avoid using PowerShell as the default for secure input and scripting examples; balance with bash/zsh where appropriate.
- Explicitly mention Linux keyring alternatives or limitations when discussing secret stores, and provide guidance for Linux users.
Storage
Find errors & resume jobs with logs in AzCopy (Azure Storage)
...rticles/storage/common/storage-use-azcopy-configure.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits Windows bias in several ways. Windows terminology and environment variables (e.g., %USERPROFILE%) are mentioned before Linux equivalents. The log review example uses PowerShell's Select-String for both Linux and Windows, which is not a native Linux tool and may confuse Linux users. There is a lack of Linux-native command examples (e.g., grep) for log searching. Instructions for quoting arguments prioritize Windows shell behavior, and PowerShell syntax is used for environment variable setting on Windows, while Linux uses export. Overall, the documentation assumes familiarity with Windows tools and patterns, with Linux support added secondarily.
Recommendations
- Provide Linux-native command examples (e.g., use 'grep UPLOADFAILED ...' for log searching on Linux instead of PowerShell's Select-String).
- Mention Linux/Mac environment variable paths and conventions before or alongside Windows ones, rather than after.
- Clarify that Select-String is a PowerShell command and not standard on Linux; suggest installing PowerShell on Linux only if needed, otherwise use native tools.
- When discussing quoting conventions, present Linux/Mac guidance first or equally, and clarify differences for various shells.
- Ensure that all examples and instructions are available for both platforms, and avoid assuming Windows as the default environment.
Storage
Transfer data to or from Azure Files by using AzCopy v10
...in/articles/storage/common/storage-use-azcopy-files.md
High Priority
View Details →
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, ensuring parity in command syntax and options. However, there is a subtle Windows bias: Windows path examples (e.g., 'C:\myDirectory') are always listed first in each example section, and special notes repeatedly instruct users to use double quotes in the Windows Command Shell, with single quotes as the default for other shells. There are no PowerShell-specific examples, and Linux-specific operational notes are present where relevant (e.g., NFS scenarios only supported on Linux). Overall, Linux coverage is strong, but Windows examples and instructions are consistently presented before Linux equivalents.
Recommendations
- Alternate the order of Windows and Linux examples so that Linux examples are sometimes presented first.
- Add a brief introductory note explicitly stating that all operations are supported on both Windows and Linux (where applicable), and clarify platform-specific limitations up front.
- Provide a summary table at the start of each section showing example paths for both Windows and Linux, to reinforce parity.
- Reduce repetition of Windows shell quoting notes by consolidating into a single section or sidebar, and add equivalent notes for Linux shells (e.g., bash, zsh) if needed.
- Consider including macOS examples where relevant, or explicitly state platform support for each scenario.
Storage
Use AzCopy v10 in scripts and scheduled transfers
...rticles/storage/common/storage-use-azcopy-in-script.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for scheduling AzCopy tasks, but Windows-specific tools (Schtasks, batch file escaping) are described in greater detail and with more context. Windows scheduling is explained with parameter breakdowns and links to Microsoft documentation, while Linux scheduling (cron) is covered more briefly. Special character escaping is discussed only for Windows batch files, not for Linux shell scripts. The Jenkins section is Linux-oriented, but overall, Windows tools and patterns are given more prominence and explanation.
Recommendations
- Provide equal detail for Linux scheduling (e.g., explain cron parameters and link to official cron documentation).
- Include information about escaping special characters in Linux shell scripts, if applicable.
- Add examples for using AzCopy in PowerShell and Bash scripts, highlighting cross-platform differences.
- Ensure links to Linux documentation (e.g., man pages for cron, bash scripting guides) are present.
- Balance the explanation depth between Windows and Linux sections, including troubleshooting tips for both platforms.
Storage
Configure Transport Layer Security (TLS) for a client application
...n/transport-layer-security-configure-client-version.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell and .NET examples for configuring TLS, both of which are primarily Windows-centric. There are no examples or guidance for configuring TLS in Linux environments, such as using curl, OpenSSL, or common Linux programming languages. Additionally, the verification step recommends Fiddler, a Windows-only tool, without mentioning Linux alternatives.
Recommendations
- Add examples for configuring TLS in Linux environments, such as using curl, Python, or Java.
- Include instructions for setting TLS versions in common Linux shells (e.g., bash) and tools (e.g., wget, curl).
- Provide verification steps using cross-platform or Linux-native tools, such as tcpdump, Wireshark, or OpenSSL.
- Ensure that examples for Linux are presented alongside or before Windows examples to improve parity.
Storage
Use the Azure Storage Emulator for development and testing (deprecated)
...b/main/articles/storage/common/storage-use-emulator.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows, with the Azure Storage Emulator only available for Windows and all usage instructions, examples, and tooling references (such as PowerShell, SQL Server, and Windows UI patterns) being Windows-centric. Linux is only mentioned as an alternative via Azurite, but no Linux-specific instructions, examples, or parity tooling are provided. The command-line examples and authentication flows are exclusively Windows/PowerShell-based, and there is no guidance for Linux users on how to achieve similar workflows.
Recommendations
- Provide equivalent Linux/macOS instructions for local Azure Storage development using Azurite, including installation, startup, and authentication flows.
- Include CLI examples (e.g., Bash, Azure CLI) for generating SAS tokens and managing storage resources, not just PowerShell.
- Document how to use Azurite with common Linux tools (e.g., Docker, npm) and show how to connect to Azurite from cross-platform SDKs.
- Add a section comparing Storage Emulator and Azurite, with migration guidance and parity notes for developers moving from Windows to Linux.
- Ensure all tooling references (e.g., Storage Explorer, SQL management) include Linux-compatible alternatives or usage notes.
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
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows operating systems and tools first and exclusively (Windows 8+, Windows Server 2016+, .NET Framework, Visual Studio, PowerShell, WinHTTP, Fiddler). There are no Linux-specific instructions, examples, or tools mentioned, nor is there guidance for configuring TLS 1.2 on Linux clients or with common Linux frameworks. The quick tips and next steps sections focus on Windows environments and omit Linux equivalents.
Recommendations
- Add explicit instructions and examples for configuring TLS 1.2 on Linux clients (e.g., OpenSSL, curl, wget, Python, Java).
- Mention Linux distributions and their default TLS settings (e.g., Ubuntu, CentOS, RHEL) alongside Windows versions.
- Include troubleshooting steps and tools for Linux environments (e.g., using openssl s_client, nmap, curl --tlsv1.2).
- Provide parity in guidance for updating libraries and frameworks commonly used on Linux (e.g., Python, Java, Node.js).
- List cross-platform tools for TLS inspection (e.g., Wireshark, openssl) in addition to Windows-specific ones like Fiddler.
- Ensure that links and next steps include Linux-focused resources and documentation.
Storage
Enforce a Minimum Required Version of Transport Layer Security (TLS)
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-minimum-version.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Windows-Centric Tips
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is presented as a primary scripting example, and Windows-specific implementation details and tips are highlighted (e.g., reliance on Windows SSL stack). The Azure CLI example is present and cross-platform, but the ordering and emphasis favor Windows/PowerShell. There is no explicit Linux example or mention of Linux-specific considerations, and the documentation does not address OpenSSL or Linux client nuances except to note that Azure Storage is not affected by OpenSSL vulnerabilities.
Recommendations
- Add explicit Linux/Bash shell examples for configuring and verifying TLS settings, such as using curl or OpenSSL to test TLS versions.
- Reorder the scripting sections to present Azure CLI before PowerShell, or clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Include a note or section on Linux client considerations, such as how to ensure Linux-based applications use the correct TLS version when connecting to Azure Storage.
- Provide troubleshooting steps or references for common Linux TLS issues (e.g., updating OpenSSL, configuring system-wide TLS defaults).
- Balance tips and notes to address both Windows and Linux environments, especially in security and implementation details.
Storage
Create multiple Azure Elastic SAN volumes in a batch
...storage/elastic-san/elastic-san-batch-create-sample.md
High Priority
View Details →
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, referencing a Windows-style file path and omitting any Linux or cross-platform CLI examples. There is no mention of Bash, Azure CLI, or Linux-compatible tooling, which may hinder accessibility for users on non-Windows platforms.
Recommendations
- Add equivalent examples using Azure CLI (az) and Bash scripting for Linux/macOS users.
- Reference Linux file path formats (e.g., /home/user/ElasticSan/TestCsv3.csv) alongside Windows paths.
- Explicitly state cross-platform compatibility and provide guidance for running scripts on Linux/macOS.
- Include notes or links to install Azure CLI and PowerShell Core on Linux/macOS.
Storage
Best practices for configuring an Elastic SAN
...cles/storage/elastic-san/elastic-san-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Image Bias
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows examples, tools, and screenshots are frequently presented before Linux equivalents, and some instructions (such as enabling Accelerated Networking) reference PowerShell and Windows-centric workflows first. Windows-specific tools (Registry Editor, iSCSI Initiator app) are described in detail, with corresponding Linux instructions sometimes less detailed or presented after Windows. Screenshots and image examples are predominantly Windows-focused, and links to scripts or further reading often prioritize Windows. There is also a tendency to mention Windows session limits and configuration nuances before Linux ones.
Recommendations
- Alternate the order of Windows and Linux sections so that Linux is sometimes presented first.
- Provide equal detail for Linux configuration steps, including GUI-based workflows where applicable.
- Include Linux-specific screenshots and visual aids alongside Windows images.
- Reference Linux command-line tools (e.g., iscsiadm, multipath-tools) in introductory sections, not only in detailed steps.
- Ensure links to further reading or scripts are provided for both Windows and Linux, with parity in depth and clarity.
- Explicitly mention session limits, configuration caveats, and troubleshooting steps for Linux as is done for Windows.
- Where PowerShell is referenced, also provide Bash/Azure CLI equivalents for Linux users.
Storage
Configure Service Endpoints for Azure Elastic SAN
...elastic-san/elastic-san-configure-service-endpoints.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is consistently presented before Azure CLI in code examples and instructions. The use of PowerShell is emphasized throughout, and variable syntax in CLI examples uses Windows-style ($Var) rather than POSIX/Linux-style. There is no mention of Linux-specific tools or shell environments, and the documentation does not provide parity for Linux command-line conventions or examples. The focus on PowerShell and Windows-first ordering may make the documentation less approachable for Linux users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to better support Linux users.
- Use POSIX-style variable syntax (e.g., VAR=value) in Azure CLI examples to match Linux conventions.
- Explicitly mention that Azure CLI commands can be run in Bash or other Linux shells, and provide sample commands using Linux shell syntax.
- Add notes or sections highlighting any Linux-specific considerations or troubleshooting steps.
- Ensure screenshots and UI instructions are not Windows-centric, and clarify cross-platform compatibility where relevant.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits Windows bias by consistently listing PowerShell examples before Azure CLI, referencing Windows-specific backup coordination tools (Volume Shadow Service) before mentioning Linux alternatives, and generally using Windows terminology and patterns. There is a lack of Linux-specific guidance, and examples do not address Linux shell scripting or tools beyond a brief mention of fsfreeze.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to avoid implicit prioritization of Windows tools.
- Expand the discussion of Linux backup coordination tools, providing more detail and examples (e.g., using fsfreeze, LVM snapshots, or application-level Linux backup strategies).
- Include Linux shell scripting examples alongside PowerShell, especially for tasks like exporting and managing snapshots.
- Clarify that Azure CLI works cross-platform and provide context for both Windows and Linux users in all procedural steps.
- Add troubleshooting or best practices sections for Linux environments, including common issues and solutions.
Storage
Manage customer-managed keys - Azure Elastic SAN
...tic-san/elastic-san-encryption-manage-customer-keys.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently providing PowerShell examples and referencing PowerShell commands first in each code section. There are no Linux-specific shell examples (such as Bash scripts), nor are there references to Linux-native tools or patterns. The Azure CLI examples are provided, but they are generic and do not address Linux-specific usage or nuances. The documentation assumes familiarity with PowerShell, which is primarily a Windows tool, and does not mention or prioritize Linux workflows.
Recommendations
- Add explicit Bash shell examples for all CLI commands, showing Linux-style variable usage and command chaining.
- Include notes or sections on running Azure CLI commands in Linux environments, addressing common Linux shell patterns.
- Avoid listing PowerShell examples first; alternate the order or provide both examples side-by-side.
- Reference Linux-native tools or scripting approaches where relevant, such as using environment variables, piping, or automation via cron.
- Clarify that Azure CLI is cross-platform and provide troubleshooting tips for Linux users (e.g., authentication, permissions, shell differences).
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation frequently mentions Windows tools and scripts before Linux equivalents, and provides more detailed instructions for Windows scenarios (e.g., PowerShell parameters, Windows-specific session limits). Windows tools such as 'iscsicli', 'mpclaim', and PowerShell scripts are referenced prominently, sometimes before Linux commands. Linux examples are present but often appear as secondary or less detailed. There is a tendency to present Windows instructions first or with more context, indicating a Windows-first and PowerShell-heavy bias.
Recommendations
- Ensure Linux commands and tools are presented with equal prominence and detail as Windows examples.
- Alternate the order of Windows and Linux instructions to avoid always listing Windows first.
- Provide Linux-specific troubleshooting steps and scripts with the same depth as Windows PowerShell examples.
- Include more Linux distribution-specific notes (e.g., for Ubuntu, CentOS, RHEL) where relevant.
- Where Windows tools are mentioned (e.g., 'iscsicli', 'mpclaim'), ensure Linux equivalents (e.g., 'iscsiadm', 'multipath') are described with equal detail.
- Add parity in session limit explanations for Linux VMs, not just Windows.
- Review script links and ensure Linux scripts are as accessible and documented as Windows PowerShell scripts.
Storage
Choose Azure File Sync cloud tiering policies
...e/file-sync/file-sync-choose-cloud-tiering-policies.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows Server, NTFS, and Windows-specific tools (e.g., fsutil, Robocopy, FSRM), with no mention of Linux equivalents or support. All examples and operational guidance are tailored to Windows environments, and there is no discussion of how (or if) cloud tiering policies apply to Linux systems or filesystems.
Recommendations
- Clarify whether Azure File Sync cloud tiering is supported on Linux servers and filesystems (e.g., ext4, XFS).
- If Linux support exists, provide equivalent commands and examples for determining cluster size and managing tiering policies on Linux (e.g., using 'lsblk', 'df', or 'stat').
- Mention Linux quota management tools (e.g., 'quota', 'xfs_quota') if applicable, and how they interact with cloud tiering.
- If Azure File Sync is Windows-only, explicitly state this in the prerequisites or limitations section to avoid confusion.
- Consider including a comparison table or section outlining differences between Windows and Linux support for Azure File Sync cloud tiering.
Storage
Azure File Sync cloud tiering policies
...es/storage/file-sync/file-sync-cloud-tiering-policy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (e.g., Invoke-StorageSyncFileRecall PowerShell cmdlet) and patterns, without providing equivalent Linux commands or examples. All operational examples and instructions assume a Windows environment, and there is no mention of Linux support or parity for Azure File Sync cloud tiering management.
Recommendations
- Include Linux-specific instructions or clarify platform support for Azure File Sync cloud tiering.
- Provide examples using Linux CLI tools (if supported), such as Azure CLI or REST API equivalents for file recall and policy management.
- Explicitly state platform limitations or availability (e.g., if Azure File Sync is Windows-only, make this clear at the start).
- If Linux support is planned or available, add parity examples and troubleshooting steps for Linux environments.
Storage
Extend Windows File Servers with Azure File Sync
...articles/storage/file-sync/file-sync-extend-servers.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows Server environments, with all examples, instructions, and screenshots tailored exclusively to Windows. There are no references to Linux servers, Linux file systems, or cross-platform alternatives. Windows-specific tools (Server Manager, Internet Explorer, PowerShell) are used throughout, and the tutorial assumes the reader is using Windows Server both on-premises and in Azure. No Linux equivalents or parity guidance are provided.
Recommendations
- Add a section clarifying Azure File Sync's compatibility or limitations with Linux servers and file shares.
- If Azure File Sync supports Linux (or if there are alternative solutions for Linux), provide parallel instructions and examples for Linux environments, including CLI commands and setup steps.
- Mention Linux file server options (such as Samba) and how they could integrate with Azure Files, if possible.
- Include Linux-based tools and commands (e.g., Azure CLI, mounting Azure Files on Linux) where relevant.
- If Azure File Sync is Windows-only, explicitly state this at the beginning and link to Linux alternatives for hybrid file sharing/storage.
- Balance PowerShell instructions with Azure CLI or Bash equivalents for cross-platform usability.
Storage
Azure File Sync on-premises firewall and proxy settings
...cles/storage/file-sync/file-sync-firewall-and-proxy.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, with all configuration steps, examples, and tooling references (PowerShell, netsh, Windows paths, .NET config files) being specific to Windows Server. There are no Linux equivalents or cross-platform instructions, and the use of Windows tools and patterns is pervasive throughout the page.
Recommendations
- Explicitly state Azure File Sync agent is Windows-only, or clarify Linux support status early in the document.
- If Linux support exists or is planned, provide equivalent Linux instructions for proxy and firewall configuration (e.g., using curl, iptables, systemd, or other Linux-native tools).
- Include Linux shell (bash) examples for network connectivity testing and firewall updates.
- Reference Linux configuration files and proxy settings (such as /etc/environment, /etc/ssl/certs, etc.) where applicable.
- If PowerShell is required, clarify whether PowerShell Core on Linux is supported and provide cross-platform usage notes.
- Add a section comparing Windows and Linux support, listing any limitations or differences.
Storage
Modify your Azure File Sync topology
...es/storage/file-sync/file-sync-modify-sync-topology.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific concepts (e.g., D: drive, Azure Virtual Machines Windows documentation) and omitting Linux-specific guidance or examples. All instructions and references assume a Windows server environment, with no mention of Linux server endpoints, file system paths, or Linux administrative tools. Windows terminology and links are provided without Linux equivalents.
Recommendations
- Include examples and guidance for Linux server endpoints, such as using Linux file system paths (e.g., /mnt/data) and relevant administrative commands.
- Reference both Windows and Linux Azure VM documentation when discussing drive management or migration.
- Clarify whether Azure File Sync supports Linux endpoints and, if so, provide parity in instructions for both platforms.
- Add notes or sections addressing differences in deprovisioning, path changes, and endpoint management for Linux servers.
- Ensure that terminology and examples are platform-neutral or explicitly cover both Windows and Linux scenarios.