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 26-50 of 1657 flagged pages
Storage
How to use managed identities with Azure File Sync
...cles/storage/file-sync/file-sync-managed-identities.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows environments, with all command-line examples provided exclusively in PowerShell and references to Windows-specific tools (e.g., Azure File Sync agent, Az.StorageSync PowerShell module). There are no examples or guidance for configuring or managing Azure File Sync managed identities from Linux or macOS systems, nor are cross-platform CLI alternatives (such as Azure CLI or REST API) mentioned. The documentation assumes the use of Windows servers or Azure Arc-enabled servers, which may limit Linux user accessibility.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works on Linux/macOS.
- Clarify whether Azure File Sync agent and management tasks can be performed on Linux servers, and if so, provide Linux-specific instructions.
- Mention REST API alternatives for automation and scripting from non-Windows platforms.
- Explicitly state platform requirements and limitations for Azure File Sync and managed identities.
- Reorder examples so that cross-platform methods (Azure CLI, REST API) are presented before or alongside Windows/PowerShell methods.
Create Pull Request
Storage
Azure File Sync networking considerations
...les/storage/file-sync/file-sync-networking-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows Server environments, with examples and instructions tailored exclusively for Windows users. PowerShell is the only automation tool referenced for configuration tasks, and Windows-specific terminology and patterns are used throughout. There are no Linux or macOS examples, nor any mention of how non-Windows systems might interact with Azure File Sync or related networking configurations.
Recommendations
- Add explicit statements clarifying Azure File Sync is only supported on Windows, and provide guidance for Linux/macOS users seeking similar solutions.
- Where PowerShell is used for configuration (e.g., proxy settings, DNS), offer equivalent instructions using cross-platform tools (such as Azure CLI or REST API), or clarify if these steps are Windows-only.
- Include Linux/macOS examples for DNS resolution (e.g., show 'nslookup' or 'dig' commands alongside PowerShell examples).
- If Azure File Sync is not supported on Linux/macOS, provide links to alternative Azure file synchronization solutions for those platforms.
- Reorder examples and instructions so that platform-agnostic or cross-platform tools (like Azure CLI, REST API) are mentioned before or alongside Windows/PowerShell tools.
Storage
Plan for an Azure File Sync Deployment
.../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 is heavily biased toward Windows environments, specifically Windows Server. All deployment, management, and troubleshooting instructions are exclusively for Windows Server, with no mention of Linux or macOS for Azure File Sync scenarios. All command-line examples use PowerShell, and only Windows tools and patterns are referenced. Linux and macOS are only mentioned as SMB clients for direct mounting, not as supported platforms for Azure File Sync itself.
Recommendations
- Clearly state at the beginning that Azure File Sync is only supported on Windows Server, and that Linux/macOS are not supported for the sync agent.
- Provide alternative guidance or links for Linux/macOS users who want to interact with Azure Files (e.g., mounting via SMB/NFS, rsync-based solutions, or third-party sync tools).
- In sections discussing direct mounting, include Linux/macOS mounting examples and reference relevant documentation.
- Where PowerShell or Windows-specific tools are used, clarify that these are only applicable to Windows Server scenarios.
- Consider a comparison table or FAQ highlighting feature parity and limitations across Windows, Linux, and macOS for Azure Files and Azure File Sync.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily Windows-centric, assuming the use of Windows Server throughout. All steps reference Windows Server only, with no mention of Linux or macOS alternatives. The only file copy tool suggested is Robocopy, a Windows-specific utility, and user cut-over options reference Windows features like DFS-N. No Linux-compatible instructions, tools, or examples are provided.
Recommendations
- Clarify early that Azure File Sync is only supported on Windows Server, if that is the case. If Linux/macOS support is possible or planned, add equivalent instructions for those platforms.
- Where file copy operations are described, suggest cross-platform tools (e.g., rsync for Linux/macOS) or note alternatives for non-Windows environments.
- When mentioning features like DFS-N, explain if there are similar solutions for Linux/macOS, or explicitly state that these are Windows-only features.
- If the product is Windows-only, make this limitation clear at the top of the documentation to set expectations for non-Windows users.
High Priority
View Details →
Detected Bias Types
Windows Only
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation for Azure File Sync is heavily Windows-centric. It exclusively references Windows Server as the supported platform, with no mention of Linux or macOS support. All examples, tools, and troubleshooting steps are tailored to Windows environments, including reliance on NTFS, Windows Update, .NET Framework, PowerShell cmdlets, and Windows-specific utilities like Robocopy. There are no Linux or macOS equivalents, examples, or guidance, and the documentation does not address cross-platform scenarios.
Recommendations
- Clearly state in the introduction and requirements that Azure File Sync is Windows-only, and explain the rationale.
- If any Linux or macOS support is planned or available (e.g., via SMB/NFS clients), provide explicit documentation and examples.
- Offer guidance for organizations with mixed environments, such as alternative Azure Files sync solutions for Linux/macOS.
- Include a comparison table of Azure Files sync options for different OS platforms.
- If possible, document any interoperability patterns (e.g., using Azure Files directly from Linux) and link to relevant resources.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on Windows Server, with Azure File Sync described as an extension for Windows Server only. All performance and scale targets are discussed in the context of Windows Server, and there is no mention of Linux or macOS support, examples, or equivalent tooling.
Recommendations
- Explicitly state platform support (e.g., clarify if Azure File Sync is Windows-only or provide Linux/macOS alternatives if available).
- If Linux/macOS support is possible, add equivalent instructions, examples, and performance guidance for those platforms.
- If Azure File Sync is Windows-exclusive, provide links or references to Azure Files usage patterns for Linux/macOS users.
- Consider including a comparison table or section outlining platform differences and guidance for non-Windows environments.
Storage
Deprovision your Azure File Sync server endpoint
.../storage/file-sync/file-sync-server-endpoint-delete.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows environments. All instructions reference Windows-only tools (Task Scheduler, Event Viewer), PowerShell cmdlets/scripts, and file paths. There are no examples or guidance for Linux or macOS users, nor any mention of cross-platform alternatives. The documentation assumes the use of Windows Server for Azure File Sync, making it difficult or impossible for Linux/macOS users to follow the procedures.
Recommendations
- Clearly state platform requirements and limitations at the beginning of the documentation.
- If Azure File Sync is Windows-only, explicitly mention this and provide links to alternative solutions for Linux/macOS users.
- Where possible, offer parity by including CLI or REST API alternatives for steps currently requiring Windows GUI tools or PowerShell.
- Add a section addressing Linux/macOS scenarios, even if only to clarify that Azure File Sync does not support these platforms.
- If any steps can be performed via Azure Portal, Azure CLI, or REST API, provide those instructions alongside Windows-specific ones.
Storage
Replace a drive on an Azure File Sync server
.../articles/storage/file-sync/file-sync-replace-drive.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows environments. All examples use Robocopy, a Windows-only tool, and instructions reference Windows-specific services and concepts (e.g., Storage Sync Agent Service, drive letters). There are no Linux or macOS equivalents, nor any mention of how to perform these tasks on non-Windows platforms. The steps and tooling assume the administrator is using Windows Server, with no guidance for Linux-based Azure File Sync scenarios.
Recommendations
- Add equivalent instructions and examples for Linux environments, including recommended tools (e.g., rsync, cp, smbclient) for data transfer.
- Clarify whether Azure File Sync supports Linux servers, and if so, provide parity in documentation for Linux/macOS users.
- If Azure File Sync is Windows-only, explicitly state this limitation at the beginning of the article.
- Where possible, use cross-platform terminology and avoid Windows-specific concepts (e.g., drive letters, Windows services) or provide Linux/macOS alternatives.
- Include notes on how to manage SMB shares and sync services on Linux.
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
Windows First
Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All migration instructions assume the use of Windows Server, Windows VMs, and Windows-native tools such as Robocopy and PowerShell cmdlets. There are no examples or guidance for performing migrations from Linux or macOS systems, nor are cross-platform alternatives to Robocopy or PowerShell mentioned. The documentation also references Windows-specific services like Storage Migration Service without Linux equivalents.
Recommendations
- Provide equivalent migration instructions for Linux environments, including supported tools (e.g., rsync, azcopy, or SMB mounting via Linux).
- Include Linux/macOS command-line examples for file migration and Azure File Sync agent installation, where supported.
- Mention cross-platform tools and clarify any Windows-only requirements, especially for Azure File Sync agent support.
- Add a section outlining limitations or requirements for non-Windows users, and suggest alternatives or workarounds.
- Present examples for both Windows and Linux/macOS side-by-side, or clearly indicate when instructions are Windows-specific.
Storage
Migrate Files Between SMB Azure file shares
...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 is heavily biased toward Windows, exclusively recommending Robocopy (a Windows-only tool) for file migration. All instructions assume a Windows VM, with no mention of Linux/macOS alternatives or cross-platform tools. There are no Linux examples, and Windows tooling is presented as the default and only option.
Recommendations
- Add instructions for migrating files using Linux/macOS tools such as rsync or smbclient.
- Include examples for mounting Azure SMB shares on Linux and macOS.
- Provide guidance on selecting appropriate VM types for Linux-based migrations.
- Reference cross-platform tools like AzCopy more prominently, with step-by-step examples.
- Reorder or parallelize examples so Linux/macOS options are shown alongside Windows.
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, with all examples, tooling, and instructions referencing Windows Server, Windows DNS, and PowerShell. There are no Linux/macOS equivalents or guidance, and the use of DFS Namespaces is described exclusively as a Windows Server feature. All step-by-step instructions and screenshots are for Windows tools, and PowerShell is the only CLI shown. No mention is made of how Linux/macOS users might interact with DFS-N or Azure Files in this context.
Recommendations
- Clarify early in the documentation that DFS Namespaces is a Windows Server-only feature, and explicitly state platform limitations.
- If possible, provide guidance or alternatives for Linux/macOS environments, such as how to access Azure Files SMB shares directly from non-Windows clients, or mention NFS support where relevant.
- Include examples or references for mounting Azure Files SMB shares from Linux/macOS, and discuss any limitations or differences in namespace management.
- Add a section comparing DFS-N with cross-platform alternatives (if any), or link to documentation for Linux/macOS file share management.
- Reorder or balance examples so that Linux/macOS usage is addressed where feasible, or clarify why it is not.
Storage
Update Password for an AD DS Storage Account Identity
.../files/storage-files-identity-ad-ds-update-password.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows environments, providing only PowerShell-based instructions and relying exclusively on Windows tools (AzFilesHybrid module, Active Directory PowerShell). There are no examples or guidance for Linux or macOS users, and all steps assume access to Windows PowerShell and Windows AD tooling.
Recommendations
- Provide equivalent instructions for Linux/macOS environments, if possible (e.g., using cross-platform Azure CLI, REST API, or LDAP tools).
- Explicitly state if the operation is only supported on Windows, and suggest alternatives or workarounds for non-Windows users.
- If PowerShell Core (cross-platform) can be used, clarify compatibility and provide examples.
- Mention and, if possible, demonstrate how to interact with AD DS from Linux (e.g., using Samba tools or LDAP utilities) for password rotation.
- Reorder or parallelize instructions so that Windows and Linux/macOS approaches are presented equally, or clarify up front that only Windows is supported.
Storage
Configure Directory and File Level Permissions for Azure Files
...torage-files-identity-configure-file-level-permissions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All configuration steps, examples, and tools (icacls, Windows File Explorer, PowerShell modules, net use) are Windows-specific. There are no Linux/macOS examples or guidance for mounting or managing ACLs, and the documentation assumes the use of Windows ACLs (NTFS), which are not natively supported on Linux. Linux is only mentioned in a final link, with no actionable steps or parity in the main content.
Recommendations
- Add explicit guidance for Linux/macOS users, including whether and how they can manage or view ACLs on Azure Files.
- If NTFS ACL management is not supported from Linux/macOS, clearly state this limitation early in the documentation.
- Provide alternative workflows or tools (if any) for Linux/macOS environments, or link to relevant documentation.
- Include Linux/macOS mounting instructions and clarify what level of access control is possible from those platforms.
- Consider restructuring the document so that platform-specific instructions are clearly separated and Linux/macOS parity (or lack thereof) is transparent.
Storage
Enable AD DS Authentication for Azure Files
...s/storage/files/storage-files-identity-ad-ds-enable.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments, with all examples and instructions using Windows PowerShell (specifically PowerShell 5.1), Windows AD tools, and Windows command-line utilities (e.g., Setspn). There are no Linux or macOS equivalents provided, nor is there any mention of how to perform these steps from non-Windows systems. The prerequisites and troubleshooting steps also assume a Windows environment.
Recommendations
- Provide equivalent instructions for Linux/macOS environments, if possible (e.g., using Samba tools, ldap utilities, or Azure CLI where applicable).
- Clarify whether any steps can be performed from Azure Cloud Shell or cross-platform PowerShell (7.x), and document limitations.
- Explicitly state Windows-only requirements at the top, and offer alternative workflows for non-Windows users (even if limited).
- Include notes on how Linux-based clients can access Azure file shares once AD DS authentication is enabled, and any additional configuration needed.
- If Windows-only is unavoidable, explain why (e.g., AD DS integration requires Windows tools) and suggest workarounds or alternatives for Linux environments.
Storage
Use Microsoft Entra Domain Services with Azure Files
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-auth-domain-services-enable.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Windows terminology, tools, and examples (especially PowerShell and Windows Server AD cmdlets) are presented first and in detail. Linux is mentioned only briefly, with no Linux-specific command examples or guidance for key steps such as configuring Kerberos encryption. Critical configuration steps (e.g., setting AES-256 encryption) rely exclusively on Windows PowerShell and Windows Server AD tools, with no Linux alternatives or parity.
Recommendations
- Provide Linux-specific instructions and examples for all major steps, especially for configuring Kerberos encryption and managing domain objects.
- Include guidance for using Linux tools (such as ldapmodify, kinit, or realm) to perform equivalent operations to Windows PowerShell cmdlets.
- Present both Windows and Linux examples side-by-side, or clearly indicate platform-specific procedures.
- Clarify any platform limitations and offer workarounds or references for Linux/macOS users.
- Ensure that prerequisites and workflow sections explicitly address Linux/macOS environments, not just Windows.
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
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily oriented toward Windows environments and tooling. All client-side configuration steps, prerequisites, and examples are Windows-specific, referencing Windows services, registry keys, Group Policy, Intune, and PowerShell. There are no instructions or examples for Linux or macOS clients, nor any mention of their support or limitations. Windows tools and patterns (e.g., File Explorer, icacls, ksetup, PowerShell cmdlets) are used exclusively, and Windows operating systems are listed as the only supported platforms for client access.
Recommendations
- Explicitly state whether Linux/macOS clients are supported for Microsoft Entra Kerberos authentication with Azure Files. If not supported, clarify this early in the documentation.
- If Linux/macOS support is possible, provide equivalent configuration instructions for those platforms, including Kerberos setup, mounting SMB shares, and troubleshooting.
- Include examples using Linux tools (e.g., smbclient, mount.cifs, kinit) and describe any required Kerberos configuration steps for non-Windows clients.
- Add a section detailing limitations or differences for Linux/macOS users, including any unsupported features or workarounds.
- Reorder or balance examples so that Windows and Linux/macOS instructions are presented with equal prominence where applicable.
Storage
Use Azure Files with Multiple Active Directory (AD) Forests
...orage/files/storage-files-identity-multiple-forests.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with all examples and instructions using Windows tools (Active Directory Domains and Trusts console, DNS Manager, File Explorer, icacls, setspn, klist, net use, PowerShell). There are no Linux or macOS equivalents or guidance for performing these tasks on non-Windows platforms. This creates friction for administrators who manage hybrid or Linux-based environments.
Recommendations
- Add instructions and examples for performing key tasks (such as mounting SMB shares, managing Kerberos tickets, and configuring AD trusts) on Linux using Samba, Kerberos utilities (e.g., kinit, klist), and relevant Linux tools.
- Provide parity for directory/file-level permission management using Linux commands (e.g., setfacl, getfacl) and explain how to interact with Azure Files from Linux clients.
- Include notes or sections clarifying which steps are Windows-only and offer alternatives or references for Linux/macOS environments.
- Where PowerShell is used (e.g., for ADSync), mention if/when there are CLI or cross-platform alternatives.
- Reorder examples so that platform-neutral or Linux/macOS instructions are presented alongside or before Windows-specific instructions when possible.
Storage
Linux migration to Azure File Sync
.../storage/files/storage-files-migration-linux-hybrid.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation is heavily biased toward Windows, both in its technical requirements and in the migration process. All migration steps assume the use of Windows Server as the target, with Robocopy (a Windows tool) as the primary copy utility. Linux tools and workflows are only briefly mentioned as alternatives, with no concrete examples or guidance. There are no Linux command examples, and the documentation assumes the reader will provision and operate Windows infrastructure, even for tasks that could be performed from Linux.
Recommendations
- Provide concrete Linux-based migration examples, such as using rsync or scp, for scenarios where a direct Linux-to-Azure migration is possible or for the initial copy to Windows.
- Include side-by-side command examples for both Windows (Robocopy) and Linux (rsync, cp, etc.), especially in the migration and copy phases.
- Clarify in the introduction that Azure File Sync does not support Linux as a sync endpoint, but offer alternative migration paths for Linux-only environments.
- Offer guidance or references for Linux administrators unfamiliar with Windows tools like Robocopy, including how to install and use them if necessary.
- Highlight any limitations or considerations for Linux file attributes, permissions, and ACLs when migrating to Windows, and provide mapping strategies.
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
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All migration steps require a Windows Server instance, and all examples use Windows-native tools (Robocopy, Event Viewer). There are no Linux or macOS equivalents, nor any mention of how users on those platforms could participate in the migration process. The workflow assumes Windows as the only viable platform for Azure File Sync, and troubleshooting steps are Windows-specific.
Recommendations
- Explicitly state Azure File Sync is Windows-only and provide alternative migration paths for Linux/macOS users.
- Offer guidance for Linux NAS administrators, such as using rsync or other cross-platform tools for initial data transfer.
- Include documentation or links for migrating NFS shares or integrating with Linux-based file servers, even if only for the Data Box ingestion phase.
- Provide parity in troubleshooting steps for non-Windows environments, or clarify limitations.
- List third-party or Azure-native alternatives for hybrid cloud file sync for Linux/macOS.
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
Windows First
Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. It exclusively discusses RoboCopy, a Windows-only tool, and all examples and instructions assume the use of Windows Server and Windows-specific features (e.g., mounting SMB shares on Windows, using Windows QoS for throttling, running commands in PowerShell or elevated Windows consoles). Although Linux is mentioned as a possible source, there are no Linux migration examples, nor are Linux-native tools or workflows described. This creates friction for Linux/macOS users who cannot use RoboCopy and lack guidance for equivalent migration tasks.
Recommendations
- Add equivalent migration instructions for Linux/macOS environments, such as using rsync, smbclient, or mount.cifs for SMB shares.
- Provide Linux/macOS command-line examples for copying files to Azure file shares over SMB.
- Discuss Linux-specific considerations for mounting Azure file shares and handling file permissions.
- Include a section comparing RoboCopy with Linux-native tools, outlining pros/cons and feature parity.
- Clarify in the introduction that RoboCopy is Windows-only and suggest alternatives for non-Windows users.
Storage
Configure DNS forwarding for Azure Files
...articles/storage/files/storage-files-networking-dns.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All code examples use PowerShell and Windows DNS Server cmdlets, with no mention of Linux or cross-platform alternatives. The prerequisites specifically call out the Azure PowerShell module, and all DNS configuration steps reference Windows Server environments and tools. There are no instructions or examples for configuring DNS forwarding using Linux-based DNS servers (e.g., BIND, dnsmasq), nor are Linux command-line tools (like dig or systemd-resolve) mentioned for testing DNS resolution.
Recommendations
- Add equivalent instructions and examples for configuring DNS forwarding using common Linux DNS servers (e.g., BIND, Unbound, dnsmasq), including configuration file snippets.
- Include Linux/macOS command-line tools (e.g., dig, host, systemd-resolve) for testing DNS resolution and clearing DNS cache.
- Clarify that the process is OS-agnostic and provide links or references to official documentation for Linux DNS server configuration.
- Rephrase prerequisites to mention that PowerShell is only required for Windows environments, and suggest alternatives for Linux/macOS users.
- Ensure that examples are presented for both Windows and Linux environments, or at least indicate the steps for Linux users.
Storage
Migrate data into Azure File Sync with Azure Data Box
...files/storage-files-migration-server-hybrid-databox.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is strongly oriented toward Windows Server environments, with all migration steps, examples, and tooling (e.g., Robocopy) focused exclusively on Windows. There are no Linux/macOS examples, nor are alternative tools or workflows for non-Windows platforms mentioned. The migration path assumes Azure File Sync will be installed on Windows Server, and the only file copy tool recommended is Robocopy, which is Windows-specific.
Recommendations
- Add explicit notes clarifying that Azure File Sync is Windows Server-only, and provide links to alternative migration guides for Linux/NAS/macOS sources.
- Include equivalent Linux/macOS migration scenarios in the overview and cross-link them from this page.
- Where file copy operations are described, mention Linux/macOS alternatives (e.g., rsync, cp, scp) and provide example commands for those platforms.
- Clarify in the introduction and migration phases that this guide is not applicable for non-Windows sources, and direct users to relevant documentation.
- Consider a dedicated section comparing Windows and Linux migration approaches, highlighting differences and available tooling.
Storage
Use Azure Files for Virtual Desktop Workloads
...in/articles/storage/files/virtual-desktop-workloads.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on Windows-based virtual desktop scenarios, referencing FSLogix, roaming user profiles, folder redirection, and Windows-specific technologies (e.g., VHD/VHDX, Entra ID, AD DS). There are no examples, guidance, or mentions of Linux or macOS virtual desktop workloads, nor any cross-platform SMB usage patterns. All examples and recommendations assume Windows environments and tools.
Recommendations
- Add explicit guidance for Linux and macOS session hosts, including SMB mounting instructions and authentication patterns.
- Include examples of mounting Azure Files shares from Linux (e.g., using mount.cifs) and macOS.
- Discuss limitations, performance, and scale considerations for non-Windows clients.
- Clarify whether FSLogix or App Attach scenarios are supported or relevant for Linux/macOS, and provide alternatives if not.
- Add a section comparing Windows and Linux/macOS support for Azure Files in VDI scenarios.
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
Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. All deployment and configuration steps assume a Windows file server, with no mention of Linux or macOS alternatives. Integration points (e.g., Volume Shadow Copy Service, Windows Explorer, DFSR) and Tiger Bridge Shell Extension are Windows-specific, and there are no examples or guidance for Linux users. This creates significant friction for non-Windows users and may prevent them from completing the deployment.
Recommendations
- Explicitly state platform requirements and limitations at the beginning of the guide.
- If Tiger Bridge supports Linux or macOS, add equivalent deployment, configuration, and restore instructions for those platforms.
- Provide examples using Linux tools (e.g., CLI, file managers) and mention any supported Linux features.
- If Tiger Bridge is Windows-only, clarify this early and suggest alternative solutions for Linux environments.
- Avoid referencing Windows tools (e.g., Windows Explorer, DFSR) without mentioning Linux/macOS equivalents or alternatives.
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 strongly Windows-centric, with Tiger Bridge described as 'fully integrated with NTFS, or ReFS file systems on windows platform.' All deployment instructions require a Windows file server, and installation steps reference Windows-specific features (Windows Explorer shell extension, NTFS/ReFS). There are no Linux/macOS deployment examples, and no mention of Linux-native installation or management workflows. While SMB/NFS sources are mentioned, the guide does not provide parity for Linux server deployment or usage. All screenshots and configuration steps are Windows-based.
Recommendations
- Add explicit instructions and examples for deploying Tiger Bridge on Linux servers, if supported.
- Include Linux/macOS equivalents for installation, configuration, and management steps (e.g., CLI usage, file system integration).
- Provide screenshots or terminal examples for Linux environments.
- Clarify Tiger Bridge's support matrix for Linux and macOS, including any limitations.
- If Tiger Bridge is Windows-only, state this clearly at the beginning and suggest alternative solutions for Linux users.