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 1-25 of 1657 flagged pages
Storage
Migrate to Azure Files Using RoboCopy
...cles/storage/files/storage-files-migration-robocopy.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
This documentation is heavily focused on Windows, specifically the use of RoboCopyโa Windows-only toolโfor migrating to Azure Files over SMB. While the introduction mentions that sources can include Linux servers, all migration steps, examples, and troubleshooting are exclusively for Windows environments. There are no Linux or macOS migration instructions, nor are alternative tools for those platforms discussed. Windows Server features and PowerShell are referenced throughout, and mounting instructions are only for Windows.
Recommendations
- Add a section describing migration options for Linux/macOS users, such as using smbclient, rsync over SMB mounts, or other cross-platform tools.
- Include Linux/macOS examples for mounting Azure file shares and copying data.
- Clarify that RoboCopy is Windows-only and suggest alternatives for non-Windows environments.
- Reorder or balance examples so that Linux/macOS scenarios are presented alongside Windows, where applicable.
Create Pull Request
Storage
Run an Azure Function in response to a blob rehydration event
...ticles/storage/blobs/archive-rehydrate-handle-event.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio on Windows. All examples and instructions assume use of Visual Studio (with screenshots), and the function app creation process explicitly sets the operating system to Windows. There are no examples or guidance for Linux/macOS users, such as using VS Code, Azure CLI, or other cross-platform tools. The publishing instructions also target Azure Function App (Windows) only.
Recommendations
- Add parallel instructions for developing and testing Azure Functions using VS Code, which is cross-platform, or the Azure CLI.
- Include guidance for creating and deploying function apps with Linux as the operating system, and clarify when Windows is required.
- Provide code snippets and steps for installing required packages and running/debugging the function on Linux/macOS.
- Mention and link to documentation for cross-platform development options in the prerequisites and throughout the article.
- Where possible, show screenshots or terminal commands for Linux/macOS environments.
Storage
Migrate files between file shares when using Azure File Sync
...torage/file-sync/file-sync-share-to-share-migration.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation for migrating files between Azure file shares using Azure File Sync is heavily Windows-centric. All examples and instructions assume the use of Windows Server, Windows VMs, PowerShell cmdlets, and Windows-only tools like Robocopy. There are no Linux/macOS equivalents or alternative instructions provided, and Windows terminology and tooling are presented exclusively and first throughout the page.
Recommendations
- Clearly state early in the documentation that Azure File Sync is a Windows-only feature, if applicable, to set expectations for non-Windows users.
- If any part of the migration process (such as copying files between shares in Azure) can be performed from Linux/macOS (e.g., using azcopy, Azure CLI, or SMB mounting), provide parallel instructions and examples.
- Mention cross-platform tools (like azcopy) where appropriate, especially for file copy operations that do not require Windows-specific features.
- Where PowerShell or Robocopy are referenced, note their platform limitations and suggest alternatives if available.
- Add a section clarifying platform requirements and limitations for Azure File Sync and related migration scenarios.
Storage
On-premises NAS migration to Azure File Sync via Data Box
...ge/files/storage-files-migration-nas-hybrid-databox.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 Server as the migration target and operational platform. All examples and instructions use Windows-native tools (Robocopy, Event Viewer), and there are no Linux/macOS equivalents or guidance for those environments. The migration workflow assumes the use of Windows Server for Azure File Sync, with no mention of Linux-based alternatives or cross-platform tooling.
Recommendations
- Clearly state at the beginning that Azure File Sync is a Windows Server-only feature, and that the migration workflow is designed for Windows environments.
- Where possible, provide guidance for Linux users on how to migrate NAS data to Azure Files (even if Azure File Sync is not supported), such as using rsync or azcopy for initial data transfer.
- Add a section outlining alternative workflows for organizations that do not have Windows Server, or link to documentation for migrating NAS data to Azure Files without Azure File Sync.
- Explicitly mention that tools like Robocopy and Event Viewer are Windows-only, and suggest Linux/macOS alternatives for file transfer and monitoring where applicable.
Storage
Microsoft Entra Kerberos Authentication for Azure Files
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-auth-hybrid-identities-enable.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily Windows-centric, with all client configuration, prerequisites, and permission management steps referencing Windows operating systems, tools, and patterns (such as PowerShell, Windows File Explorer, Group Policy, Intune, registry edits, and Windows-specific commands). No Linux or macOS client scenarios, tools, or equivalents are mentioned, and all examples and instructions assume a Windows environment. This creates friction for non-Windows users seeking to use Azure Files with Entra Kerberos authentication.
Recommendations
- Explicitly state in the prerequisites and introduction whether Linux/macOS clients are supported or not for Microsoft Entra Kerberos authentication with Azure Files.
- If Linux/macOS support is possible, provide equivalent instructions for configuring Kerberos ticket retrieval, mounting SMB shares, and managing permissions on those platforms.
- If Linux/macOS support is not available, clarify this limitation early in the documentation to set expectations for cross-platform users.
- Where possible, reference cross-platform tools (such as Azure CLI) and clarify any OS-specific requirements or limitations.
- Consider adding a section on alternative approaches for non-Windows clients, or link to relevant documentation.
Storage
On-premises NAS migration to Azure Files
...age/files/storage-files-migration-nas-cloud-databox.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation for migrating on-premises NAS to Azure Files via DataBox is heavily Windows-centric. It exclusively recommends using Windows Server and RoboCopy for file transfer, omits Linux/macOS migration tooling and examples, and provides detailed guidance for Windows environments (such as mounting SMB shares and configuring DFS-N). Linux equivalents (e.g., rsync, smbclient, NFS migration) are not mentioned, and the instructions for mounting Azure file shares and running migration jobs are Windows-only.
Recommendations
- Add Linux/macOS migration instructions, including recommended tools (e.g., rsync, smbclient) for copying files from NAS to DataBox and from DataBox to Azure Files.
- Provide examples for mounting Azure file shares on Linux/macOS using SMB (e.g., mount.cifs) and NFS (where supported).
- Include troubleshooting tips for Linux/macOS environments, such as permissions, performance tuning, and compatibility notes.
- Clarify which steps are Windows-only and offer alternative workflows for non-Windows environments.
- Reference official Azure documentation for Linux/macOS clients where available.
Storage
Deploy Tiger Bridge Continuous Data Protection, Archive and Disaster Recovery with Azure Blob Storage
...up-archive-disaster-recovery/tiger-bridge-cdp-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation for deploying Tiger Bridge CDP, Archive, and Disaster Recovery with Azure Blob Storage is heavily Windows-centric. It assumes the use of a Windows file server, references Windows-specific features (Volume Shadow Copy Service, Windows Explorer, DFSR), and provides instructions and screenshots exclusively for Windows environments. There are no examples, guidance, or mentions of Linux or macOS deployment, configuration, or usage.
Recommendations
- Clarify early in the documentation whether Tiger Bridge is Windows-only, or if Linux/macOS support exists. If Tiger Bridge is cross-platform, add Linux/macOS installation and configuration steps.
- Provide equivalent examples for Linux environments, such as how to restore files, manage versions, and interact with Azure Blob Storage using Tiger Bridge on Linux (if supported).
- If Tiger Bridge is Windows-only, explicitly state this in the prerequisites and introduction to avoid confusion for non-Windows users.
- If partial Linux support exists (e.g., CLI tools, API access), document those workflows and tools alongside Windows instructions.
Storage
Deploy hybrid data infrastructure with Tiger Bridge and Azure Blob Storage
...ary-secondary-storage/tiger-bridge-deployment-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows environments, with Tiger Bridge described as fully integrated with NTFS/ReFS and running on Microsoft Windows Server. All deployment steps, screenshots, and examples assume a Windows file server, and there are no Linux/macOS deployment instructions or examples. Windows-specific features like Explorer shell extensions are mentioned, and no Linux equivalents or CLI examples are provided. While Tiger Bridge can manage NAS sources via SMB/NFS, the guide does not cover deployment or operation on Linux servers or provide parity for Linux/macOS users.
Recommendations
- Add explicit guidance for deploying Tiger Bridge in Linux environments, if supported, including installation steps, configuration, and management.
- Provide Linux/macOS CLI examples for pairing with Azure Blob Storage and managing policies, if Tiger Bridge offers such interfaces.
- Clarify platform limitations early in the documentation: if Tiger Bridge is Windows-only, state this clearly at the top.
- If Tiger Bridge can run as a gateway on Linux for NAS/NFS sources, include a dedicated section with Linux deployment steps and screenshots.
- Mention alternative management tools for Linux environments, or provide links to relevant documentation.
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
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments, with all examples and instructions using Windows-specific tools (PowerShell, Command Prompt, Registry Editor, NTFS attributes, Windows services). There are no Linux or macOS equivalents or guidance, and the documentation assumes the use of Windows Server for Azure File Sync management.
Recommendations
- Clarify early in the documentation that Azure File Sync is only supported on Windows Server, if that is the case. If Linux/macOS support is planned or partial, provide equivalent instructions or note limitations.
- If any cross-platform management is possible (e.g., via REST API, Azure Portal, or CLI), include those examples alongside Windows-specific ones.
- Explicitly state the platform requirements and limitations for Azure File Sync, so non-Windows users are not misled.
- If Linux/macOS agents or tools exist, provide parity examples and troubleshooting steps.
- Consider adding a section for alternative solutions for Linux/macOS users, such as using Azure Files directly with SMB/NFS clients.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows environments. It assumes the recovery is performed on a Windows Server or Azure VM running Windows, references installation of the Azure File Sync agent specifically for Windows, and provides only a Robocopy command (a Windows tool) for data recovery. There are no Linux/macOS instructions, examples, or alternative tools mentioned.
Recommendations
- Add guidance for recovering Azure File Sync on Linux or macOS systems, if supported.
- Provide equivalent Linux/macOS commands (e.g., using rsync instead of Robocopy) for data copying.
- Clarify platform requirements and limitations at the beginning of the document.
- If Azure File Sync is Windows-only, state this explicitly and link to alternatives for Linux/macOS users.
Storage
Create an Azure File Sync Server Endpoint
.../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 for creating an Azure File Sync server endpoint exhibits a notable Windows bias. It references PowerShell cmdlets (e.g., Invoke-StorageSyncFileRecall) as the primary method for managing sync and file recall, with no mention of Linux or macOS equivalents. The examples and terminology (drive letters, RoboCopy, F:\ paths) are Windows-centric, and there are no instructions or examples for performing these tasks on Linux or macOS. This creates friction for non-Windows users and implies that Azure File Sync is primarily intended for Windows environments.
Recommendations
- Explicitly state Azure File Sync's platform support (e.g., Windows-only, or if Linux/macOS support is planned or available).
- If Linux/macOS support exists, provide equivalent examples and tooling instructions for those platforms.
- If PowerShell is required, clarify whether PowerShell Core (cross-platform) is supported and provide installation steps for Linux/macOS.
- Avoid using Windows-specific terminology (e.g., drive letters, RoboCopy) without clarifying platform applicability.
- Add a section addressing Linux/macOS users, including limitations, alternatives, or workarounds.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation for Azure File Sync is heavily focused on Windows Server, with all examples, deployment instructions, and benefits described exclusively in terms of Windows environments. There is no mention of Linux or macOS support, nor any examples or guidance for those platforms. Windows Server is presented as the only supported on-premises cache, and Windows-specific tools and patterns (such as clustering and agent installation) are referenced without Linux equivalents.
Recommendations
- Clarify platform support: Explicitly state whether Linux or macOS servers are supported or not for Azure File Sync.
- Add Linux/macOS parity: If supported, provide equivalent examples, deployment steps, and architectural guidance for Linux/macOS systems.
- Mention alternatives: If Azure File Sync is Windows-only, suggest alternative solutions for Linux/macOS users (e.g., direct Azure Files mounting via SMB/NFS, third-party sync tools).
- Reorder examples: Where possible, present platform-agnostic information first, or provide parallel examples for Windows and Linux/macOS.
- Highlight protocol support: Since SMB and NFS are mentioned, clarify how these protocols can be used from non-Windows clients and what limitations exist.
Storage
Manage Registered Servers with Azure File Sync
...les/storage/file-sync/file-sync-server-registration.md
High Priority
View Details →
Detected Bias Types
Windows Only
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is exclusively focused on Windows Server environments, with all instructions, prerequisites, and examples tailored to Windows. PowerShell is the only CLI shown, and Windows-specific tools, paths, and configuration files are referenced throughout. There is no mention of Linux or macOS support, nor any examples or guidance for non-Windows platforms.
Recommendations
- Clarify platform support: Explicitly state whether Azure File Sync supports only Windows Server, or if Linux/macOS are supported or planned.
- If Linux/macOS support exists or is planned, provide equivalent instructions, examples, and tooling for those platforms.
- If Azure File Sync is Windows-only, add a prominent note at the top of the documentation to inform users from other platforms.
- Consider providing alternative solutions or links for Linux/macOS users seeking similar functionality.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows Server environments, with monitoring instructions and tooling (event logs, performance counters) specific to Windows. There are no Linux/macOS examples or guidance, and all references to on-premises monitoring assume Windows Server. Windows tools (Event Viewer, Perfmon.exe) are mentioned exclusively, and the documentation does not address Linux-based file servers or agents.
Recommendations
- Clarify early in the documentation that Azure File Sync is a Windows Server-only solution, or explicitly state platform limitations.
- If Linux/macOS support is planned or available, provide equivalent monitoring instructions, including log file locations, supported tools, and example commands for those platforms.
- If only Windows is supported, add a prominent note to inform non-Windows users that Azure File Sync monitoring is not available for Linux/macOS servers.
- Consider including cross-platform alternatives or links to Azure Monitor documentation for Linux servers where relevant.
- Reorder sections to make platform requirements clear before presenting Windows-specific tooling.
Storage
On-premises NAS migration to Azure File Sync
...es/storage/files/storage-files-migration-nas-hybrid.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is strongly Windows-centric, with all migration steps requiring a Windows Server as an intermediary and exclusively referencing Windows tools (RoboCopy, Windows Server, DFS-Namespace, Active Directory). No Linux or macOS migration paths, tools, or examples are provided, and the workflow assumes Windows environments throughout.
Recommendations
- Provide alternative migration workflows for Linux-based NAS appliances, such as using Linux SMB clients or rsync to migrate data directly to Azure File Shares.
- Include examples using Linux command-line tools (e.g., smbclient, rsync, Azure CLI) for copying data from NAS to Azure.
- Clarify whether Azure File Sync or Azure Storage Mover can be used without a Windows Server intermediary, and document any Linux-compatible approaches.
- Add troubleshooting and cut-over guidance for non-Windows environments, including mapping Linux users/groups and permissions.
- Present Windows and Linux/macOS examples side-by-side, or clearly indicate Windows-only requirements up front.
Storage
Configure cloud trust between AD DS and Microsoft Entra ID
...iles/storage-files-identity-auth-hybrid-cloud-trust.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with all prerequisites, examples, and tooling focused on Windows and PowerShell. Linux/macOS clients are not mentioned, and no equivalent instructions or tools are provided for non-Windows platforms. Windows-specific tools (PowerShell, Windows File Explorer, Group Policy) are used exclusively, and Windows is listed as a required client OS.
Recommendations
- Explicitly state whether Linux/macOS clients are supported for accessing Azure Files with Entra Kerberos in hybrid scenarios.
- If Linux/macOS support is possible, provide equivalent instructions for those platforms, including required packages, configuration steps, and example commands.
- Mention and document any Linux tools (e.g., kinit, smbclient, mount.cifs) that can be used for Kerberos authentication to Azure Files, if supported.
- Clarify prerequisites for non-Windows environments, or provide guidance for alternative approaches if only Windows is supported.
- If only Windows is supported, make this limitation clear at the beginning of the documentation.
Storage
On-premises NAS migration to Azure Files
...age/files/storage-files-migration-nas-cloud-databox.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. All migration steps rely on Windows Server and RoboCopy, a Windows-only tool, with no Linux/macOS alternatives or guidance. Windows-specific networking, authentication, and troubleshooting are discussed in detail, while Linux is only briefly mentioned in VPN configuration links. There are no examples or instructions for performing the migration from Linux or macOS systems, nor are cross-platform tools (e.g., rsync, smbclient) referenced.
Recommendations
- Add a parallel migration workflow for Linux/macOS environments, including supported tools (e.g., rsync, smbclient, cifs-utils) for copying files to DataBox and Azure file shares.
- Provide Linux/macOS-specific examples for mounting Azure file shares and performing incremental file copy operations.
- Discuss file permission and metadata preservation strategies for non-Windows platforms.
- Reference cross-platform tools and scripts where possible, and clarify any limitations or differences in fidelity.
- Include troubleshooting guidance for Linux/macOS users, especially around SMB mounting, authentication, and performance tuning.
Storage
Run an Azure Function in response to a blob rehydration event
...ticles/storage/blobs/archive-rehydrate-handle-event.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased towards Windows, with all development and deployment instructions centered on Visual Studio (Windows-only), explicit instructions to select Windows as the OS for the Function App, and publishing guidance exclusively for 'Azure Function App (Windows)'. There are no examples or guidance for Linux/macOS users, nor are alternative tools or workflows (such as VS Code, Azure CLI, or cross-platform .NET tooling) mentioned. Package installation is shown only via PowerShell/NuGet Package Manager Console, which is also Windows-centric.
Recommendations
- Add instructions for developing and testing Azure Functions using cross-platform tools like VS Code and the Azure Functions Core Tools CLI.
- Include examples for package installation using dotnet CLI (e.g., 'dotnet add package ...'), which works on Linux/macOS.
- Provide guidance for creating and publishing Azure Function Apps on Linux, including selecting Linux as the OS in the portal and using Azure CLI or VS Code for deployment.
- Mention supported development environments for macOS and Linux, and link to relevant documentation.
- Ensure screenshots and step-by-step instructions are not exclusively tied to Windows/Visual Studio.
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 Only
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
This documentation page is heavily biased towards Windows. The Azure Storage Emulator is explicitly Windows-only, with all installation, usage, and command-line instructions referencing Windows tools, patterns, and paths (e.g., SQL Server LocalDB, Windows authentication, Start menu, Windows taskbar, PowerShell). There are no Linux/macOS usage examples, and the only mention of cross-platform support is a brief note recommending Azurite for non-Windows platforms, without any substantive guidance or parity in examples.
Recommendations
- Add clear, step-by-step instructions for using Azurite on Linux/macOS, including installation, initialization, and usage.
- Provide equivalent command-line and scripting examples for Azurite, using Bash or other common Linux/macOS tools.
- Include a comparison table highlighting feature parity and differences between Storage Emulator (Windows) and Azurite (cross-platform).
- Move the Azurite recommendation and cross-platform guidance to the top of the page, making it the primary focus for new development.
- Explicitly state that Storage Emulator is deprecated and Windows-only at the beginning, with links to Azurite documentation for Linux/macOS users.
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
Summary
The documentation is strongly oriented toward Windows environments. It references Windows Server features (NTFS, Event Viewer, Windows Server data deduplication), Windows-specific attributes (FILE_ATTRIBUTE_RECALL_ON_DATA_ACCESS), and PowerShell cmdlets (Invoke-StorageSyncFileRecall) without mentioning Linux or macOS equivalents or support. There are no examples or guidance for non-Windows platforms, and all operational details assume a Windows file server context.
Recommendations
- Clarify platform support: Explicitly state whether Azure File Sync and cloud tiering are supported on Linux/macOS, and if not, provide alternatives or guidance.
- If Linux/macOS support exists, add equivalent examples and instructions for those platforms, including how to monitor, configure, and troubleshoot tiering.
- Mention Linux file system attributes and tools where relevant, or note their absence.
- Provide parity in troubleshooting steps, e.g., how to check tiering health or logs on Linux/macOS.
- If only Windows is supported, make this clear early in the documentation to set user expectations.
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 environments, with explicit statements that Azure File Sync is only supported on Windows. All examples, settings, and instructions are tailored for Windows servers, with no Linux/macOS equivalents or alternatives provided. Windows-specific tools, paths, and concepts (e.g., C:\ paths, Windows services, Programs and Features) are used throughout. Linux users are excluded from the described functionality and cannot complete the task.
Recommendations
- Clearly state Windows-only support at the top and in prerequisites (already present, but could be more prominent).
- Provide links or guidance for Linux/macOS users on alternative Azure file sync solutions, if any exist.
- If future support for Linux is planned, mention roadmap or preview features.
- Where possible, generalize steps (e.g., Azure CLI usage) to clarify which steps are cross-platform and which are Windows-specific.
- Add a comparison table or FAQ addressing why Linux is not supported and what alternatives exist.
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 Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively describes silent installation of the Azure File Sync agent using Windows-specific tools (msiexec), with all examples and parameters tailored for Windows Server environments. No Linux or macOS installation methods, commands, or equivalents are provided, and the documentation assumes a Windows context throughout.
Recommendations
- Clarify in the introduction that Azure File Sync agent is only available for Windows, if that is the case.
- If Linux/macOS support exists or is planned, provide equivalent installation instructions and examples for those platforms.
- Explicitly state platform requirements and limitations to avoid confusion for non-Windows users.
- If possible, mention alternative solutions or approaches for Linux/macOS users who may be seeking similar functionality.
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 is heavily focused on Windows environments, referencing Windows-specific tools (FSRM, NTFS, Robocopy, fsutil) and commands, and does not provide Linux/macOS equivalents or guidance. All examples and operational procedures assume Windows Server, with no mention of how (or if) Azure File Sync cloud tiering can be used or monitored from Linux or macOS systems.
Recommendations
- Clarify Azure File Sync's platform supportโexplicitly state if Linux/macOS are unsupported, or provide guidance for those platforms if supported.
- If possible, include equivalent commands or procedures for Linux/macOS (e.g., how to check cluster size, monitor tiering, etc.).
- Add a section addressing cross-platform considerations, including limitations and alternatives for non-Windows users.
- If Azure File Sync is Windows-only, make this clear at the beginning of the documentation to set expectations.
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 macOS support, nor are alternative steps or tools provided for non-Windows platforms. The use of Windows-specific tools (PowerShell, Internet Explorer, Server Manager) and the absence of cross-platform guidance create a strong Windows bias.
Recommendations
- Clarify in the introduction whether Azure File Sync supports only Windows or if Linux/macOS alternatives exist.
- If Linux/macOS support is available, provide equivalent setup instructions, examples, and screenshots for those platforms.
- Mention and link to any cross-platform tools or APIs that can be used to interact with Azure File Sync from Linux/macOS.
- If Azure File Sync is Windows-only, explicitly state this limitation early in the documentation to set expectations for non-Windows users.
- Consider adding a comparison table of supported operating systems and features.
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 Windows-centric, with all examples, instructions, and tooling focused exclusively on Windows Server environments. PowerShell is used for all command-line examples, and Windows-specific configuration files and tools (e.g., netsh, machine.config) are referenced throughout. There are no Linux or macOS instructions, nor any mention of how (or if) Azure File Sync can be configured or used on non-Windows platforms.
Recommendations
- Clarify platform support: Explicitly state whether Azure File Sync is Windows-only or if Linux/macOS are supported. If not supported, make this clear early in the documentation.
- If Linux/macOS support exists or is planned, provide equivalent examples for proxy/firewall configuration using common Linux tools (e.g., iptables, ufw, curl, wget, environment variables for proxy settings).
- Reference Linux equivalents for .NET proxy configuration if the agent runs on .NET Core on Linux.
- Include troubleshooting steps and connectivity tests for Linux/macOS environments, using bash scripts or native tools.
- If only Windows is supported, add a prominent note to prevent confusion for non-Windows users.