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 926-950 of 1657 flagged pages
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-troubleshoot.md
...ticles/storage/elastic-san/elastic-san-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several sections. Windows tools and scripts (e.g., iscsicli, mpclaim, PowerShell scripts) are often mentioned before or more prominently than their Linux equivalents. Some troubleshooting steps and examples are provided only for Windows, or with more detail for Windows than Linux. In some cases, Linux commands are mentioned, but not always with the same level of explanation or parity.
Recommendations
- Ensure that Linux commands and tools are presented alongside Windows equivalents, and with equal prominence and detail.
- Where PowerShell scripts are referenced for Windows, provide Bash or Python script equivalents for Linux, and link to them with equal visibility.
- Avoid listing Windows tools or commands first by default; alternate the order or present both together.
- Where session limits or configuration parameters are discussed, provide explicit Linux instructions and examples, not just for Windows.
- In sections like 'Unable to connect to more than eight volumes to a Windows VM', add a parallel section for Linux VMs if applicable, or clarify if the limitation is Windows-specific.
- In the 'Troubleshoot CRC protection' section, provide step-by-step Linux instructions with the same clarity as the Windows instructions.
- Review all troubleshooting steps to ensure Linux users are not required to infer steps from Windows-centric instructions.
Create Pull Request
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-disaster-recovery-best-practices.md
...ile-sync/file-sync-disaster-recovery-best-practices.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (such as Volume Shadow Copy Service and the Previous Versions tab), requiring PowerShell for configuration, and omitting Linux equivalents or examples. There is no mention of Linux server support, backup, or restore procedures, and all operational guidance assumes a Windows environment.
Recommendations
- Include explicit guidance for Linux-based Azure File Sync agents if supported, or clarify platform limitations.
- Provide Linux command-line examples (e.g., using shell scripts or Linux-native backup tools) alongside PowerShell instructions.
- Reference Linux file system snapshot and backup solutions (such as LVM snapshots, rsync, or third-party Linux backup tools) where VSS is mentioned.
- Avoid assuming the use of Windows-only features (like the Previous Versions tab) without offering Linux alternatives or noting their absence.
- Clearly state platform support and any feature gaps between Windows and Linux in Azure File Sync scenarios.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-cloud-tiering-overview.md
.../storage/file-sync/file-sync-cloud-tiering-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation is heavily oriented towards Windows environments. It references Windows Server features (such as NTFS, reparse points, and data deduplication), describes file attributes and behaviors specific to NTFS, and mentions PowerShell cmdlets (e.g., Invoke-StorageSyncFileRecall) without providing any Linux equivalents or clarifying cross-platform support. There are no examples, instructions, or notes for Linux or non-Windows environments, and all technical details assume a Windows file server context.
Recommendations
- Explicitly state whether Azure File Sync cloud tiering is supported or unsupported on Linux servers, and if not, clarify this early in the documentation.
- If Linux support exists or is planned, provide equivalent examples and instructions for Linux environments, including file system behaviors, relevant commands, and troubleshooting steps.
- Where Windows-specific features (e.g., NTFS attributes, Event Viewer logs, PowerShell cmdlets) are mentioned, offer Linux analogs or note their absence.
- Add a section comparing Windows and Linux support for Azure File Sync, outlining any differences in feature availability, setup, and management.
- Ensure parity in screenshots and examples, showing both Windows and Linux file property dialogs or command outputs where applicable.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-agent-silent-installation.md
...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 files, Windows file paths, environment variables like %SYSTEMDRIVE%). There are no examples or mentions of Linux installation methods, tools, or compatibility, indicating a strong Windows bias.
Recommendations
- Clarify in the introduction whether Azure File Sync agent is supported on Linux. If not, state this explicitly to avoid confusion.
- If Linux support exists or is planned, provide equivalent Linux installation instructions (e.g., using .deb/.rpm packages, shell scripts, or relevant package managers).
- Include Linux command-line examples alongside Windows examples, using appropriate tools and file path conventions.
- Mention Linux-specific considerations or limitations, if any, in the installation process.
- Ensure that all configuration options and parameters are documented for both platforms, or clearly indicate if some are Windows-only.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-how-to-manage-tiered-files.md
...rage/file-sync/file-sync-how-to-manage-tiered-files.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows environments, with all examples and instructions using Windows-specific tools (PowerShell, Command Prompt, reg.exe, fsutil, Windows Explorer, Windows registry paths). There are no Linux equivalents or cross-platform guidance, and the documentation assumes the user is operating on Windows Server. Azure File Sync is presented as a Windows-only solution, with no mention of Linux support or alternatives.
Recommendations
- Clearly state early in the documentation that Azure File Sync is currently a Windows-only feature, if that is the case. If Linux support is planned or available, provide equivalent instructions and examples for Linux environments.
- Where possible, provide cross-platform alternatives or clarify the lack thereof (e.g., note that registry settings and PowerShell cmdlets are not available on Linux).
- If certain features are only available on Windows, explicitly mention this limitation to set user expectations.
- Consider including a section on how Linux users can interact with Azure Files (e.g., via SMB/NFS mounts, az CLI, or REST API), even if tiering is not supported, to guide non-Windows users.
- Review all examples and instructions to ensure that, where feasible, Linux or cross-platform approaches are presented alongside Windows-specific ones.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-extend-servers.md
...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 exclusively focused on Windows Server environments, with all examples, instructions, and screenshots tailored to Windows Server and its tools (e.g., PowerShell, Server Manager, Internet Explorer). There is no mention of Linux or cross-platform alternatives, and all steps assume the use of Windows-specific workflows and interfaces.
Recommendations
- Clearly state early in the documentation that Azure File Sync is only supported on Windows Server, if that is the case. If not, add equivalent instructions for Linux environments or clarify Linux support status.
- If partial Linux support exists (e.g., for Azure Files but not File Sync), provide links or references to Linux-specific documentation for related scenarios.
- Where PowerShell is used, mention if there are CLI or REST API alternatives that can be used from Linux or cross-platform environments.
- If possible, provide a comparison table or FAQ addressing platform support and alternatives for Linux administrators.
- Avoid assuming the use of Windows-only tools (e.g., Internet Explorer, RDP) unless absolutely necessary, and suggest cross-platform alternatives (e.g., SSH, Azure CLI, browser-agnostic instructions) where applicable.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-server-recovery.md
...rticles/storage/file-sync/file-sync-server-recovery.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation assumes the recovery process is performed exclusively on Windows Server or Azure VMs running Windows. It references only Windows-specific tools (Robocopy), and all instructions and agent installation steps are for Windows. There are no examples or guidance for Linux environments, nor are Linux tools or agent support discussed.
Recommendations
- Clarify early in the documentation whether Azure File Sync supports only Windows, or if Linux is supported, provide equivalent instructions for Linux environments.
- If Linux is supported, provide examples using Linux tools (e.g., rsync) alongside Robocopy, and include Linux command-line examples.
- Mention and link to Linux agent installation guides if available.
- If Azure File Sync is Windows-only, explicitly state this limitation at the beginning of the documentation to set user expectations.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-introduction.md
...n/articles/storage/file-sync/file-sync-introduction.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page for Azure File Sync demonstrates a strong Windows bias. All examples, deployment scenarios, and tool references are centered exclusively around Windows Server. There is no mention of Linux support, Linux-based file servers, or cross-platform usage. The documentation assumes the reader is using Windows Server, and all operational guidance is Windows-specific.
Recommendations
- Explicitly state whether Azure File Sync supports only Windows Server, or clarify any Linux support or limitations.
- If Linux or other platforms are supported, provide equivalent examples and deployment scenarios for those environments.
- Mention Linux-compatible protocols (such as NFS) and describe how they can be used with Azure File Sync, if applicable.
- Include guidance or links for users who may want to integrate Linux file servers with Azure Files, even if Azure File Sync itself is Windows-only.
- Balance the documentation by addressing both Windows and Linux administrators in the introduction and benefits sections.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-snapshots.md
.../articles/storage/elastic-san/elastic-san-snapshots.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided for every operation, and in some sections (such as the 'Take a stable snapshot' section), Windows-specific tools and patterns (like Volume Shadow Service) are mentioned first and in more detail than their Linux equivalents. Linux is only briefly mentioned, and the Linux tool (fsfreeze) is described as providing less functionality. There are no Linux shell (bash) or scripting examples, and the documentation does not address Linux-specific workflows or application-consistent backup strategies in depth.
Recommendations
- Provide Linux shell (bash) script examples alongside PowerShell for all CLI-based operations.
- Expand the discussion of Linux backup coordination tools, including examples of using fsfreeze and other common Linux utilities (e.g., LVM snapshots, application-specific tools) for achieving file- or application-consistent snapshots.
- When mentioning Windows tools (like Volume Shadow Service), give equal prominence and explanation to Linux alternatives, possibly with links to relevant documentation.
- Consider adding a table or section comparing Windows and Linux approaches to snapshot consistency, including best practices for both platforms.
- Ensure that any prerequisites or environment setup steps are described for both Windows and Linux users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-modify-sync-topology.md
...es/storage/file-sync/file-sync-modify-sync-topology.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation implicitly assumes a Windows environment throughout. There are no Linux-specific examples or guidance, and the only OS-specific reference is to the Windows D: drive. The instructions and terminology (e.g., 'server endpoint path', 'D drive', 'Registered servers' tab) are Windows-centric, with no mention of Linux equivalents or cross-platform considerations. This creates a bias toward Windows users and leaves Linux administrators without clear guidance.
Recommendations
- Add explicit guidance for Linux-based Azure File Sync agents, if supported, including examples of typical Linux file system paths and considerations.
- Where drive letters or Windows-specific terminology is used (e.g., 'D: drive'), provide Linux equivalents (e.g., '/mnt/data') or clarify if the feature is Windows-only.
- Include screenshots or navigation steps for both Windows and Linux environments where applicable.
- State clearly at the beginning of the documentation which platforms are supported, and if Linux is not supported, make this explicit to avoid confusion.
- If Azure File Sync is Windows-only, add a note to clarify this and suggest alternative solutions for Linux users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-firewall-and-proxy.md
...cles/storage/file-sync/file-sync-firewall-and-proxy.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All configuration steps, examples, and command-line instructions are provided exclusively for Windows Server, using Windows-specific tools (PowerShell, netsh, editing machine.config, etc.). There are no examples or guidance for configuring Azure File Sync proxy/firewall settings on Linux or non-Windows platforms, nor is there any mention of Linux support or alternatives.
Recommendations
- Explicitly state platform support: If Azure File Sync is only supported on Windows Server, clarify this at the beginning of the documentation. If Linux support is planned or available, provide equivalent instructions.
- Add Linux examples: For sections on proxy and firewall configuration, include Linux equivalents (e.g., using curl, iptables, firewalld, or editing environment variables for .NET Core apps on Linux).
- Provide cross-platform PowerShell/CLI guidance: Where PowerShell is used, mention if and how these cmdlets can be used on PowerShell Core on Linux, or provide Azure CLI alternatives.
- Reference Linux documentation: Link to relevant Microsoft or community documentation for configuring proxies and firewalls on Linux systems.
- Avoid hardcoding Windows paths: When referencing files or modules, note the Linux equivalents or clarify if they are Windows-only.
- Clarify tool availability: For tools like netsh or ServerRegistration.exe, state their platform limitations and suggest Linux alternatives if possible.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-monitoring.md
...ain/articles/storage/file-sync/file-sync-monitoring.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation for monitoring Azure File Sync is heavily oriented toward Windows Server environments. It exclusively references Windows Server, Windows-specific tools (Event Viewer, Perfmon.exe), and Windows event logs for monitoring and troubleshooting. There are no examples, instructions, or references for Linux systems or cross-platform monitoring approaches. The documentation assumes the use of Windows Server as the on-premises cache and does not mention or support Linux-based alternatives.
Recommendations
- Explicitly state in the introduction whether Azure File Sync is supported only on Windows Server, or clarify if Linux support is planned or available.
- If Linux support is available or planned, provide equivalent monitoring instructions for Linux systems, including how to access logs, monitor sync health, and collect performance metrics using Linux-native tools (e.g., journalctl, sysstat, or custom scripts).
- Where possible, use cross-platform Azure Monitor features and show examples for both Windows and Linux, or clarify when a feature is Windows-only.
- Consider including a section that addresses monitoring from non-Windows endpoints, even if only to state limitations or alternatives.
- Review all tool and process mentions to ensure Linux administrators are not excluded from monitoring guidance.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-planning.md
.../main/articles/storage/file-sync/file-sync-planning.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation for Azure File Sync is heavily biased toward Windows environments. It exclusively discusses deployment, management, and compatibility in the context of Windows Server, with no mention of Linux or cross-platform agents. All examples, requirements, and tools (such as PowerShell cmdlets and NTFS-specific features) are Windows-centric. Linux is only briefly mentioned as a client for direct SMB mounting, but not as a participant in Azure File Sync. There are no Linux-specific instructions, tools, or parity in examples.
Recommendations
- Clearly state early in the documentation that Azure File Sync is only supported on Windows Server, and clarify the lack of Linux agent support.
- If any Linux or cross-platform support is planned or available (even in preview), mention it and provide equivalent instructions or links.
- Where possible, provide parity in examples for direct SMB mounting from Linux (e.g., show how to mount Azure Files using Linux commands such as 'mount -t cifs').
- For management and evaluation tools, mention if there are any CLI or cross-platform alternatives to PowerShell, or clarify that only PowerShell is supported.
- In sections discussing file systems, clarify that NTFS requirements preclude Linux/ext4/xfs support, and explain the rationale.
- If Azure File Sync is fundamentally Windows-only, consider a brief FAQ or callout for Linux users explaining alternatives (such as using direct SMB/NFS mounts or third-party sync tools).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/migrate-files-between-shares.md
...articles/storage/files/migrate-files-between-shares.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation exclusively describes file migration using Robocopy, a Windows-only tool, and instructs users to deploy a Windows VM. There are no Linux or cross-platform alternatives or examples provided, nor is there mention of Linux-compatible tools or procedures. The guidance is entirely Windows-centric, with no parity for Linux users.
Recommendations
- Include instructions for performing SMB file share migrations from a Linux VM, using tools such as rsync, smbclient, or mount.cifs.
- Provide example Linux command-line workflows for mounting Azure SMB shares and copying data.
- Mention cross-platform tools (e.g., AzCopy, if applicable) and clarify their suitability for SMB file shares.
- Structure the documentation to present both Windows and Linux options, or at least acknowledge Linux as a supported platform for such migrations.
- Add a section comparing the pros and cons of Windows and Linux migration approaches, including performance and compatibility notes.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-managed-identities.md
...cles/storage/file-sync/file-sync-managed-identities.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on PowerShell for all command-line examples and configuration steps, with no mention of Linux shell equivalents or cross-platform CLI tools. All scripting and automation guidance is provided using PowerShell cmdlets, which are native to Windows environments. There is no discussion of how to perform these tasks on Linux servers, nor are there Bash, Azure CLI, or cross-platform instructions. The prerequisites and agent installation steps also implicitly assume a Windows environment.
Recommendations
- Add Azure CLI examples for all configuration and verification steps, as Azure CLI is cross-platform and works on both Linux and Windows.
- Explicitly state whether the Azure File Sync agent and managed identity features are supported on Linux servers, or clarify that they are Windows-only if that is the case.
- If Linux is supported, provide Bash or shell script equivalents for PowerShell commands.
- Include guidance for managing Azure Arc-enabled Linux servers, if applicable, and how to enable managed identities on those.
- Mention any platform-specific limitations or requirements up front, so Linux administrators know what is or isn't possible.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-release-notes.md
.../articles/storage/file-sync/file-sync-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation for Azure File Sync is heavily biased toward Windows environments. All instructions, requirements, and examples are exclusively for Windows Server, with repeated references to Windows-specific tools (e.g., PowerShell cmdlets, Robocopy, NTFS, FSRM, .NET Framework, Windows Update). There is no mention of Linux support, examples, or equivalent tooling, and the documentation assumes the reader is operating in a Windows ecosystem.
Recommendations
- Clearly state early in the documentation whether Azure File Sync supports only Windows or if there are any Linux/UNIX options.
- If Linux support is available or planned, provide equivalent instructions, examples, and troubleshooting steps for Linux environments.
- If only Windows is supported, explicitly mention this limitation to set expectations for cross-platform users.
- Where possible, reference cross-platform tools or protocols (e.g., SMB, NFS) and clarify their support or limitations on non-Windows systems.
- Provide a comparison table or section outlining feature parity (or lack thereof) between Windows and Linux for Azure Files and related sync capabilities.
- If PowerShell is required, note whether PowerShell Core (cross-platform) is supported, and provide examples for Linux/macOS if applicable.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-networking-overview.md
...les/storage/file-sync/file-sync-networking-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation is heavily oriented toward Windows environments, consistently referencing Windows Server as the on-premises platform, providing only PowerShell examples and cmdlets, and omitting Linux equivalents or guidance. There is no mention of Linux support or examples for configuring Azure File Sync, and all tooling and instructions assume a Windows context.
Recommendations
- Explicitly state whether Azure File Sync supports Linux servers as endpoints. If not, clarify this early in the documentation.
- If Linux support is available or planned, provide equivalent instructions and examples for Linux environments, including relevant CLI commands (e.g., Bash, Azure CLI) and configuration steps.
- Where PowerShell cmdlets are referenced (e.g., Set-StorageSyncProxyConfiguration, Resolve-DnsName), provide alternative commands for Linux (such as Azure CLI, curl, or nslookup).
- Avoid language that assumes Windows as the only on-premises platform; instead, use inclusive phrasing such as 'on-premises server' and specify OS requirements where relevant.
- Add a section or note summarizing platform support and any limitations for non-Windows environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-server-endpoint-create.md
.../storage/file-sync/file-sync-server-endpoint-create.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (e.g., Invoke-StorageSyncFileRecall) and Windows file path conventions (e.g., F:\sync1). There are no examples or instructions for Linux systems, nor is there mention of Linux compatibility or equivalent tools. The documentation assumes the use of Windows servers and tools throughout, without acknowledging or providing guidance for Linux environments.
Recommendations
- Explicitly state platform support (Windows-only or cross-platform) at the beginning of the documentation.
- If Linux is supported, provide equivalent Linux command-line instructions (e.g., using Azure CLI, shell scripts) alongside PowerShell examples.
- Use platform-agnostic path examples or provide both Windows (e.g., F:\sync1) and Linux (e.g., /mnt/sync1) path formats.
- Mention any limitations or differences in feature support between Windows and Linux servers.
- Reference Linux tools or commands where appropriate, or clarify if certain features (like cloud tiering or file recall) are unavailable on Linux.
- Include troubleshooting or best practices sections specific to Linux environments if supported.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-replace-server.md
...articles/storage/file-sync/file-sync-replace-server.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively references Windows Server as the supported OS, uses Windows-specific tools (Robocopy), and provides no Linux or cross-platform alternatives or examples. All instructions and terminology assume a Windows environment, with no mention of Linux compatibility or equivalent procedures.
Recommendations
- Clarify early in the documentation whether Azure File Sync supports only Windows Server, or if Linux is supported/planned.
- If Linux support exists or is planned, provide equivalent instructions and examples for Linux environments, including alternative tools (e.g., rsync instead of Robocopy).
- If only Windows is supported, explicitly state this at the beginning to set user expectations and avoid confusion.
- Where possible, use cross-platform terminology and tools, or at least mention Linux alternatives for common tasks (such as file copying and permissions management).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-networking-endpoints.md
...es/storage/file-sync/file-sync-networking-endpoints.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias in several ways: it consistently refers to 'Windows file servers' as the only supported on-premises server type for Azure File Sync, provides PowerShell examples and output before or instead of cross-platform alternatives, and uses Windows-centric terminology and tools (e.g., PowerShell cmdlets, Windows DNS output). While Azure CLI and Bash examples are included for some tasks, certain operations (such as disabling the Storage Sync Service public endpoint) are only possible via PowerShell, with the documentation explicitly stating that Azure CLI does not support the operation. There is also a lack of Linux-specific guidance or examples for on-premises scenarios, and output samples are often shown only for Windows environments.
Recommendations
- Clarify in the introduction that Azure File Sync currently only supports Windows file servers, but provide explicit guidance for Linux users seeking similar functionality or alternatives.
- Where PowerShell is used, always provide equivalent Azure CLI/Bash examples and outputs, or clearly state when a feature is not available cross-platform.
- When showing command output (e.g., nslookup), include both Windows and Linux/macOS output formats to help users on all platforms.
- If certain features are Windows-only (such as the File Sync agent), make this explicit and suggest alternative Azure Files access patterns for Linux environments.
- Consider providing a table summarizing which operations are supported on which platforms (Windows, Linux, macOS, Portal, PowerShell, CLI) for transparency.
- Where possible, advocate for parity in Azure CLI support for operations currently limited to PowerShell, and link to relevant Azure feedback channels.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-extension.md
...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, both in prerequisites and in all provided examples. It explicitly states that Azure File Sync is only supported on Windows, and all instructions, settings, and validation steps refer to Windows-specific tools, paths, and concepts (e.g., C:\ paths, Windows services, Programs and Features). There are no Linux examples, nor any mention of Linux equivalents or alternatives. Windows tools and patterns (such as PowerShell, Windows file paths, and Windows service names) are used throughout, and the documentation does not address Linux users beyond stating lack of support.
Recommendations
- If Azure File Sync is not supported on Linux, clarify this prominently at the start and suggest alternative solutions for Linux users (such as using Azure File Share with native Linux SMB/NFS clients or third-party sync tools).
- If future Linux support is planned, provide a roadmap or link to updates.
- Where possible, provide parity in documentation by including a section or links for Linux users, even if only to explain why the feature is not available and what alternatives exist.
- Avoid using Windows-specific terminology (such as C:\ paths, Programs and Features, or Windows service names) in general Azure Arc documentation unless the feature is truly Windows-only.
- In cross-platform documentation, always present both Windows and Linux options/examples, or clearly indicate when a feature is platform-specific.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-resource-move.md
.../articles/storage/file-sync/file-sync-resource-move.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell for command-line examples and instructions. There are no equivalent CLI examples for Linux (such as Azure CLI or Bash), and the only scripting tool mentioned is PowerShell, which is native to Windows. No Linux-specific tools, commands, or patterns are referenced, and all automation guidance assumes a Windows-centric environment.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell for all resource management tasks, especially for assigning managed identities and role assignments.
- Explicitly mention that all operations can be performed from any OS using the Azure CLI or portal, and provide cross-platform instructions.
- Where PowerShell is referenced, add a note or section for Bash/Linux users, including sample scripts or commands.
- Review all automation and scripting guidance to ensure it is not Windows-specific, and add Linux/macOS parity where possible.
- Include a table or section comparing PowerShell and Azure CLI commands for common tasks in Azure File Sync resource management.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-share-to-share-migration.md
...torage/file-sync/file-sync-share-to-share-migration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows environments. All migration steps, examples, and tooling (such as Robocopy, PowerShell cmdlets, and Storage Migration Service) are Windows-specific. There are no Linux or cross-platform examples, and the instructions assume the use of Windows Server VMs and Windows-native tools. Linux equivalents or alternatives are not mentioned or suggested.
Recommendations
- Provide equivalent Linux-based migration instructions, including how to mount Azure File Shares on Linux and use tools like rsync or azcopy for file transfer.
- Include examples using Azure CLI or Bash scripts in addition to PowerShell cmdlets.
- Mention and document any limitations or differences when using Azure File Sync with Linux-based file servers.
- List both Windows and Linux options for each migration scenario, or clarify if Azure File Sync is only supported on Windows (and state this explicitly at the top).
- If Robocopy is recommended, also suggest cross-platform tools (e.g., azcopy, rsync) and provide sample commands.
- When referencing Storage Migration Service, note that it is a Windows-only tool and suggest alternatives for non-Windows environments if available.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/encryption-in-transit-for-nfs-shares.md
.../storage/files/encryption-in-transit-for-nfs-shares.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits mild Windows bias in the registration instructions, where PowerShell is presented before Azure CLI, and a PowerShell screenshot is used to illustrate verification, despite the rest of the guide being Linux-focused. The rest of the content is strongly Linux-centric, with all operational examples and supported platforms being Linux distributions. However, the use of PowerShell as a primary registration method and as a visual reference may signal a Windows-first perspective.
Recommendations
- Present Azure CLI registration instructions before PowerShell, as CLI is cross-platform and more relevant to Linux users.
- Replace or supplement the PowerShell screenshot in the verification section with a Linux terminal screenshot to match the Linux context.
- Clarify that PowerShell registration is optional and primarily for Windows users, while CLI is recommended for Linux environments.
- Ensure that all visual aids and examples reflect the primary audience's platform (Linux) for this scenario.
- If possible, provide Bash or shell script equivalents for any administrative tasks currently shown only in PowerShell.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/analyze-files-metrics.md
...b/main/articles/storage/files/analyze-files-metrics.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 detailed PowerShell examples (a Windows-centric tool) before Azure CLI, omitting any Linux shell or scripting examples, and referencing Windows tools and patterns. There are no explicit Linux or Bash examples, and troubleshooting links default to Windows tabs. The .NET SDK section, while cross-platform, is not specifically Linux-focused. The documentation assumes familiarity with Windows-centric workflows and does not address Linux users' needs directly.
Recommendations
- Add Bash and/or Python scripting examples for metric retrieval using Azure CLI, demonstrating usage in Linux environments.
- Explicitly mention Linux support and provide Linux-specific guidance or notes where relevant (e.g., obtaining resource IDs, authentication).
- Balance the order of examples: present Azure CLI (cross-platform) before PowerShell, or provide both side-by-side.
- Include troubleshooting links and references that are not Windows-defaulted; ensure Linux troubleshooting is equally visible.
- Where screenshots or UI instructions are given, clarify any OS-specific differences or provide Linux desktop examples if relevant.
- Consider adding a section or callout for Linux administrators, summarizing key steps and tools for monitoring Azure Files from Linux.