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 951-975 of 1657 flagged pages
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-disaster-recovery.md
...main/articles/storage/files/files-disaster-recovery.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias. When describing how to query the Last Sync Time property, it lists Azure PowerShell before Azure CLI and client libraries, which are more cross-platform. There are no explicit Linux or macOS-specific examples or guidance, and no mention of Linux-specific tools or mounting patterns (such as using the NFS protocol or Linux mount commands). The documentation assumes a general audience but implicitly prioritizes Windows/PowerShell workflows and omits parity Linux guidance.
Recommendations
- When listing tools or commands, mention Azure CLI before or alongside Azure PowerShell, as CLI is cross-platform and more familiar to Linux users.
- Provide explicit Linux examples for common operations, such as mounting Azure Files shares using NFS or SMB on Linux, and querying properties using Bash/CLI.
- Include references to Linux tools and workflows (e.g., mount.cifs, mount.nfs, or relevant Linux client libraries) where appropriate.
- Add a section or callout for Linux administrators, highlighting any differences or considerations unique to Linux environments.
- Ensure parity in troubleshooting and failover instructions for both Windows and Linux clients.
Create Pull Request
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-ad-ds-overview.md
...storage/files/storage-files-identity-ad-ds-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows terminology, tools, and workflows. Windows-specific concepts (such as Windows ACLs, DACLs, and domain join instructions) are emphasized, while Linux equivalents are either omitted or only briefly mentioned. Troubleshooting and mounting guidance reference Windows resources, and there are no Linux-specific examples or instructions for mounting or managing permissions. Linux is mentioned only in passing as a supported client OS, with no parity in examples or operational guidance.
Recommendations
- Add explicit Linux examples for mounting Azure file shares using SMB (e.g., using the 'mount' command or cifs-utils).
- Include Linux-specific troubleshooting links and guidance, similar to the Windows troubleshooting reference.
- Describe how file/directory-level permissions can be managed from Linux clients, or clarify any limitations.
- Mention Linux tools and commands alongside Windows tools (e.g., reference both Windows ACLs and POSIX ACLs, if applicable).
- Where domain join is discussed, provide links or instructions for joining Linux machines to AD DS (e.g., using realmd, sssd, or samba).
- Ensure that all steps and diagrams are inclusive of both Windows and Linux environments, or clearly state if certain features are Windows-only.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-server-registration.md
...les/storage/file-sync/file-sync-server-registration.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 instructions, prerequisites, and examples are specific to Windows Server, with exclusive use of Windows tools (Server Manager, PowerShell, Windows file paths, netsh, etc.). There are no Linux equivalents or cross-platform guidance, and the documentation assumes the user is operating in a Windows ecosystem throughout.
Recommendations
- Clearly state at the beginning whether Azure File Sync supports only Windows Server, or clarify platform limitations.
- If Linux support is available or planned, provide equivalent instructions, examples, and tools for Linux environments (e.g., bash scripts, Linux agent installation, Linux proxy configuration).
- If Azure File Sync is Windows-only, explicitly mention this in the prerequisites and introduction to set user expectations.
- Where possible, use cross-platform Azure CLI examples in addition to (or instead of) PowerShell, as Azure CLI is supported on Windows, Linux, and macOS.
- Avoid referencing Windows-specific UI tools (like Server Manager) without alternatives or clear notes for non-Windows users.
- For proxy and configuration steps, provide Linux file path and command equivalents if supported.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-manage-namespaces.md
...main/articles/storage/files/files-manage-namespaces.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. All examples, instructions, and tooling references are for Windows Server, PowerShell, and Windows DNS. There are no Linux equivalents or cross-platform considerations, and the documentation assumes the use of Windows-specific infrastructure and management tools throughout.
Recommendations
- Clearly state early in the documentation that DFS Namespaces is a Windows Server feature and is not natively available on Linux, but mention any possible alternatives or interoperability scenarios for Linux clients.
- Where possible, provide guidance for Linux clients accessing DFS-N managed shares (e.g., using smbclient, mount.cifs, or other SMB tools on Linux).
- If relevant, mention open-source or cross-platform alternatives to DFS-N (such as Samba DFS support or other namespace/virtualization solutions) and their compatibility with Azure Files.
- Add a section on how non-Windows environments can interact with Azure Files and DFS-N, including any limitations or required configurations.
- In sections about DNS, mention how to create CNAME records using Linux-based DNS servers (e.g., BIND) or via Azure DNS, not just Windows DNS.
- Where PowerShell is used, note that these commands are for Windows and provide any possible cross-platform alternatives or clarify that Linux/macOS users will need to use Windows tools for DFS-N management.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/migrate-files-storage-mover.md
.../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 demonstrates a Windows-first bias by referencing Windows tools (Robocopy), mentioning Windows Server and Azure File Sync for Windows Server before Linux, and omitting Linux-specific migration tools or examples. While it states that SMB sources can be Windows, Linux, or NAS, all concrete examples, tool references, and alternative migration paths are Windows-centric. There are no Linux command-line examples, nor are Linux migration tools or patterns discussed.
Recommendations
- Include Linux-specific migration tool references (e.g., rsync, smbclient) as alternatives to Robocopy.
- Provide example workflows or commands for migrating from Linux SMB shares, not just Windows.
- Mention Linux/NAS migration scenarios explicitly and equally alongside Windows scenarios.
- If Azure File Sync is only for Windows, clarify this and suggest Linux-friendly alternatives.
- Ensure that all steps (such as agent registration) include both Windows and Linux command-line examples where applicable.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-data-protection-overview.md
...ticles/storage/files/files-data-protection-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. Azure PowerShell is given a dedicated section before Azure CLI, and Azure File Sync (a Windows-only tool) is presented as the default hybrid backup solution without mentioning Linux alternatives. There is no discussion of Linux-native backup or restore patterns, and the SMB protocol (primarily used by Windows) is emphasized over NFS (used by Linux/UNIX).
Recommendations
- Add explicit examples and guidance for Linux administrators, such as using NFS shares and Linux-native tools for backup and restore.
- Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform and more familiar to Linux users.
- Mention the limitations of Azure File Sync for Linux and suggest alternative hybrid backup strategies for Linux file servers.
- Include references to Linux automation (e.g., Bash scripting, cron jobs) for managing Azure Files data protection.
- Clarify protocol support and provide parity in documentation for both SMB (Windows) and NFS (Linux/UNIX) scenarios.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-ad-ds-update-password.md
.../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-specific tools and PowerShell cmdlets (AzFilesHybrid, Active Directory PowerShell), with explicit requirements for Windows environments (domain-joined Windows client, Windows PowerShell 5.1). There are no Linux or cross-platform alternatives or examples, and Windows tooling is mentioned first and exclusively.
Recommendations
- Provide equivalent instructions for Linux environments, such as using cross-platform Azure CLI or REST API for Kerberos key rotation if supported.
- Clarify whether the process is fundamentally Windows-only due to AD DS requirements, or if there are supported Linux-based management options (e.g., via Samba, LDAP tools, or Azure CLI).
- If Linux parity is not possible, explicitly state this limitation early in the documentation.
- Where possible, use cross-platform scripting languages or tools (e.g., Python, Azure CLI) for examples.
- Add a section or note addressing Linux administrators and their options (or lack thereof) for this scenario.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/authorize-oauth-rest.md
...ob/main/articles/storage/files/authorize-oauth-rest.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples and instructions, referencing Windows-centric tools (PowerShell, AzCopy), and presenting PowerShell before CLI. There are no explicit Linux shell (bash) or cross-platform scripting examples, and the CLI section, while present, is less detailed and still assumes familiarity with Azure CLI rather than native Linux tools or workflows. No Linux-specific guidance or troubleshooting is provided.
Recommendations
- Add Linux shell (bash) examples for common operations, such as using curl or wget with REST APIs, or scripting with bash.
- Include parity in example depth and detail for Azure CLI and bash scripts, matching the PowerShell sections.
- Reference cross-platform tools (e.g., AzCopy, Storage Explorer) with explicit Linux usage instructions and installation steps.
- Reorder sections to present Azure CLI and bash examples before or alongside PowerShell to avoid a 'Windows-first' impression.
- Provide troubleshooting tips or notes for Linux users, such as file path conventions, authentication caveats, or package dependencies.
- Explicitly state that all examples are cross-platform where applicable, and clarify any OS-specific limitations.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-whats-new.md
...cs/blob/main/articles/storage/files/files-whats-new.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by frequently prioritizing Windows-specific features (such as Azure File Sync, which is only available for Windows), referencing Windows tools (PowerShell) before or more prominently than cross-platform alternatives, and providing detailed instructions or examples for Windows scenarios while omitting equivalent Linux guidance. Linux support is mentioned for certain NFS and Kerberos features, but overall, Windows and PowerShell are more deeply integrated and discussed, especially for management and agent deployment scenarios.
Recommendations
- When referencing management tools, always mention Azure CLI and REST API alongside PowerShell, and provide parity in example commands for both Windows and Linux environments.
- For features like Azure File Sync, clearly state platform limitations and, where possible, suggest alternative solutions for Linux (such as rsync, AzCopy, or third-party sync tools).
- Ensure that new features and enhancements are described with both Windows and Linux use cases, including explicit Linux client scenarios where applicable.
- Add Linux-specific examples and workflows, especially for mounting, managing, and securing file shares, to match the depth provided for Windows.
- Review the order of tool and platform mentions to avoid always listing Windows or PowerShell first; alternate or group by scenario instead.
- Where screenshots or UI walkthroughs are provided, include Linux/Unix terminal examples or references to relevant Linux documentation.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/glusterfs-migration-guide.md
...in/articles/storage/files/glusterfs-migration-guide.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 tools (Robocopy, PowerShell cmdlets) are mentioned by name and with detailed usage before their Linux equivalents. Windows-specific instructions and tools (e.g., Robocopy, 'Get-AzStorageAccountKey', 'net use', PowerShell) are given prominence and more detailed explanation, while Linux tools (rsync, fpsync) are mentioned but with less depth and sometimes only as alternatives. In some cases, Windows tools are referenced in the main text or 'See also' section without equal Linux coverage. The troubleshooting and verification steps also mention Windows commands first or in more detail.
Recommendations
- Ensure Linux tools (rsync, fpsync) are given equal prominence and detailed explanation as Robocopy, including advanced usage examples and troubleshooting.
- When listing tools or procedures, alternate the order (sometimes Linux first) or present both platforms in parallel to avoid 'windows_first' bias.
- Provide PowerShell and Bash/Linux CLI equivalents for all commands (e.g., retrieving storage account keys, mounting shares) and link to relevant Linux documentation where appropriate.
- Expand the 'See also' section to include more Linux-focused migration and troubleshooting resources, not just Robocopy or Windows-centric links.
- Where possible, avoid assuming Windows as the default platform (e.g., in migration tool recommendations or step-by-step guides).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-netapp-comparison.md
...icles/storage/files/storage-files-netapp-comparison.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a moderate Windows bias. Migration tools such as Robocopy and Storage Migration Service (both Windows-centric) are listed without Linux equivalents or context. There are no Linux/UNIX-native migration tools (e.g., rsync, NFS utilities) mentioned, and no Linux-specific examples or guidance are provided. Additionally, Windows tools are listed before cross-platform or Linux tools, reinforcing a Windows-first perspective.
Recommendations
- Include Linux-native migration tools such as rsync, NFS utilities, or Linux-based data movers in the 'Migration Tools' section.
- Provide examples or references for mounting and using Azure Files and Azure NetApp Files from Linux systems, not just SMB/Windows-centric tools.
- Ensure that tool lists and examples are balanced, listing cross-platform or Linux tools alongside or before Windows-specific tools.
- Add links to Linux-focused documentation or quickstarts for both Azure Files and Azure NetApp Files.
- Explicitly mention compatibility and best practices for Linux workloads where relevant, especially in sections discussing protocols, authentication, and migration.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-auth-hybrid-identities-enable.md
...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. All operating system prerequisites, configuration steps, and client instructions are specific to Windows (Windows 10/11, Windows Server). Only Windows tools and patterns are described (PowerShell, Group Policy, Intune, Registry, ksetup, Windows File Explorer, icacls), and there are no examples or guidance for Linux or macOS clients. The documentation does not mention or address how to use Microsoft Entra Kerberos authentication for Azure Files from non-Windows platforms, nor does it clarify if such scenarios are unsupported.
Recommendations
- Explicitly state whether Linux and macOS clients are supported or unsupported for Microsoft Entra Kerberos authentication with Azure Files.
- If Linux/macOS support exists or is planned, provide equivalent configuration and usage instructions for those platforms (e.g., using smbclient, mount.cifs, krb5.conf configuration, kinit, etc.).
- If only Windows is supported, add a clear note at the top of the documentation to inform users of this limitation.
- Where possible, provide cross-platform examples for Azure CLI and other tools, or clarify any OS-specific differences.
- Consider including a section on interoperability, outlining what is and isn't possible from non-Windows clients.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-smb-protocol.md
...blob/main/articles/storage/files/files-smb-protocol.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a clear Windows bias. Windows terminology, tools, and examples (such as PowerShell and Windows registry edits) are presented exclusively or before Linux equivalents. Windows-specific configuration steps and troubleshooting (e.g., registry keys, Set-SmbClientConfiguration) are detailed, while Linux client configuration for SMB (such as cifs-utils or smb.conf) is not addressed. Linux is only mentioned in passing, and there are no Linux-specific SMB client instructions or troubleshooting guidance.
Recommendations
- Add Linux-specific SMB client configuration and troubleshooting sections, including mounting instructions using cifs-utils and relevant smb.conf options.
- When discussing client-side encryption settings (e.g., AES-256-GCM), provide equivalent Linux commands or configuration (such as mount options or smb.conf parameters) and note Linux kernel/Samba version requirements.
- Include Linux examples alongside PowerShell and Azure CLI, especially for client configuration and security settings.
- When referencing Windows registry or PowerShell commands for enabling features, provide Linux alternatives or explicitly state if a feature is not configurable or required on Linux.
- Ensure that Linux is mentioned equally in scenario descriptions, not only as a legacy or secondary consideration.
- Where possible, provide parity in troubleshooting steps for both Windows and Linux clients.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-active-directory-overview.md
...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, Kerberos as implemented in Windows environments), and by omitting Linux-specific examples or guidance. While there is a single mention that Linux clients are supported, the rest of the content, including terminology, diagrams, and use cases, is framed around Windows-centric identity sources and workflows. There are no Linux command examples, nor is there parity in describing how Linux clients interact with Azure Files using identity-based authentication.
Recommendations
- Add explicit Linux client examples and workflows for identity-based authentication, including references to relevant Linux tools (e.g., mount.cifs, Kerberos configuration on Linux, kinit, etc.).
- Include diagrams or workflow descriptions that illustrate Linux client authentication flows, not just Windows/AD-centric ones.
- Balance terminology and use cases by mentioning Linux and cross-platform scenarios alongside Windows, rather than after or as an aside.
- Provide links to Linux-specific documentation and troubleshooting guides for SMB/Kerberos integration with Azure Files.
- Where Windows-specific features (like DACLs) are mentioned, clarify Linux equivalents (such as POSIX ACLs) or note any limitations.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-authorization-overview.md
.../storage/files/storage-files-authorization-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools (File Explorer, icacls, Set-ACL, robocopy) for managing directory and file-level permissions and for preserving ACLs. No Linux or cross-platform equivalents are mentioned, and all examples and instructions assume a Windows environment. The ordering and phrasing also present Windows methods first and exclusively, with no guidance for Linux users.
Recommendations
- Include Linux-compatible instructions and examples for configuring directory and file-level permissions, such as using the 'smbclient' or 'mount.cifs' tools and Linux ACL commands (e.g., 'setfacl', 'getfacl').
- Mention and provide examples of cross-platform or REST API-based methods for managing permissions, if available.
- When discussing tools for copying data and preserving ACLs, reference Linux alternatives (e.g., 'rsync' with SMB mounts, 'smbclient', or other relevant tools) and clarify any limitations or differences.
- Rephrase sections to avoid implying that only Windows environments are supported, and ensure parity in the order and detail of Windows and Linux instructions.
- Add a note or section explicitly addressing Linux/macOS clients and their support or limitations for Azure Files authorization and ACL management.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/smb-performance.md
...cs/blob/main/articles/storage/files/smb-performance.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All configuration and verification steps for SMB Multichannel are exclusively described for Windows clients, using Windows PowerShell commands and Windows-specific tools (e.g., robocopy, diskspd.exe). There are no Linux examples or instructions for enabling, verifying, or testing SMB Multichannel from Linux clients. References to documentation and tools are Windows-centric, and Linux support is only mentioned in passing (for metadata caching), without any actionable guidance.
Recommendations
- Add explicit guidance and examples for configuring, enabling, and verifying SMB Multichannel on Linux clients (e.g., using modern Linux kernels with SMB3.1.1, mounting with appropriate cifs options, and using smbstatus or similar tools).
- Provide Linux command-line equivalents for all PowerShell/Windows commands (e.g., show how to check SMB Multichannel status on Linux).
- Include Linux-compatible performance testing tools (e.g., fio, dd, or iozone) alongside Windows tools like diskspd.exe and robocopy.
- Reference Linux documentation for SMB Multichannel (e.g., Samba, kernel.org) in the 'Next steps' and throughout the article.
- Ensure that all feature descriptions and limitations clarify support for both Windows and Linux clients, and provide parity in troubleshooting and verification steps.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-mount-file-share.md
...orage/files/storage-files-identity-mount-file-share.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Windows environments, providing only Windows-specific instructions, tools (PowerShell, net use, setspn, DNS Manager), and examples for mounting SMB Azure file shares. There are no Linux or cross-platform examples, and Windows tools and patterns are mentioned exclusively and first throughout the document.
Recommendations
- Add equivalent instructions and examples for mounting SMB Azure file shares on Linux clients, using tools such as mount.cifs and Kerberos authentication.
- Include Linux prerequisites, such as required packages (e.g., cifs-utils, krb5-user) and configuration steps for Kerberos and credential management.
- Provide troubleshooting guidance for Linux environments, including common errors and diagnostic commands.
- Present both Windows and Linux examples side-by-side or in parallel sections to ensure parity and inclusivity.
- Reference cross-platform tools or approaches where possible, and clarify any Azure Files limitations or differences between Windows and Linux clients.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-faq.md
.../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 demonstrates a Windows-centric bias. Many examples and troubleshooting steps reference Windows tools (PowerShell, File Explorer, cmdkey, net use, icacls) without providing Linux/macOS equivalents. Windows terminology and workflows are described in detail, while Linux is only mentioned in passing or in NFS-specific sections. There are no Linux command examples for common tasks such as mounting, credential management, or ACL handling. The documentation assumes Windows as the default environment for Azure File Sync and related features.
Recommendations
- Provide equivalent Linux/macOS command-line examples (e.g., mount.cifs, smbclient, setfacl, getfacl) alongside Windows/PowerShell instructions for mounting, credential management, and ACL operations.
- When referencing tools like PowerShell, File Explorer, or Windows commands, also mention and demonstrate how to perform the same tasks on Linux and macOS.
- Avoid assuming Windows as the default platform in explanations; explicitly address cross-platform scenarios where possible.
- Include troubleshooting steps and best practices for Linux and macOS clients, especially for authentication, file locking, and metadata preservation.
- Expand the 'Security, authentication, and access control' section to cover Linux-specific auditing and access control mechanisms.
- Ensure that all protocol-agnostic features (e.g., snapshots, billing, redundancy) are described in a platform-neutral way, with examples for all supported OSes.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-nas-hybrid.md
...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 biased towards Windows environments. It assumes the migration target is always a Windows Server, only provides instructions and examples for Windows (e.g., RoboCopy, Windows Server setup), and does not mention or provide alternatives for Linux-based systems or tools. There are no Linux/Unix migration examples, and all operational steps are Windows-centric.
Recommendations
- Add a section or guidance for scenarios where the migration target is a Linux server or where Linux tools are preferred.
- Provide equivalent Linux command-line examples (e.g., using rsync, cifs-utils, or Azure CLI on Linux) for copying data from NAS to Azure.
- Mention and compare Linux-compatible tools (such as azcopy, rsync, or Azure Storage Mover CLI) alongside Windows tools like RoboCopy.
- Clarify early in the document that Azure File Sync is only supported on Windows, but offer migration alternatives for Linux-based environments.
- Include troubleshooting tips and best practices for Linux users migrating SMB/NFS shares to Azure File Shares.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-ad-ds-enable.md
...s/storage/files/storage-files-identity-ad-ds-enable.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All examples and instructions use Windows PowerShell (specifically PowerShell 5.1), Windows-based tools (Active Directory PowerShell module, Setspn, etc.), and require a Windows domain-joined device. There are no examples or guidance for performing these tasks from Linux or cross-platform environments, nor any mention of Linux-based tools or methods for managing AD DS integration with Azure Files.
Recommendations
- Provide equivalent instructions and examples for Linux environments, including how to join Azure Files to AD DS using Linux-based tools (such as Samba's net ads join, Kerberos utilities, or LDAP tools).
- Clarify whether the process is supported or unsupported from non-Windows systems, and if unsupported, explicitly state this early in the documentation.
- If possible, offer Azure CLI or REST API alternatives for steps currently requiring PowerShell, to improve cross-platform accessibility.
- Include troubleshooting and verification steps that can be performed from Linux clients, such as mounting Azure Files shares using Kerberos authentication from Linux.
- Add a section discussing Linux support and any limitations, with links to relevant documentation for Linux-based AD DS integration.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-configure-file-level-permissions.md
...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 is heavily Windows-centric, focusing exclusively on Windows ACLs, Windows tools (icacls, File Explorer, net use), and PowerShell. There are no examples or guidance for configuring permissions from Linux clients, nor is there mention of Linux tools or workflows. The documentation assumes a Windows environment throughout and does not address cross-platform scenarios or NFS shares.
Recommendations
- Add a section explicitly stating the (lack of) support for configuring file/directory-level permissions from Linux clients, and clarify if this is a technical limitation or a documentation gap.
- If possible, provide Linux-based guidance for mounting Azure Files (SMB) shares and clarify what permission management is possible from Linux (e.g., using smbclient, mount.cifs, or other tools).
- Mention and document NFS options for Linux clients, if applicable, and clarify the differences in permission models.
- If Windows ACLs are only manageable from Windows, state this clearly at the top and suggest alternative approaches for Linux environments.
- Include parity in examples: if only Windows is supported, explain why; if Linux is supported, provide equivalent Linux commands and workflows.
- Consider including a table comparing Windows and Linux support for Azure Files permission management.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-assign-share-level-permissions.md
...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 demonstrates a Windows bias by focusing on Windows-centric concepts (Active Directory, Windows ACLs), referencing Windows tools (PowerShell cmdlets), and using Windows terminology (SMB, ACLs) throughout. Linux/NFS scenarios are explicitly marked as unsupported, and there are no Linux-specific examples or guidance for managing permissions from Linux clients or with Linux-native tools.
Recommendations
- Include explicit guidance and examples for Linux/NFS scenarios where supported, or provide clear alternatives or workarounds for Linux users.
- When referencing ACLs and permissions, clarify the applicability to both Windows and Linux clients, or state limitations more prominently.
- Provide parity in examples by including Bash/shell scripts and Linux CLI usage alongside PowerShell, especially for cross-platform tools like Azure CLI.
- If certain features are Windows-only (e.g., SMB/ACLs), add a section summarizing Linux/NFS support status and recommended approaches for Linux environments.
- Avoid using Windows terminology (e.g., 'Windows ACLs') as the default; instead, use more generic terms (e.g., 'file system ACLs') and specify when something is Windows-specific.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-auth-domain-services-enable.md
...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 strong Windows bias. It consistently references Windows-specific tools and workflows (such as Windows PowerShell, Windows Server Active Directory cmdlets, and Windows domain-joined VMs) and provides detailed instructions and examples only for Windows environments. There are no Linux-specific instructions or examples for mounting Azure Files with Microsoft Entra Domain Services, nor guidance for Linux domain-joined VMs or Kerberos configuration on Linux. The prerequisites and workflow are described solely from a Windows perspective.
Recommendations
- Add equivalent Linux instructions for mounting Azure Files with Microsoft Entra Domain Services authentication, including Kerberos configuration and troubleshooting.
- Provide examples using Linux command-line tools (e.g., kinit, smbclient, mount.cifs) for accessing Azure file shares with identity-based authentication.
- Include guidance for domain-joining Linux VMs to Microsoft Entra Domain Services, if supported, or clearly state any platform limitations.
- When listing tools or workflows, present both Windows and Linux options, or clarify platform support early in the document.
- If Linux is not supported for this scenario, explicitly state this in the prerequisites and introduction to set expectations.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-introduction.md
...n/articles/storage/files/storage-files-introduction.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a Windows bias by prioritizing Windows terminology, tools, and scenarios. Windows and PowerShell are mentioned before Linux equivalents, and Windows-specific features (like Azure File Sync and AD DS integration) are highlighted without parallel Linux guidance. The scripting/tooling section emphasizes PowerShell, and the 'next steps' section lists Windows mounting instructions before Linux. There is a lack of Linux-specific examples or parity in feature discussion.
Recommendations
- Ensure Linux and macOS examples are presented alongside or before Windows examples, especially in introductory and 'getting started' sections.
- Highlight Linux-compatible tools (e.g., Bash, Azure CLI) equally with PowerShell.
- Provide Linux equivalents for features like Azure File Sync or clarify if alternatives exist.
- Balance the discussion of identity/authentication by mentioning Linux integration options (e.g., LDAP, Kerberos) where relevant.
- In the 'next steps' and similar lists, alternate the order or group by OS to avoid always listing Windows first.
- Add explicit Linux and macOS scripting/tooling guidance (e.g., Bash scripts, mount commands) in relevant sections.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-linux-hybrid.md
.../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 Windows-centric, focusing on migration from Linux to Windows Server for Azure File Sync. It consistently prioritizes Windows tools (notably Robocopy), provides detailed steps only for Windows Server, and omits concrete Linux command examples or parity guidance. Linux tools and approaches are mentioned only briefly and generically, with no practical examples or step-by-step instructions. The documentation assumes and enforces a Windows Server intermediary, with little to no actionable guidance for Linux administrators beyond the initial migration trigger.
Recommendations
- Provide concrete Linux command examples (e.g., using rsync, cp, or scp) for copying data from Linux to Windows, including syntax and options to preserve permissions and metadata.
- Include a section comparing Windows and Linux copy tools, with a table of features and caveats for each.
- Offer step-by-step guidance for Linux administrators, including how to mount Windows shares from Linux and copy data directly.
- List common Linux pitfalls (e.g., character encoding, permission mapping) and how to address them during migration.
- Reference or link to Linux-specific migration tools or scripts where appropriate.
- Ensure that Linux and Windows approaches are presented with equal prominence, or at least provide clear Linux-first pathways where possible.