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 126-150 of 1657 flagged pages
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 for Windows and Bash for Linux. However, prompts for sensitive input (such as client secrets and certificate passwords) are only shown using PowerShell's Read-Host, with no Linux equivalent (e.g., read -s). Additionally, references to Windows-specific tools (like Export-PfxCertificate) are present, and PowerShell is used as the default for interactive examples, even in generic sections. The Azure CLI section uses different environment variable values for Windows and Linux, with Windows using PSCRED (PowerShell credential) and Linux using AZCLI, which may cause confusion. Overall, there is a slight preference for Windows/PowerShell patterns and tools, with Linux equivalents sometimes missing or less emphasized.
Recommendations
- Provide Linux equivalents for all PowerShell-specific examples, especially for secure input prompts (e.g., use 'read -s' in Bash for secrets/passwords).
- When referencing Windows tools (e.g., Export-PfxCertificate), also mention or link to Linux/macOS alternatives for certificate export and management.
- Ensure that generic examples (such as setting environment variables or running AzCopy commands) are shown in both Bash and PowerShell, or use a neutral syntax where possible.
- Clarify the difference in environment variable values for Azure CLI integration between Windows and Linux, and explain why they differ.
- Consider presenting Linux examples first or side-by-side with Windows examples to avoid implicit prioritization of Windows.
Create Pull Request
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
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates Windows bias in several ways: PowerShell syntax is used for both Windows and Linux examples (e.g., Select-String), Windows environment variable patterns are shown first, and Windows-specific quoting conventions are explained in detail. There is a lack of native Linux/Unix command examples (such as grep or sed), and the documentation generally assumes familiarity with Windows tools and patterns.
Recommendations
- Provide native Linux/Unix command examples (e.g., use 'grep UPLOADFAILED ...' instead of 'Select-String' for Linux).
- List Linux examples before Windows examples where appropriate, or present them side-by-side.
- Explain Linux/Unix quoting conventions first, and clarify differences for Windows users.
- Include references to common Linux shell environments (bash, zsh) and their usage patterns.
- Avoid using Windows-centric tools or syntax in Linux sections unless they are truly cross-platform.
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 scheduled tasks, but Windows-specific tools (Schtasks, batch file escaping) are described in more detail and with more context than their Linux equivalents. Windows tools and patterns (Schtasks, .bat/.cmd files, PowerShell mention) are highlighted, and the section on escaping SAS tokens is Windows/batch-specific, with no Linux equivalent provided. The Windows example includes more explanation of command parameters and links to further documentation, while the Linux example is more concise.
Recommendations
- Provide equal detail and explanation for Linux scheduling tools (e.g., explain cron parameters and link to official cron documentation).
- Include a section on escaping special characters in shell scripts for Linux (e.g., handling %, &, and other shell metacharacters in bash).
- Mention Linux alternatives to Windows tools (e.g., at, systemd timers) where appropriate.
- Ensure that links to further documentation are provided for both platforms.
- Avoid assuming PowerShell or batch file usage exclusively; mention shell scripting and its nuances for Linux users.
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 operations, but consistently lists Windows-style paths (e.g., 'C:\myDirectory') and Windows command shell quoting conventions before their Linux equivalents. Notes and tips frequently reference Windows command shell behavior, with Linux guidance given as an exception or afterthought. There is a subtle prioritization of Windows terminology and patterns throughout, though Linux/NFS parity is generally maintained in the examples.
Recommendations
- Alternate the order of examples so that Linux/NFS examples are sometimes presented first, or present both examples side-by-side.
- Provide explicit Linux shell command examples (e.g., bash, zsh) and clarify quoting/escaping conventions for Linux users, not just as exceptions to Windows.
- Add a summary table or section that highlights platform-specific requirements and differences up front, making Linux/NFS usage equally prominent.
- Where possible, use generic path placeholders (e.g., <local-directory-path>) in syntax blocks before showing platform-specific examples.
- Ensure that all tips and notes address Linux and Windows users equally, rather than defaulting to Windows and adding Linux as a footnote.
Storage
Copy from Google Cloud Storage to Azure Storage with AzCopy
...cles/storage/common/storage-use-azcopy-google-cloud.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates mild Windows bias. Windows commands and conventions (such as cmd.exe quoting and 'set' for environment variables) are mentioned first or with special notes, while Linux/macOS equivalents are included but sometimes secondary. There is a tip specifically for Windows Command Shell users regarding quoting, and the environment variable setup table lists Windows first. No PowerShell-specific examples are present, but the overall pattern prioritizes Windows tools and conventions.
Recommendations
- Present Linux/macOS commands and conventions before or alongside Windows equivalents, rather than listing Windows first.
- Balance tips and notes so that Linux/macOS shell users receive equal attention (e.g., clarify quoting for bash/zsh users as well as Windows users).
- Where platform-specific instructions are needed, use parallel structure and avoid giving Windows precedence.
- Consider adding explicit PowerShell and bash examples if platform-specific scripting is discussed.
- Review the order of environment variable setup instructions to avoid implicit prioritization of Windows.
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 for the Azure Storage Emulator is heavily Windows-centric. The emulator itself is Windows-only, and all usage instructions, examples, and tooling references (such as PowerShell, SQL Server Management Studio, and Windows authentication) are specific to Windows. There are no Linux or macOS usage examples, and the only mention of cross-platform development is a brief reference to Azurite, with no further guidance or parity in examples. The command-line instructions, installation paths, and UI references are all Windows-specific.
Recommendations
- Provide equivalent examples and instructions for Azurite, which is cross-platform, including installation and usage on Linux and macOS.
- Include Linux/macOS command-line examples for common tasks (e.g., starting the emulator, generating SAS tokens, connecting with SDKs).
- Mention and demonstrate cross-platform tools (such as Azure CLI, Storage Explorer) for authentication and management, not just PowerShell and SSMS.
- Clearly separate Windows-only instructions from cross-platform guidance, and ensure that Linux/macOS developers are given actionable steps.
- Add a comparison table or section highlighting feature parity and migration steps between Storage Emulator (Windows) and Azurite (cross-platform).
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 strong Windows bias by providing only PowerShell and .NET examples for configuring TLS, both of which are primarily Windows-centric. There are no examples for Linux or macOS clients, nor are cross-platform tools or commands mentioned. The recommended verification tool is Fiddler, which is also Windows-focused, with no mention of alternatives available on Linux.
Recommendations
- Add examples for configuring TLS in Linux environments, such as using curl, Python, or OpenSSL.
- Include instructions for setting TLS versions in common Linux shells (e.g., bash) or with Linux SDKs.
- Mention cross-platform or Linux-native network traffic analysis tools (e.g., Wireshark, tcpdump) for TLS verification.
- Ensure that examples and tooling recommendations are presented for both Windows and Linux/macOS platforms, or clearly indicate platform-specific instructions.
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 prioritizing Windows operating systems and tools (e.g., Windows 8+, Windows Server 2016+, .NET Framework, Visual Studio, PowerShell, WinHTTP, Fiddler) in its guidance and examples. There is a lack of Linux-specific instructions, tools, or examples for configuring TLS 1.2, and Linux environments are not mentioned in quick tips or next steps. Most troubleshooting and configuration references are Windows-centric.
Recommendations
- Add explicit guidance for Linux environments, including how to verify and enforce TLS 1.2 in common distributions (e.g., Ubuntu, CentOS, RHEL).
- Include Linux command-line examples (e.g., using OpenSSL, curl, or system configuration files) for checking and enforcing TLS versions.
- Mention Linux equivalents of Windows tools (e.g., Wireshark, OpenSSL, curl) for troubleshooting TLS connections.
- Provide parity in quick tips, such as noting which Linux distributions have TLS 1.2 enabled by default and how to update or configure them.
- Reference cross-platform frameworks and libraries (e.g., Python, Java, Node.js) and how to ensure TLS 1.2 support in those environments.
- Balance the order of presentation so that Windows and Linux are addressed equally, or group OS-specific guidance under clearly labeled sections.
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 Tools
Windows First
Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. It highlights Windows-specific implementation details (such as Azure Storage's reliance on Windows SSL), provides PowerShell examples before Azure CLI, and references PowerShell and Windows tools without offering equivalent Linux or cross-platform alternatives. While Azure CLI is included (which is cross-platform), the prominence and ordering of Windows/PowerShell content, as well as the lack of explicit Linux shell or OpenSSL-based troubleshooting examples, indicate a Windows-centric approach.
Recommendations
- Provide explicit Linux/Bash shell examples alongside or before PowerShell examples, especially for common administrative tasks.
- Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- When referencing implementation details (such as SSL/TLS stack), mention both Windows and Linux/OpenSSL implications, or clarify the impact for non-Windows clients.
- Include troubleshooting or verification steps using Linux-native tools (e.g., curl, openssl s_client) to check TLS versions and connectivity.
- Balance the ordering of examples so that neither Windows nor Linux is always presented first, or use tabs to allow users to select their preferred platform.
- Avoid statements that suggest Windows is the default or only supported environment unless that is strictly true.
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 Windows PowerShell example for batch creation of Azure Elastic SAN volumes, referencing a Windows-style file path and omitting any Linux or cross-platform alternatives. There are no Bash, Azure CLI, or Linux shell script examples, nor is there mention of how to perform the task on non-Windows systems.
Recommendations
- Add equivalent examples using Bash and Azure CLI to demonstrate how Linux users can batch-create Elastic SAN volumes.
- Include notes on file path conventions for Linux (e.g., /home/user/ElasticSan/TestCsv3.csv) alongside Windows paths.
- Explicitly state cross-platform compatibility of the process, and mention any required tools for Linux/macOS.
- Consider providing a Python or shell script alternative for users who do not use PowerShell.
Storage
Use Azure Container Storage (version 1.x.x) with Azure managed disks
...er-storage/use-container-storage-with-managed-disks.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by consistently referencing Windows-centric tools and workflows, such as using 'code' (Visual Studio Code) as the default text editor and guiding users through Azure Portal GUI steps. There are no explicit Linux shell or editor examples (e.g., nano, vim), nor are Linux-specific command-line patterns or alternatives mentioned. The instructions for role assignment and disk management rely on Azure Portal GUI navigation, which is more familiar to Windows users, and do not provide CLI alternatives that are common in Linux workflows. The page does not mention PowerShell, but the overall approach and tool selection favor Windows users.
Recommendations
- Provide Linux-native editor examples (e.g., nano, vim, emacs) alongside 'code' when instructing users to create or edit YAML files.
- Include CLI alternatives for Azure Portal GUI steps, such as using 'az role assignment create' for role assignments, to support headless or Linux-first workflows.
- Explicitly mention that all CLI commands (kubectl, az) are cross-platform and provide notes or examples for both Windows and Linux environments where workflows differ.
- Add a section or callout for Linux users, highlighting any differences or additional steps required when using Linux-based systems.
- Avoid assuming Visual Studio Code is installed or preferred; suggest generic text editors or provide platform-specific alternatives.
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
Summary
The documentation page demonstrates a mild Windows bias. Windows examples and instructions (e.g., PowerShell commands, Registry Editor steps, screenshots of Windows tools) are consistently presented before Linux equivalents. Windows-specific tools (PowerShell, Registry Editor, iSCSI Initiator app) are mentioned by name and with detailed steps, while Linux instructions, though present, are less visually emphasized and sometimes less detailed regarding tool usage. References to enabling features (Accelerated Networking) link to Windows/PowerShell guides first. Screenshots for Windows configuration steps are more numerous and prominent.
Recommendations
- Alternate the order of Windows and Linux sections to avoid consistently prioritizing Windows.
- Provide equal detail and visual emphasis (e.g., screenshots) for Linux configuration steps and tools.
- Include direct links to Linux-specific guides and documentation (e.g., using iscsiadm, multipath-tools).
- Mention Linux commands and tools (e.g., Azure CLI, shell scripts) alongside PowerShell where relevant.
- Ensure that all configuration examples (such as enabling Accelerated Networking) have both PowerShell and CLI/bash instructions, with equal prominence.
- Add troubleshooting and best practices sections for both platforms, not just Windows.
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
Summary
The documentation page provides command-line examples exclusively for Azure PowerShell and Azure CLI, with PowerShell examples consistently presented before CLI examples. There are no Linux-specific shell examples (e.g., Bash scripts), nor are there references to Linux-native tools or workflows. The use of PowerShell as a primary example may implicitly favor Windows users, as PowerShell is the default shell on Windows, while Linux users typically use Bash or other shells.
Recommendations
- Add explicit Bash shell examples for Azure CLI commands, demonstrating usage in a typical Linux environment (e.g., variable assignment, command chaining, error handling).
- Clarify that Azure CLI commands are cross-platform and provide notes or examples for both Windows (CMD/PowerShell) and Linux (Bash) environments.
- Where PowerShell is used, provide equivalent Bash script snippets for Linux users, especially for tasks involving variable assignment and scripting.
- Consider reordering examples so that Azure CLI (which is cross-platform) is presented before PowerShell, or present both in parallel tabs.
- Mention Linux-specific considerations or workflows where relevant, such as authentication or environment setup differences.
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 mechanisms (Volume Shadow Service) before mentioning Linux alternatives, and providing more detailed context for Windows tools. Linux tools are mentioned briefly and only as alternatives, and there are no Linux shell-specific examples. The documentation does not provide parity in guidance or examples for Linux users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present them side-by-side to avoid implying preference.
- Expand the explanation of Linux backup coordination tools (e.g., fsfreeze) and mention application-consistent backup options for Linux, such as LVM snapshots or database-specific tools.
- Include Linux shell script examples (bash) for Azure CLI usage, demonstrating common Linux patterns (e.g., variable assignment, piping, error handling).
- Add notes or sections highlighting differences and best practices for Linux environments, especially for backup consistency.
- Ensure that references to Windows tools (like Volume Shadow Service) are balanced with equivalent Linux solutions, and provide links to further documentation for both platforms.
Storage
How to install the Azure File Sync agent silently
...orage/file-sync/file-sync-agent-silent-installation.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides instructions and examples for installing the Azure File Sync agent on Windows, using Windows-specific tools (msiexec) and conventions (unattend answer file, %SYSTEMDRIVE%, Windows file paths). There are no references to Linux equivalents, nor any mention of Linux support or alternative installation methods for non-Windows platforms.
Recommendations
- Clarify platform support: Explicitly state whether Azure File Sync agent is Windows-only or if Linux is supported.
- If Linux is supported, provide equivalent silent installation instructions for Linux, including command-line examples (e.g., using dpkg, rpm, or other relevant package managers).
- Include Linux-specific configuration file examples and paths.
- If Linux is not supported, add a clear note indicating that the agent is only available for Windows, to avoid confusion for cross-platform administrators.
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 Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows tools (e.g., fsutil, Robocopy, File Server Resource Manager), focusing on NTFS and Windows Server versions, and omitting Linux equivalents or examples. All instructions and technical details assume a Windows environment, with no mention of Linux support, commands, or file systems.
Recommendations
- Clarify whether Azure File Sync cloud tiering is supported on Linux servers or file systems. If not, explicitly state the Windows-only support.
- If Linux support exists or is planned, provide equivalent Linux commands (e.g., for checking cluster size, file system info) and mention supported Linux file systems.
- Include examples or guidance for Linux administrators, such as how to monitor tiering, set policies, or handle migration using Linux tools.
- Reference Linux quota management tools if applicable, and discuss differences in file system behavior (e.g., ext4, XFS) compared to NTFS.
- Avoid assuming Windows as the default platform; structure documentation to address both Windows and Linux scenarios where possible.
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 a Windows bias by referencing the Windows-specific PowerShell cmdlet 'Invoke-StorageSyncFileRecall' as the only example of how to recall files. There are no Linux or cross-platform equivalents mentioned, nor is there any guidance for managing Azure File Sync cloud tiering policies from Linux systems. All examples and scenarios assume a Windows environment, with no mention of Linux tools, commands, or workflows.
Recommendations
- Include Linux-specific instructions or examples for managing Azure File Sync cloud tiering policies, if supported.
- If Azure File Sync is Windows-only, explicitly state this limitation early in the documentation.
- Provide cross-platform alternatives or clarify which features/tools are exclusive to Windows.
- Mention whether PowerShell Core (cross-platform) can be used, or suggest REST API/CLI alternatives for Linux users.
- Add a section comparing management options on Windows and Linux, or link to relevant Linux documentation if available.
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 is no mention of Linux or cross-platform alternatives, and all tooling (such as PowerShell and Internet Explorer) is Windows-specific. The tutorial assumes the user is operating in a Windows ecosystem from start to finish.
Recommendations
- Add a section clarifying Azure File Sync's compatibility (or lack thereof) with Linux servers and file systems.
- If Linux support is possible, provide parallel instructions and examples for Linux environments, including setup, agent installation, and file sync configuration.
- Mention Linux equivalents for steps such as file creation, disk management, and Azure CLI usage.
- Where PowerShell is used, offer Azure CLI or Bash alternatives for cross-platform parity.
- Explicitly state any platform limitations up front to guide users from non-Windows backgrounds.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools and PowerShell scripts are often mentioned first or exclusively, with Linux equivalents provided but sometimes after the Windows instructions. Windows-specific tools (iscsicli, mpclaim) and PowerShell scripts are referenced more prominently, and troubleshooting steps for Windows VMs are more detailed than those for Linux. In some sections, Windows instructions precede Linux ones, and Windows session limits are discussed in detail, while Linux limits are less emphasized.
Recommendations
- Ensure that Linux examples and tools are presented with equal prominence and detail as Windows equivalents.
- When listing commands or scripts, alternate the order or present both Windows and Linux instructions side-by-side.
- Provide detailed troubleshooting steps and session limits for Linux VMs, matching the depth given for Windows.
- Reference Linux tools (e.g., iscsiadm, multipath) as clearly and frequently as Windows tools.
- Where scripts are linked, ensure both Windows and Linux scripts are equally highlighted and described.
- Avoid using Windows-centric terminology (e.g., PowerShell parameters) without providing the Linux equivalent in the same context.
Storage
Understand Azure File Sync Cloud Tiering
.../storage/file-sync/file-sync-cloud-tiering-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation is heavily oriented toward Windows environments, referencing Windows Server features (NTFS, StorageSync.sys, Event Viewer, Data Deduplication) and PowerShell cmdlets (Invoke-StorageSyncFileRecall) without mention of Linux equivalents or support. There are no examples or guidance for Linux systems, and Windows terminology and tools are used exclusively and first throughout the page.
Recommendations
- Clarify platform support: Explicitly state whether Azure File Sync cloud tiering is supported on Linux servers. If not supported, mention this early in the documentation.
- Add Linux parity information: If Linux support exists, provide equivalent examples, tools, and troubleshooting steps for Linux environments.
- Balance examples: Include both Windows and Linux command-line examples for operations like file recall, health checks, and event logging.
- Reference Linux filesystems: Discuss how tiering interacts with common Linux filesystems (e.g., ext4, XFS) if applicable.
- Mention Linux monitoring tools: If relevant, suggest Linux-native tools (e.g., journalctl, syslog, inotify) for monitoring and troubleshooting instead of only Event Viewer.
- Avoid Windows-first language: Structure documentation so that platform-specific instructions are grouped or clearly labeled, rather than assuming Windows as the default.
Storage
Best practices for disaster recovery with Azure File Sync
...ile-sync/file-sync-disaster-recovery-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-centric tools and patterns such as Volume Shadow Copy Service (VSS), the Previous Versions tab, DFS-N, and PowerShell for configuration. There are no examples or guidance for Linux environments, nor are Linux backup or restore tools mentioned. The documentation assumes the on-premises server is Windows-based and does not address disaster recovery strategies for Linux servers or cross-platform scenarios.
Recommendations
- Include explicit guidance for Linux-based servers, such as supported backup and restore strategies for Linux endpoints.
- Provide Linux command-line examples (e.g., using rsync, cron, or native snapshot tools) alongside PowerShell instructions.
- Mention Linux-compatible Azure File Sync agent support and any limitations or differences in disaster recovery procedures.
- Reference Linux equivalents for features like VSS (e.g., LVM snapshots, btrfs/zfs snapshots) and clarify which features are Windows-only.
- Ensure parity in documentation structure by presenting Windows and Linux options side-by-side where possible.
Storage
Install the Azure File Sync Agent on Arc-enabled Windows Servers
...main/articles/storage/file-sync/file-sync-extension.md
High Priority
View Details →
Detected Bias Types
Windows Only
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is exclusively focused on Windows servers, with all examples, prerequisites, and instructions tailored for Windows environments. There is explicit mention that Linux is not supported, and all tooling, settings, and file paths are Windows-specific (e.g., C:\ paths, Windows services, Programs and Features). No Linux equivalents, examples, or alternative workflows are provided. The documentation uses Windows terminology and tools throughout, and Linux is only referenced to state lack of support.
Recommendations
- Clearly state Windows-only support in the introduction and prerequisites, and provide a link to alternative solutions for Linux users (if any exist).
- If Azure File Sync is not supported on Linux, suggest comparable Azure file sync solutions or third-party alternatives for Linux Arc-enabled servers.
- Where possible, provide parity in documentation by referencing Linux-compatible Azure file sync or storage solutions, even if only to clarify limitations and alternatives.
- If future support for Linux is planned, include a roadmap or guidance for Linux users.
- Consider adding a FAQ section addressing why Linux is not supported and what options Linux users have.
Storage
How to manage Azure File Sync tiered files
...rage/file-sync/file-sync-how-to-manage-tiered-files.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments, with all examples, commands, and instructions using Windows-specific tools (PowerShell, Command Prompt, reg.exe, fsutil, NTFS attributes, Windows Registry). There is no mention of Linux support, nor are any Linux equivalents or cross-platform considerations provided. The documentation assumes the user is operating on Windows Server and does not address how to manage Azure File Sync tiered files from Linux or other platforms.
Recommendations
- Explicitly state platform requirements and limitations at the top of the document (e.g., Azure File Sync is only supported on Windows Server).
- If Azure File Sync is not supported on Linux, clarify this in the documentation and provide links to alternative solutions for Linux users.
- If any functionality is available via REST API, Azure CLI, or portal, provide examples for those methods to enable cross-platform management.
- Where possible, mention or provide parity for Linux (e.g., how to check file tiering status, manage exclusions, recall files) or explain why such actions are not possible.
- Add a section addressing cross-platform scenarios, including guidance for hybrid environments or alternatives for non-Windows systems.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page for Azure File Sync consistently centers Windows Server as the only supported or recommended platform, with all examples, deployment steps, and benefits described exclusively in terms of Windows Server. There is no mention of Linux support, Linux-based tools, or cross-platform parity, and protocols are referenced only as available 'on Windows Server.' Recovery, migration, and backup scenarios all assume Windows Server usage, and no Linux equivalents or alternatives are provided.
Recommendations
- Explicitly state platform requirements and clarify whether Linux is supported or not.
- If Linux support is available, provide equivalent examples, deployment steps, and recovery scenarios for Linux servers.
- Reference Linux-compatible protocols and tools where applicable, and mention how Linux clients or servers can interact with Azure File Sync.
- Include a comparison table or section outlining feature parity and limitations between Windows and Linux environments.
- If Azure File Sync is Windows-only, add a note for Linux users suggesting alternative Azure file storage solutions or migration strategies.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias. Azure File Sync is described as transforming Windows Server into a cache for Azure Files, and all monitoring instructions and tooling references (event logs, performance counters, agent installation) are exclusively for Windows Server. There are no Linux equivalents, examples, or guidance for monitoring Azure File Sync from Linux systems, nor is there mention of cross-platform agent support or alternative tooling.
Recommendations
- Explicitly state platform requirements and limitations for Azure File Sync, clarifying that it is Windows Server-only if that is the case.
- If Linux support is possible or planned, provide equivalent monitoring instructions, examples, and tooling for Linux systems.
- Where possible, offer cross-platform alternatives for monitoring (e.g., using Azure Monitor REST APIs, CLI, or SDKs) and provide examples for both Windows and Linux.
- Add a section addressing monitoring from non-Windows environments, even if only to clarify limitations or suggest workarounds.
- Ensure that documentation does not assume Windows as the default platform and that any platform-specific instructions are clearly labeled.