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 176-200 of 1657 flagged pages
Storage
GlusterFS to Azure Files Migration Guide
...in/articles/storage/files/glusterfs-migration-guide.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 areas: Windows requirements and tools (Robocopy, PowerShell) are consistently presented before Linux equivalents, and Windows-specific instructions are more detailed. Windows tools (Robocopy) are highlighted as the recommended migration method, while Linux alternatives (rsync, fpsync) are mentioned but with less emphasis and detail. PowerShell/Windows command examples are more prominent, and troubleshooting for Windows is more extensive. Some Linux-specific migration scenarios (e.g., using fpsync for large datasets) are referenced but not elaborated. The documentation could better balance the coverage and detail for Linux users.
Recommendations
- Present Linux and Windows instructions in parallel, or alternate which platform is shown first in each section.
- Provide equally detailed examples and explanations for Linux migration tools (e.g., fpsync, rsync) as for Robocopy.
- Include troubleshooting steps for Linux migration tools (e.g., fpsync) and common Linux errors.
- Expand on Linux-specific scenarios, such as mounting NFS shares, optimizing rsync/fpsync for large datasets, and handling Linux file permissions.
- Add links to Linux documentation and community resources with the same prominence as Windows resources.
- Ensure that recommendations and best practices are given for both platforms, not just Windows (e.g., performance optimization, security).
Create Pull Request
Storage
Migrate to SMB Azure file shares using Azure Storage Mover
.../articles/storage/files/migrate-files-storage-mover.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools (Robocopy), mentioning Windows Server as a source before Linux, and omitting Linux-specific migration tool examples. The migration agent deployment instructions focus on Hyper-V and VMware (common in Windows environments) and do not provide parity for Linux-based hypervisors or native Linux instructions. There are no Linux command-line examples or guidance for Linux administrators.
Recommendations
- Include explicit Linux migration examples, such as using Linux SMB shares as sources and steps for Linux administrators.
- Mention Linux-based hypervisors (e.g., KVM, Proxmox) as supported platforms for the Storage Mover agent, if applicable.
- Provide Linux-specific instructions for agent registration, including SSH commands and environment setup.
- Reference Linux migration tools (e.g., rsync, smbclient) alongside Robocopy, and clarify their roles and limitations.
- Ensure examples and guidance are presented in a cross-platform manner, not prioritizing Windows tools or environments.
Storage
Configure root squash settings for NFS Azure file shares
...cs/blob/main/articles/storage/files/nfs-root-squash.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 Azure PowerShell examples before Azure CLI, with no Linux-native tooling (such as Bash scripts or Linux shell commands) shown for configuring root squash. The use of PowerShell commands and terminology is prominent, and there are no examples or guidance for Linux administrators using native Linux tools or workflows. The Azure portal instructions are platform-neutral, but the command-line sections favor Windows-centric tools and patterns.
Recommendations
- Add Linux-native examples using Bash or shell scripts for configuring root squash, especially for common Linux admin workflows.
- Include instructions for using Linux tools (e.g., curl, jq, REST API calls) to configure root squash, not just Azure CLI and PowerShell.
- Present Azure CLI examples before PowerShell, as CLI is more commonly used on Linux systems.
- Explicitly mention Linux prerequisites and environment setup for Azure CLI usage.
- Clarify that Azure CLI can be used cross-platform, and provide sample commands run from a Linux shell.
- Consider adding troubleshooting or verification steps using Linux commands (e.g., show how to verify root squash from a Linux NFS client).
Storage
Improve SMB Azure File Share Performance
...cs/blob/main/articles/storage/files/smb-performance.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows configuration and verification steps for SMB Multichannel are presented in detail, including PowerShell commands and references to Windows tools (robocopy, diskspd.exe), while Linux configuration is covered but lacks equivalent verification or performance testing examples. Feature registration instructions are only provided for Azure PowerShell and the Azure portal, with no mention of CLI or Linux-native alternatives. References to Windows documentation are more frequent and prominent than Linux equivalents.
Recommendations
- Add Linux-specific verification steps for SMB Multichannel (e.g., using smbstatus, dmesg, or CIFS utils to confirm multichannel connections).
- Provide Linux-native performance testing examples (e.g., using fio or iozone) alongside Windows tools like diskspd.exe.
- Include Azure CLI instructions for feature registration to improve parity for Linux users.
- Reference official Linux SMB documentation or guides in addition to Windows documentation.
- Ensure that examples and instructions are presented in a cross-platform order, or grouped by OS, rather than Windows-first.
- Where PowerShell is used, offer Bash or shell script equivalents for common administrative tasks.
Storage
Overview - Azure Files Authorization and Access Control
.../storage/files/storage-files-authorization-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows ACLs, Windows identity sources, and Windows-specific tools (e.g., robocopy) for managing Azure Files authorization and access control. There are no examples or mentions of Linux equivalents, such as POSIX ACLs, Linux authentication mechanisms, or Linux file movement tools. The documentation assumes familiarity with Windows concepts and does not provide guidance for Linux administrators.
Recommendations
- Include examples of configuring directory and file-level permissions using Linux clients, such as using SMB mounting on Linux and managing POSIX ACLs where supported.
- Mention and provide guidance for Linux file movement tools (e.g., rsync, smbclient) and how ACLs can be preserved or mapped when migrating data from Linux systems.
- Clarify whether Azure Files supports POSIX ACLs and, if not, provide recommendations or workarounds for Linux users.
- Add a section or notes addressing Linux authentication sources (e.g., LDAP, Kerberos) and how they integrate with Azure Files.
- Ensure parity in documentation by presenting both Windows and Linux procedures side-by-side where possible.
Storage
Overview - Azure Files Identity-Based Authentication
...orage/files/storage-files-active-directory-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows concepts, tools, and patterns first (e.g., AD DS, DACLs, domain-joining), and by omitting Linux-specific examples or guidance. Windows terminology and workflows are presented as the default, while Linux support is only briefly mentioned and deferred to a separate document. There are no Linux or MacOS usage examples, and Windows-centric features (such as DACLs and FSLogix) are highlighted without Linux equivalents.
Recommendations
- Add Linux and MacOS usage examples for identity-based authentication, including configuration steps and troubleshooting tips.
- Provide parity in terminology, such as referencing Linux file permissions and access control models alongside Windows DACLs.
- Include links to Linux-specific documentation directly in relevant sections, not just as a parenthetical note.
- Mention Linux-compatible tools and authentication patterns (e.g., Samba, sssd, Kerberos client configuration) where appropriate.
- Ensure diagrams and workflows illustrate both Windows and Linux client scenarios.
- Avoid presenting Windows workflows and terminology as the default; clarify cross-platform applicability throughout.
Storage
Configure a Site-to-Site VPN for Azure Files
...icles/storage/files/storage-files-configure-s2s-vpn.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. It explicitly recommends Windows Server's RRAS as a default option for on-premises VPN appliances, mentioning it before any Linux alternatives. The only specific appliance configuration guidance links to Windows Server documentation, with no mention of Linux-based VPN solutions (such as strongSwan, Openswan, or Libreswan). Throughout the page, PowerShell examples are provided in full parity with Azure CLI, but the narrative and troubleshooting steps often reference PowerShell cmdlets first. The mounting instructions do link out to Linux and macOS guides, but the core VPN appliance configuration is Windows-centric.
Recommendations
- Explicitly mention common Linux VPN appliances (e.g., strongSwan, Openswan, Libreswan) as alternatives to Windows RRAS in the prerequisites and configuration sections.
- Provide links to Azure's tested Linux VPN device documentation, or include example configuration steps for a popular Linux VPN appliance.
- When referencing how to obtain the public IP address of the VPN gateway, include Azure CLI examples alongside PowerShell.
- Ensure that troubleshooting and verification steps are presented with both PowerShell and Azure CLI commands, and avoid defaulting to Windows tools.
- Consider adding a short section or note on cross-platform considerations for on-premises VPN appliances, highlighting both Windows and Linux options.
Storage
Azure Files frequently asked questions (FAQ)
.../blob/main/articles/storage/files/storage-files-faq.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. Most examples, troubleshooting steps, and tool references are Windows-centric, with frequent mentions of PowerShell, Windows File Explorer, Windows registry edits, and Windows-specific attributes (NTFS ACLs, offline attribute, etc.). Instructions and examples for Linux (and macOS) are largely absent, even in sections where cross-platform usage is implied. Windows tools and patterns are mentioned exclusively or before Linux equivalents, and Linux-specific guidance is minimal or missing.
Recommendations
- Add equivalent Linux and macOS examples for all PowerShell and Windows command-line instructions (e.g., show how to check/remove alternate data streams, recall tiered files, manage ACLs, etc. on Linux).
- Include Linux-specific troubleshooting steps and tool references (e.g., how to manage tiered files, handle file attributes, audit access, and resolve conflicts on Linux).
- Provide parity in documentation for mounting, syncing, and managing Azure Files on Linux, including examples using native Linux tools (e.g., mount, rsync, setfacl, getfacl, etc.).
- Explicitly mention Linux/macOS alternatives when referencing Windows-only features or behaviors (e.g., clarify how thumbnail previews, file attributes, and ACLs are handled on Linux).
- Reorder sections or examples to present cross-platform instructions together, rather than defaulting to Windows-first.
- Where Windows registry or File Explorer is referenced, provide Linux/macOS equivalents or note platform limitations.
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
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows environments. All examples and instructions use Windows PowerShell, Windows-specific modules (Active Directory PowerShell), and Windows command-line tools (Setspn). There are no Linux or cross-platform alternatives provided for any step, and the prerequisites and troubleshooting sections assume a Windows domain-joined machine. The documentation also refers to Windows patterns and tools before mentioning any alternatives (which are not present), and there is no guidance for Linux clients or administrators.
Recommendations
- Provide equivalent instructions and examples for Linux environments, such as using Samba and Kerberos tools for domain joining and authentication.
- Include cross-platform PowerShell (PowerShell Core) or CLI alternatives where possible, and clarify which steps are Windows-only.
- Document how Linux clients can access Azure Files with AD DS authentication, including required configuration and troubleshooting.
- Mention and link to any Azure CLI, REST API, or other platform-agnostic methods for configuring AD DS authentication.
- Add a section on supported scenarios for non-Windows environments, including limitations and workarounds.
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 exclusively provides instructions and examples using Windows-centric tools and PowerShell cmdlets (AzFilesHybrid, Active Directory PowerShell). There are no Linux or cross-platform alternatives mentioned, and all procedures assume a Windows environment. The guidance is structured around Windows-first workflows, with no parity for Linux administrators.
Recommendations
- Provide equivalent instructions for Linux environments, such as using LDAP tools (ldapmodify, ldappasswd) or Samba utilities to update AD DS passwords.
- Include examples using cross-platform scripting languages (e.g., Python with ldap3) for password rotation.
- Clarify any platform requirements and, where possible, offer alternatives for non-Windows clients.
- Add a section explicitly addressing Linux/macOS administrators, outlining supported methods and any limitations.
- Reference Azure CLI or REST API options if available, as these are generally cross-platform.
Storage
Assign Share-Level Permissions for Azure Files
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-assign-share-level-permissions.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a Windows-centric bias in several ways: it repeatedly references Windows ACLs as the method for granular file/directory access control, analogizes Azure RBAC roles to Windows File Server ACLs, and recommends using Windows ACLs for enforcement. The migration tool highlighted is a PowerShell cmdlet designed for Windows environments, with no mention of Linux alternatives. All examples for assigning permissions use Azure Portal, PowerShell, and CLI, but there is no guidance or examples for Linux-specific tools, workflows, or integration with Linux identity systems (e.g., LDAP, NFS, POSIX ACLs). The documentation does not address how Linux clients interact with Azure Files in the context of share-level permissions, nor does it mention Linux file permission models.
Recommendations
- Add explicit guidance and examples for Linux clients, including how share-level permissions interact with Linux SMB clients and how to manage file-level permissions from Linux.
- Discuss Linux file permission models (e.g., POSIX ACLs) and clarify their compatibility or limitations with Azure Files.
- Provide migration strategies and tooling for organizations moving from Linux-based file servers (e.g., Samba/NFS) to Azure Files.
- Include Linux command-line examples (e.g., using smbclient, mount.cifs, or Azure CLI from Linux) for assigning and verifying permissions.
- Clarify any differences in authentication and authorization flows for Linux users/groups, especially in hybrid environments.
- Reference or link to documentation about Linux support for Azure Files, including troubleshooting and best practices.
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 First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All examples, instructions, and tooling references are Windows-centric, including exclusive use of Windows tools (Active Directory Domains and Trusts console, DNS Manager, File Explorer, icacls, setspn, net use, klist), and PowerShell commands. There are no Linux or cross-platform alternatives provided for mounting shares, managing AD trusts, configuring DNS, or validating Kerberos tickets. The instructions assume Windows environments and do not mention Linux clients or Samba integration, despite Azure Files supporting SMB access from Linux.
Recommendations
- Add Linux-specific instructions for mounting SMB Azure file shares (e.g., using mount.cifs or smbclient), including Kerberos authentication setup.
- Provide guidance for managing AD trusts and DNS from Linux (e.g., using Samba tools, realmd, or command-line utilities).
- Include examples of configuring file-level permissions using Linux ACLs (setfacl) and explain interoperability with Windows ACLs.
- Document how to validate Kerberos tickets and troubleshoot authentication on Linux (e.g., using klist, kvno, and other MIT/Heimdal Kerberos tools).
- Clarify any limitations or requirements for Linux clients in multi-forest AD scenarios with Azure Files.
- Where PowerShell is used, offer Bash or shell equivalents for Linux environments.
- Explicitly state platform requirements and parity, and link to cross-platform documentation where available.
Storage
On-Premises AD DS Authentication for Azure Files
...storage/files/storage-files-identity-ad-ds-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by prioritizing Windows terminology, tools, and examples. Windows OS versions and domain join instructions are mentioned first and in more detail, while Linux is referenced only briefly and generically. Windows-specific tools (e.g., ACLs, DACLs) and troubleshooting links are provided, but there are no equivalent Linux examples or guidance for mounting shares, configuring permissions, or troubleshooting. The documentation assumes familiarity with Windows environments and omits Linux-specific steps and best practices.
Recommendations
- Provide explicit Linux examples for mounting Azure file shares using AD DS authentication, including sample commands for popular distributions (e.g., Ubuntu, RHEL).
- Include instructions for configuring file and directory permissions on Linux clients, referencing Linux ACLs and tools (e.g., setfacl, getfacl).
- Add troubleshooting guidance for Linux mounting errors and authentication issues, similar to the Windows troubleshooting link.
- Balance the order of presentation so that Linux is mentioned alongside Windows, rather than as an afterthought.
- Clarify any limitations or differences in AD DS authentication support between Windows and Linux clients.
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 demonstrates a Windows bias by prioritizing Windows VM scenarios, providing detailed PowerShell and Windows Server Active Directory cmdlet instructions, and referencing Windows tools and patterns (e.g., PowerShell 5.1, klist). Linux VM support is mentioned but not exemplified, and no Linux-specific commands or workflows are provided for key steps such as domain joining, enabling features, or configuring Kerberos encryption.
Recommendations
- Add explicit Linux VM examples for domain joining, including references to supported distributions and step-by-step instructions.
- Provide Linux CLI commands (e.g., using kinit, smbclient, or mount.cifs) for accessing Azure file shares with Microsoft Entra credentials.
- Include instructions for configuring Kerberos encryption on Linux, such as editing krb5.conf and using relevant Linux tools.
- Reference Linux equivalents for tools like klist and explain how to purge Kerberos tickets and remount shares on Linux.
- Ensure parity in troubleshooting and validation steps for both Windows and Linux environments.
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 page exhibits a strong Windows bias. All client-side configuration instructions, prerequisites, and examples are exclusively for Windows operating systems and tools (Group Policy, Intune, registry, PowerShell, Windows File Explorer, icacls, ksetup). There are no examples, instructions, or mentions of Linux or macOS clients, nor any cross-platform tools or patterns. The documentation assumes the use of Windows environments for both hybrid and cloud-only scenarios, and omits guidance for non-Windows platforms.
Recommendations
- Add explicit statements about support or lack thereof for Linux/macOS clients, including any limitations.
- If supported, provide Linux/macOS equivalents for mounting Azure Files with Microsoft Entra Kerberos authentication, including required packages (e.g., cifs-utils, krb5-user), configuration steps, and troubleshooting.
- Include examples of configuring Kerberos and SMB mounts on Linux, such as editing /etc/krb5.conf, using kinit, and mounting with mount.cifs.
- Document any differences in permissions management (e.g., POSIX ACLs vs. NTFS ACLs) and how to manage them on non-Windows platforms.
- Clarify whether features like directory/file-level permissions and Kerberos ticket retrieval are available or planned for non-Windows clients.
- If Linux/macOS are not supported, state this clearly and provide guidance or alternatives for cross-platform environments.
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 biased toward Windows environments. All prerequisites, examples, and configuration steps assume Windows clients and administrators. PowerShell is the only scripting environment referenced, and Windows-specific tools (such as File Explorer, Active Directory PowerShell cmdlets, Group Policy) are used exclusively. There are no examples or guidance for Linux clients, nor mention of Linux equivalents for key steps such as Kerberos configuration, file permissions, or domain integration.
Recommendations
- Add explicit guidance and examples for Linux clients, including supported distributions and Kerberos configuration steps.
- Provide Linux command-line equivalents for all PowerShell commands, using tools like kinit, smbclient, and relevant Linux Kerberos utilities.
- Clarify whether and how Linux clients can participate in the cloud trust scenario, including prerequisites and limitations.
- Include instructions for configuring directory and file-level permissions from Linux (e.g., using setfacl or smbclient), and explain how NTFS ACLs map to POSIX permissions.
- Mention any required packages or configuration changes for Linux systems to support Microsoft Entra Kerberos authentication over SMB.
- Present examples for both Windows and Linux side-by-side, or clearly indicate platform-specific instructions.
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
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All examples and instructions for configuring directory and file-level permissions for Azure Files are exclusively focused on Windows tools and workflows, such as Windows ACLs (NTFS), icacls, Windows File Explorer, and PowerShell. There are no examples or guidance for Linux clients, nor any mention of Linux-compatible ACL management tools or patterns. The documentation assumes the use of Windows authentication models and omits Linux-specific considerations for mounting or managing permissions.
Recommendations
- Add explicit guidance and examples for configuring file and directory permissions from Linux clients, including supported ACL models and tools (e.g., setfacl, getfacl).
- Clarify whether Linux SMB clients can manage or honor Windows ACLs, and document any limitations or requirements.
- Provide Linux command-line examples for mounting Azure Files shares and managing permissions, alongside Windows examples.
- Discuss cross-platform interoperability for ACLs, including how permissions set on Windows are interpreted on Linux and vice versa.
- Include troubleshooting tips for Linux users encountering permission issues with Azure Files.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (PowerShell, Azure File Sync) and patterns before their Linux equivalents. Windows-centric features (such as Azure File Sync and AD DS integration) are highlighted, and scripting/tooling examples mention PowerShell before Azure CLI. While Linux is acknowledged, Windows tools and scenarios are presented first or more prominently.
Recommendations
- Present Linux and Windows examples side-by-side or in parallel, rather than listing Windows first.
- Include Linux-specific tooling and scripting examples (e.g., Bash scripts, Linux mount commands) alongside PowerShell.
- Highlight Linux equivalents for features like Azure File Sync or clarify if alternatives exist.
- Expand discussion of NFS and Linux authentication/integration scenarios to match the detail given for Windows/AD DS.
- Ensure links to Linux usage guides are as prominent as those for Windows.
- Mention cross-platform tools (e.g., Azure CLI, Storage Explorer) before platform-specific ones.
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 oriented toward Windows environments. It assumes migration targets are Windows Server, exclusively describes Windows Server setup and requirements, and uses Windows-specific tools (Robocopy, Event Viewer) for migration and monitoring. There are no Linux or cross-platform examples, and Linux tools or workflows are not mentioned. The migration workflow is designed around Windows Server and Azure File Sync, with no guidance for Linux-based alternatives.
Recommendations
- Add guidance for migrating NAS data directly to Azure Files from Linux systems, including supported tools (e.g., rsync, azcopy, SMB/NFS mounts).
- Provide Linux-based examples for copying data to Data Box and Azure File Shares, including command-line instructions.
- Clarify whether Azure File Sync or Data Box supports Linux servers as sources or targets, and document any limitations.
- Include troubleshooting steps and monitoring guidance for Linux environments (e.g., syslog, Linux file system permissions).
- Mention cross-platform tools and approaches where possible, and avoid assuming Windows Server as the only migration target.
Storage
Linux migration to Azure File Sync
.../storage/files/storage-files-migration-linux-hybrid.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily Windows-centric, focusing almost exclusively on Windows Server and Windows-native tools (notably Robocopy) for the migration process. Linux is only mentioned as the source system, with no Linux-native migration examples or detailed guidance for Linux administrators. The use of Robocopy is presented as the primary (and in practice, only) migration tool, with only a brief mention that 'Linux copy tools' could be used, but without any examples, recommendations, or parity in guidance. All configuration, troubleshooting, and operational steps are described from a Windows perspective, and there is no step-by-step Linux-side guidance or tool equivalency.
Recommendations
- Provide concrete Linux-native migration examples, such as using rsync or scp, for copying data from Linux to Windows Server.
- Include a section comparing Robocopy with Linux tools (e.g., rsync, cp, tar), outlining pros, cons, and fidelity considerations.
- Offer step-by-step instructions for Linux administrators, including how to mount Windows shares from Linux and perform the migration using Linux commands.
- Add troubleshooting tips and best practices for Linux-to-Windows migrations, including permission and ACL mapping.
- Ensure that Linux tools and approaches are mentioned before or alongside Windows tools, not only as an afterthought.
- Consider providing sample scripts or command lines for both Linux and Windows environments to achieve parity.
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 exhibits a strong Windows bias throughout the migration process. Windows Server is assumed and required for key steps, especially for running RoboCopy, which is a Windows-only tool. All file copy examples use RoboCopy, and mounting instructions are provided only for Windows. There is no mention of Linux-based alternatives for copying files, mounting shares, or handling ACLs. Linux tools and workflows are omitted or relegated to secondary references, and the guide does not provide parity for Linux administrators.
Recommendations
- Provide Linux-based migration examples using tools such as rsync, smbclient, or NFS utilities for copying files and preserving metadata.
- Include instructions for mounting Azure file shares on Linux systems, referencing both SMB and NFS where supported.
- Discuss handling of file permissions and ACLs when migrating from Linux NAS systems, including limitations and workarounds.
- Offer alternative workflows for environments where Windows Server is not available or desired, including containerized or cross-platform solutions.
- Ensure that references to VPN configuration, authentication, and networking include Linux-specific guidance and links.
- Present Windows and Linux options side-by-side in each relevant section, rather than defaulting to Windows-first approaches.
Storage
Migration Overview for SMB Azure File Shares
...cles/storage/files/storage-files-migration-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation page exhibits a Windows bias by prioritizing Windows migration tools (RoboCopy, Azure File Sync, Storage Migration Service) and providing detailed guidance and examples for Windows environments. Linux migration scenarios are mentioned but lack equivalent detail, examples, and tool coverage. Windows-specific tools and patterns are referenced first and more frequently, while Linux migration is limited to Azure Storage Mover with no practical examples or guidance. Several helper tools (TreeSize, RoboCopy) are Windows-only, and there is no mention of Linux-native file-copy tools or procedures.
Recommendations
- Add Linux-specific migration examples, such as using rsync, cifs-utils, or smbclient to copy files to Azure file shares.
- Provide step-by-step guides for Linux SMB migration, including mounting Azure file shares on Linux and preserving file fidelity.
- Include Linux-native tools in the migration tool comparison table and discuss their file fidelity capabilities.
- Balance the order of presentation so that Linux and Windows scenarios are given equal prominence.
- Reference Linux helper tools for file share analysis (e.g., du, ncdu, stat) alongside Windows tools like TreeSize.
- Clarify any limitations or differences in file fidelity when migrating from Linux SMB shares and suggest best practices.
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 heavily focused on Windows Server as the migration target and exclusively describes migration steps using Windows-based tools (RoboCopy, Azure File Sync agent, Windows Server configuration). There are no Linux or cross-platform migration examples, and the workflow assumes the use of Windows infrastructure throughout. Windows tools and patterns (RoboCopy, DFS-Namespace, Active Directory) are mentioned without Linux equivalents or alternatives. The documentation does not provide guidance for scenarios where the migration target is a Linux server or where Linux-based tools might be preferred.
Recommendations
- Add migration examples and workflows for Linux-based servers, including guidance for using Linux SMB clients and tools (e.g., rsync, smbclient, cifs-utils).
- Mention and compare Linux-compatible migration tools (such as Azure Storage Mover CLI, azcopy, or rsync) alongside RoboCopy, and provide usage examples.
- Clarify whether Azure File Sync can be used with Linux servers or provide alternative hybrid cloud solutions for Linux environments.
- Include troubleshooting steps and best practices for Linux-based NAS appliances and migration targets.
- Present both Windows and Linux options in parallel throughout the documentation, rather than assuming Windows as the default or only supported platform.
Storage
Migrate to Azure Files Using RoboCopy
...cles/storage/files/storage-files-migration-robocopy.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. It exclusively describes migration using RoboCopy, a Windows-native tool, and all examples, instructions, and troubleshooting tips assume the use of Windows Server and Windows-specific features (such as PowerShell, Windows QoS, and NTFS ACLs). Although Linux is mentioned as a possible source, there are no Linux-specific migration instructions, examples, or alternative tools provided. The mounting instructions and all operational guidance are Windows-centric, with no parity for Linux users.
Recommendations
- Provide equivalent migration instructions and examples for Linux environments, including mounting Azure file shares on Linux and using Linux-native tools (e.g., rsync, smbclient).
- Include Linux command-line examples for copying files to Azure file shares, and discuss any differences in file fidelity, permissions, and performance.
- Mention and compare Linux alternatives to RoboCopy, such as rsync or cifs-utils, and discuss their suitability for Azure file share migrations.
- Add troubleshooting and optimization tips relevant to Linux environments, including network and IOPS considerations.
- Ensure that both Windows and Linux migration routes are described, with clear guidance for each platform.
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 heavily focused on Windows Server as the source platform for migration to Azure File Sync using Azure Data Box. All examples, instructions, and tooling references assume a Windows environment, specifically Windows Server 2012 R2 or newer. Tools like Robocopy, which are native to Windows, are recommended exclusively, with no mention of Linux equivalents or migration paths from Linux servers. The documentation does not provide parity for Linux users or administrators, nor does it discuss how to migrate from Linux-based file servers.
Recommendations
- Add explicit guidance and examples for migrating data from Linux servers to Azure File Sync using Azure Data Box.
- Include Linux-native tools (e.g., rsync, cp, smbclient) for copying data to Data Box SMB shares, with sample commands.
- Clarify whether Azure File Sync supports Linux-based endpoints, and if not, provide alternative migration strategies for Linux environments.
- Present migration scenarios for both Windows and Linux sources, or clearly state the Windows-only scope at the beginning.
- If Data Box is usable from Linux, provide setup and troubleshooting steps for Linux clients, including mounting SMB shares and handling file fidelity.