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 151-175 of 1657 flagged pages
Storage
Azure File Sync on-premises firewall and proxy settings
...cles/storage/file-sync/file-sync-firewall-and-proxy.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All examples, configuration steps, and troubleshooting instructions use Windows-specific tools (PowerShell, netsh, .NET config files, Windows paths). There are no references to Linux equivalents, nor any guidance for non-Windows platforms. The documentation assumes the use of Windows Server throughout and does not address scenarios for Linux servers or cross-platform agent support.
Recommendations
- Clearly state platform requirements and limitations at the beginning (e.g., 'Azure File Sync agent is only supported on Windows Server').
- If Linux support is planned or available, provide equivalent examples for Linux (e.g., using curl, iptables, systemd, or other Linux-native tools for proxy/firewall configuration and connectivity testing).
- Where possible, abstract instructions to be platform-neutral (e.g., describe required network/proxy/firewall settings in terms of protocols and endpoints, not just Windows config files).
- Add troubleshooting steps for Linux environments, if supported, or explicitly mention that troubleshooting is only applicable to Windows.
- If PowerShell is required, clarify that it is a Windows-only tool and suggest alternatives for Linux (such as Azure CLI or REST API usage).
- Provide a comparison table of configuration steps for Windows and Linux, or mention the lack of Linux support if that is the case.
Create Pull Request
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
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments. All command-line examples use PowerShell, and the only agent referenced is the Azure File Sync agent, which is Windows-only. There are no Linux-specific instructions, tools, or examples, and the documentation assumes the use of Windows servers or Azure Arc-enabled servers (which also require Windows for Azure File Sync). The use of PowerShell and Windows-centric terminology throughout the page further reinforces the Windows bias.
Recommendations
- Explicitly state that Azure File Sync is currently only supported on Windows Server, if that is the case. If Linux support is planned or available, add equivalent instructions and examples for Linux environments.
- Provide parity in command-line examples by including Azure CLI or Bash instructions where possible, especially for identity and role assignment steps.
- Clarify the requirements and limitations for non-Windows environments (e.g., Azure Arc-enabled Linux servers) and provide guidance or alternatives for Linux users.
- If PowerShell is required, explain why and offer alternatives or workarounds for users on Linux or macOS.
- Add a section addressing cross-platform considerations, including any roadmap or links to Linux support if available.
Storage
Azure File Sync networking considerations
...les/storage/file-sync/file-sync-networking-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation is heavily focused on Windows environments, with all examples and instructions referencing Windows Server, PowerShell cmdlets, and Windows-specific tools. There are no Linux-specific examples, instructions, or mentions of Linux support for Azure File Sync. PowerShell is used exclusively for configuration tasks, and Windows terminology is prevalent throughout the document.
Recommendations
- Add explicit statements about Azure File Sync support (or lack thereof) for Linux servers, clarifying platform compatibility.
- Provide equivalent Linux examples where possible, such as using Bash, curl, or Azure CLI for networking and DNS configuration.
- Include Linux tools (e.g., dig, nslookup on Linux) in DNS resolution examples, not just PowerShell.
- If Azure File Sync is Windows-only, make this clear early in the documentation and provide guidance for Linux users on alternative solutions (such as mounting Azure Files directly via SMB/NFS).
- Balance the order of instructions and examples so that Linux and cross-platform tools are mentioned alongside or before Windows-specific ones where relevant.
Storage
Configure Azure File Sync network endpoints
...es/storage/file-sync/file-sync-networking-endpoints.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows terminology and tools (PowerShell, Windows file servers) are used throughout, with Windows-centric concepts (e.g., 'registered servers, which are Windows file servers') presented as the default. PowerShell examples are given for most operations, and in some cases, only PowerShell is supported (e.g., disabling Storage Sync Service public endpoint). Output examples are shown for Windows, and there is no mention of Linux equivalents for Azure File Sync agent or server registration. While Azure CLI and Bash examples are provided for networking configuration, the core sync service is described as Windows-only, and Linux use cases are not addressed.
Recommendations
- Explicitly state platform limitations (e.g., Azure File Sync agent is Windows-only) at the beginning of the article.
- Provide Linux-specific guidance or alternatives for file share access and network endpoint configuration, where possible.
- Include output examples for Linux/macOS terminals alongside Windows/PowerShell outputs.
- Where PowerShell is the only supported method, clarify why and suggest any workarounds or alternatives for Linux users.
- If Azure File Sync is not available for Linux, link to documentation for Linux-compatible Azure Files solutions.
- Review terminology to avoid assuming Windows as the default (e.g., refer to 'on-premises servers' rather than 'Windows file servers' where appropriate).
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 page exhibits a strong Windows bias: Azure File Sync is described as a solution for Windows Server only, with all deployment, management, and troubleshooting examples and tools (such as PowerShell cmdlets) being Windows-centric. There are no Linux-specific instructions, examples, or parity in tooling, and Windows terminology, features, and patterns (NTFS, BitLocker, DFS, Data Deduplication, etc.) are referenced exclusively or before any cross-platform alternatives. Linux is only mentioned in passing as a client for mounting SMB shares, not as a supported platform for Azure File Sync itself.
Recommendations
- Clearly state platform limitations at the top of the documentation, including that Azure File Sync is Windows Server-only, and provide guidance for Linux users seeking similar functionality.
- Where possible, offer Linux equivalents or alternatives for features (e.g., suggest third-party or Azure-native solutions for file caching/sync on Linux).
- Include cross-platform examples for mounting Azure file shares, management, and backup, not just Windows/PowerShell.
- Reference Linux file system compatibility and limitations, and provide links to relevant documentation for Linux-based solutions.
- If Azure File Sync will not support Linux, provide a comparison table of features between Windows and Linux approaches to Azure Files, and recommend best practices for Linux environments.
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
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All examples use Windows-specific tools (Robocopy), commands are given for the Windows command line, and there is no mention of Linux equivalents or instructions for non-Windows platforms. The workflow assumes Windows Server and Windows VMs, with no guidance for Linux-based Azure File Sync servers or cross-platform scenarios.
Recommendations
- Provide equivalent instructions for Linux environments, including supported file copy tools (e.g., rsync, cp, or smbclient) and relevant command examples.
- Clarify whether Azure File Sync supports Linux servers, and if so, include steps for Linux-based endpoints.
- Mention Linux tools and patterns alongside Windows tools, or at least after them, to ensure parity.
- Add notes about platform limitations, and if only Windows is supported, make this explicit early in the documentation.
- Where possible, use platform-agnostic terminology and workflows, or clearly separate Windows and Linux instructions.
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 and referencing only Windows-specific tools (e.g., Robocopy, DFS-N). There are no examples or guidance for Linux servers or cross-platform scenarios, and all instructions and terminology are tailored to Windows environments.
Recommendations
- Clarify whether Azure File Sync supports Linux servers, and if so, provide equivalent instructions and examples for Linux environments.
- If Robocopy is recommended for file copying, suggest Linux alternatives (such as rsync) and provide example commands.
- Mention and explain any Linux-compatible methods for user cut-over, such as NFS exports, Samba shares, or Linux DFS equivalents, if applicable.
- Ensure that documentation sections do not assume Windows-only environments, and provide parity in guidance for other supported platforms.
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
Summary
The documentation exclusively describes file migration using Robocopy, a Windows-only tool, and instructs users to deploy a Windows VM. There are no Linux migration examples, nor are Linux tools (such as rsync or smbclient) mentioned. The guidance assumes a Windows environment and does not provide parity for Linux users.
Recommendations
- Add migration instructions using Linux-compatible tools such as rsync or smbclient.
- Include examples for mounting Azure SMB file shares on Linux VMs.
- Present both Windows and Linux migration options side-by-side, or clarify platform requirements up front.
- Reference cross-platform tools (e.g., AzCopy) where applicable and provide usage examples for both OSes.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation for Azure File Sync is heavily Windows-centric. All agent installation, configuration, and troubleshooting instructions are exclusively for Windows Server (2012 R2, 2016, 2019, 2022, 2025). The only supported file system is NTFS. All operational examples and tools (such as PowerShell cmdlets, Robocopy, .NET Framework requirements) are Windows-specific, with no mention of Linux, Linux file systems, or cross-platform alternatives. There are no Linux installation instructions, examples, or parity notes.
Recommendations
- Explicitly state Azure File Sync is Windows-only, or clarify platform limitations early in the documentation.
- If Linux support is planned, add a roadmap or parity statement.
- Provide guidance for hybrid environments (e.g., syncing between Windows and Linux file shares using Azure Files).
- Offer alternative examples for Linux users (e.g., using Azure CLI, azcopy, or REST API for monitoring and management).
- Document limitations and alternatives for Linux file servers, such as using Azure Files directly or third-party sync tools.
- Add a comparison table of supported/unsupported platforms and features.
Storage
Azure File Sync resource moves and topology changes
.../articles/storage/file-sync/file-sync-resource-move.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell as the only CLI example for managing Azure File Sync resources (specifically for assigning managed identities), and by referencing Windows-centric tools and patterns (such as PowerShell and the Azure portal). There are no examples or instructions for performing equivalent operations using Linux-friendly tools like Azure CLI, Bash, or REST API. This may disadvantage users who administer Azure resources from Linux or cross-platform environments.
Recommendations
- Add equivalent Azure CLI and/or Bash examples for all resource management tasks currently shown only in PowerShell.
- Explicitly mention that all operations can be performed from Linux/macOS environments, and provide links or steps for cross-platform tooling.
- Where PowerShell is referenced, provide side-by-side examples using Azure CLI or REST API.
- Clarify that the Azure portal is accessible from any OS, but also offer command-line alternatives for automation and scripting.
- Review all sections for implicit Windows assumptions and ensure Linux parity in terminology and instructions.
Storage
Create an Azure File Sync Server Endpoint
.../storage/file-sync/file-sync-server-endpoint-create.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page exhibits a Windows bias by exclusively referencing Windows-specific tools and patterns, such as PowerShell cmdlets (e.g., Invoke-StorageSyncFileRecall) and RoboCopy, without providing Linux equivalents or examples. All path examples use Windows-style drive letters (e.g., F:\sync1), and there is no mention of Linux support, commands, or filesystem conventions. The documentation implicitly assumes the server is running Windows, and does not address scenarios or instructions for Linux-based servers.
Recommendations
- Explicitly state platform requirements and clarify if Azure File Sync supports Linux servers. If Linux is supported, provide equivalent Linux commands and examples alongside Windows/PowerShell instructions.
- Include Linux filesystem path examples (e.g., /mnt/sync1) where appropriate, and discuss any differences in behavior or limitations for Linux deployments.
- Reference Linux tools (such as rsync) for migration scenarios, or explain how authoritative upload/mirroring can be achieved on Linux.
- If PowerShell is required, clarify whether PowerShell Core on Linux is supported, and provide installation and usage instructions for Linux environments.
- Add a section comparing Windows and Linux server endpoint setup, highlighting any platform-specific considerations, limitations, or best practices.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily Windows-centric: it only references Windows Server and Azure VMs running Windows, exclusively mentions the Azure File Sync agent for Windows, and provides a Robocopy command (a Windows tool) for data recovery. There are no Linux equivalents, examples, or mentions, and the workflow assumes a Windows environment throughout.
Recommendations
- Explicitly state platform requirements and limitations (e.g., if Azure File Sync is Windows-only, clarify this early in the documentation).
- If Linux support is possible, provide equivalent instructions and examples for Linux environments, including alternative tools (e.g., rsync instead of Robocopy).
- If Azure File Sync is not available for Linux, suggest alternative solutions for Linux users, such as using Azure File Share mounting and Linux-native sync tools.
- Add a comparison table or section outlining differences in recovery procedures between Windows and Linux.
- Ensure that cross-platform considerations are addressed in prerequisites and throughout the workflow.
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
Windows First
Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All instructions, screenshots, and examples reference Windows-only tools such as Task Scheduler, Event Viewer, and PowerShell cmdlets/scripts. There is no mention of Linux equivalents, nor any guidance for deprovisioning Azure File Sync endpoints from Linux servers. The documentation assumes the use of Windows Server and its GUI tools, with no cross-platform consideration.
Recommendations
- Add explicit guidance for Linux-based Azure File Sync endpoints, if supported.
- Provide CLI-based examples using cross-platform tools (e.g., Azure CLI, REST API) instead of or alongside PowerShell.
- Include screenshots or terminal output from Linux environments where applicable.
- Clarify platform requirements and limitations at the start of the documentation.
- If Azure File Sync is Windows-only, state this clearly and explain why Linux is not supported.
Storage
Manage Registered Servers with Azure File Sync
...les/storage/file-sync/file-sync-server-registration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All instructions, prerequisites, and examples are exclusively for Windows Server. Only Windows tools (Server Manager UI, PowerShell, netsh, Windows file paths, Windows-specific agent installers) are mentioned. There are no Linux equivalents or cross-platform notes, and all scripting and automation is shown with PowerShell. The documentation assumes the user is operating within a Windows Server context and does not address Linux or cross-platform scenarios.
Recommendations
- Clearly state early in the documentation whether Azure File Sync is supported only on Windows Server, or if Linux support is planned or available.
- If Linux support exists or is planned, provide equivalent instructions, examples, and prerequisites for Linux systems (e.g., agent installation, registration, proxy configuration, and management).
- If Azure File Sync is Windows-only, explicitly mention this limitation in the introduction and prerequisites to set user expectations.
- Where possible, provide cross-platform PowerShell Core (pwsh) examples and clarify if cmdlets or modules are compatible with Linux/macOS.
- For proxy and network configuration, include Linux equivalents (e.g., modifying environment variables, editing relevant config files, using Linux command-line tools).
- Avoid assuming the presence of Windows-only tools (e.g., Server Manager UI, netsh) without alternatives or explanations for non-Windows users.
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 First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments. All migration steps assume the use of Windows Server, Windows VMs, and Windows-native tools such as Robocopy and PowerShell cmdlets (e.g., Invoke-StorageSyncFileRecall). There are no examples or instructions for performing these migrations from Linux clients or using Linux tools. The documentation references Windows-specific services like Storage Migration Service and does not mention Linux alternatives or cross-platform approaches.
Recommendations
- Provide equivalent migration instructions for Linux environments, including mounting Azure file shares on Linux and using Linux-native tools (e.g., rsync, cp, azcopy).
- Include Linux command-line examples for copying files between shares, such as rsync or azcopy usage.
- Mention how to install and use Azure File Sync agent or alternatives on Linux, or clarify its Windows-only support.
- Reference Linux SMB client configuration for mounting Azure file shares.
- Add troubleshooting and monitoring guidance for Linux users.
- Clearly indicate any limitations or requirements for Linux environments in Azure File Sync scenarios.
Storage
Analyze Azure Files metrics with Azure Monitor
...b/main/articles/storage/files/analyze-files-metrics.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell examples and referencing Windows-centric troubleshooting resources. While Azure CLI examples are present (which are cross-platform), there are no explicit Linux shell (bash) examples, nor are Linux-specific tools or troubleshooting patterns mentioned. The troubleshooting link uses a Windows tab by default, and there is no parity in guidance for Linux clients or NFS scenarios. The .NET SDK examples are platform-neutral, but the overall pattern is Windows-first.
Recommendations
- Add explicit bash/Linux shell examples for metric queries using Azure CLI, including sample scripts and environment notes.
- Include troubleshooting guidance and links for Linux clients (e.g., mounting Azure Files via SMB/NFS on Linux, performance investigation steps for Linux).
- Reference Linux tools (such as smbclient, mount.cifs, nfs-utils) where appropriate for monitoring or troubleshooting.
- Ensure that troubleshooting links and tabs provide Linux-first or equal visibility, not defaulting to Windows.
- Mention NFS monitoring and metrics where supported, and provide examples for NFS scenarios.
- Balance PowerShell and CLI examples by showing both in parallel, and clarify cross-platform applicability.
Storage
Enable access to Azure file shares using OAuth over REST
...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 page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. PowerShell is featured prominently with detailed step-by-step instructions, and Windows tools like AzCopy and Storage Explorer are mentioned before any Linux alternatives. There is a lack of explicit Linux or cross-platform examples, especially in the command-line sections, and no mention of Linux-specific patterns or tools for accessing Azure file shares via OAuth over REST. The CLI examples are generic and do not address Linux-specific nuances or shell environments.
Recommendations
- Add explicit Linux shell examples (e.g., bash) for Azure CLI commands, including environment setup and authentication nuances.
- Mention and provide examples for Linux-native tools (such as curl, wget, or REST API calls using bash) to access Azure file shares via OAuth over REST.
- Include guidance for using AzCopy and Storage Explorer on Linux, with installation and usage instructions.
- Ensure parity in step-by-step instructions for both PowerShell (Windows) and bash (Linux) environments.
- Clarify cross-platform compatibility of Azure CLI and SDKs, and provide troubleshooting tips for Linux users.
- Reorder sections to present CLI and REST API examples before PowerShell, or present them in parallel tabs for equal visibility.
Storage
Change Redundancy Configuration for Azure Files
...storage/files/files-change-redundancy-configuration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently presenting PowerShell examples and terminology, and by listing PowerShell before Azure CLI in most cases. While Azure CLI is included (which is cross-platform), there are no explicit Linux shell examples (e.g., Bash), nor any mention of Linux-specific tools or workflows. The documentation does not provide parity for Linux users in terms of command-line examples or guidance, and PowerShell is featured heavily, which is primarily a Windows-centric tool (despite its cross-platform availability).
Recommendations
- Add explicit Bash shell examples for Azure CLI commands, showing usage in a typical Linux environment.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any Linux-specific notes if relevant (e.g., installation, authentication).
- Balance the order of examples: alternate or randomize the order between PowerShell and CLI, or present CLI first in some sections.
- Mention Linux-native tools (such as AzCopy, which is referenced but not exemplified) and provide example usage in Linux.
- Where PowerShell is referenced, note its cross-platform availability and provide installation instructions for Linux if appropriate.
- Consider including screenshots or terminal outputs from Linux environments to visually represent parity.
Storage
Data Protection Overview for Azure Files
...ticles/storage/files/files-data-protection-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates Windows bias by prioritizing Windows-centric tools and patterns. Azure PowerShell is given a dedicated section before Azure CLI, and Azure File Sync (a Windows-only tool) is highlighted as the primary hybrid backup solution. There are no explicit Linux or cross-platform backup/restore examples, and Windows management paradigms (PowerShell, File Sync) are mentioned more prominently than their Linux equivalents.
Recommendations
- Add explicit Linux backup and restore examples, such as using native Linux SMB/NFS clients, rsync, or scripting with Azure CLI on Linux.
- Include information about Linux-compatible hybrid backup solutions, or clarify Azure File Sync's Windows-only nature and suggest alternatives for Linux servers.
- Ensure parity in tooling sections: present Azure CLI and REST API examples before or alongside PowerShell, and indicate cross-platform compatibility.
- Mention Linux-specific considerations for Azure Files (e.g., NFS support, mounting instructions, backup strategies) to balance the Windows focus.
- Where Windows tools are referenced (e.g., PowerShell, File Sync), provide links or notes for equivalent Linux workflows or tools.
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 Server DFS Namespaces, Windows DNS, and PowerShell for all examples and instructions. There are no references to Linux equivalents, cross-platform alternatives, or guidance for non-Windows environments. All tooling, screenshots, and walkthroughs assume a Windows Server infrastructure, with no mention of Linux SMB clients, Samba, or non-Windows DFS-like solutions.
Recommendations
- Add a section describing how Linux SMB clients can access DFS-N namespaces and Azure Files, including any limitations or configuration steps.
- Mention Samba as a potential alternative for namespace management in Linux environments, or clarify DFS-N's lack of support outside Windows.
- Provide explicit guidance on interoperability, such as how Linux users can mount DFS-N paths, and any caveats (e.g., lack of DFS-N client support in Linux).
- Include examples using Linux command-line tools (e.g., smbclient, mount.cifs) to access Azure Files shares.
- Clarify in the requirements and introduction that DFS-N is a Windows-only technology, and suggest alternatives or workarounds for Linux environments.
- If possible, link to documentation about cross-platform SMB access and namespace virtualization for non-Windows systems.
Storage
Disaster recovery and failover for Azure Files
...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 a Windows bias by consistently mentioning Azure PowerShell before Azure CLI when discussing how to query properties or initiate failover actions. There are no explicit Linux or Unix-specific examples, nor are Linux tools or workflows highlighted. The guidance and examples are platform-neutral in some areas, but where tooling is mentioned, Windows-centric tools (PowerShell) are prioritized or listed first, and Linux parity is not addressed.
Recommendations
- Ensure that all command-line examples are provided for both Azure PowerShell and Azure CLI, with equal prominence and ordering (alternate which is listed first, or present side-by-side).
- Explicitly mention Linux and macOS compatibility for Azure CLI and client libraries, and provide examples of usage on those platforms.
- Where file share mounting/remounting is discussed, include SMB/NFS mount instructions for Linux clients alongside any Windows instructions.
- Add troubleshooting or operational guidance for Linux environments, such as handling file handles, leases, and failover scenarios on Linux.
- Review linked articles to ensure Linux parity in disaster recovery and failover workflows.
Storage
Use Managed Identities with Azure Files (preview)
...ain/articles/storage/files/files-managed-identities.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by presenting PowerShell-based instructions and tooling first and in greater detail, especially in the initial setup and configuration sections. Windows-specific tools (e.g., AzFilesSmbMIClient, PowerShell modules) are described before their Linux equivalents, and the prerequisite steps are almost exclusively Windows/PowerShell-focused. Linux instructions are present but often follow Windows steps, are less detailed, and sometimes lack parity in example depth (e.g., troubleshooting, client library integration).
Recommendations
- Provide Linux CLI (e.g., Bash/Azure CLI) equivalents alongside PowerShell commands in all setup and configuration sections.
- Present Windows and Linux instructions in parallel (side-by-side tabs or sections) throughout the document, not just in later steps.
- Expand Linux troubleshooting guidance to match the detail provided for Windows (e.g., log file locations, diagnostic commands).
- Include Linux-specific prerequisites and environment setup steps (e.g., required packages, Azure CLI installation) at the same prominence as Windows/PowerShell.
- Ensure all client library integration examples for Linux are as detailed as those for Windows, including code samples and usage scenarios.
- Avoid language that implies Windows is the default or primary platform (e.g., 'Open PowerShell as administrator' before mentioning Linux alternatives).
Storage
What's New in Azure Files and Azure File Sync
...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 page demonstrates a moderate Windows bias. Windows terminology, features, and tools (such as PowerShell, Windows Server, and SMB) are frequently mentioned first or exclusively, especially in Azure File Sync sections. Examples and management instructions often reference PowerShell and Windows-centric workflows, with limited or no Linux-specific examples or parity for Azure File Sync. While NFS and Linux support are mentioned for Azure Files, Azure File Sync remains Windows-only, and Linux management tools or equivalent patterns are not discussed.
Recommendations
- Provide Linux-specific examples and workflows wherever possible, especially for Azure Files management and usage.
- Clearly indicate platform limitations (e.g., Azure File Sync is Windows-only) and suggest Linux alternatives or workarounds.
- Balance the order of presenting Windows and Linux features, ensuring Linux/NFS features are not always secondary.
- Include CLI and REST API examples for both Windows and Linux environments, not just PowerShell.
- Reference Linux tools (e.g., mount, nconnect, cron for scheduling) alongside Windows tools.
- Add documentation or links for managing Azure Files from Linux, including authentication, backup, and monitoring scenarios.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows/PowerShell examples are presented first and in more detail, Windows-specific tools (such as Azure File Sync and PowerShell) are mentioned and explained, and Linux equivalents are either absent or only briefly referenced. The guidance for geo-redundancy for SSD file shares centers on Windows file servers and Azure File Sync, with no mention of Linux-based alternatives. While an Azure CLI example is provided, it is secondary to the PowerShell example and requires additional tooling (jq) without further explanation. There is no discussion of mounting Azure Files from Linux clients or using Linux-native tools for redundancy or failover.
Recommendations
- Provide Linux-specific examples and workflows alongside Windows/PowerShell, such as using Bash scripts, cron jobs, or Linux file servers for geo-redundancy.
- Include guidance for mounting Azure Files on Linux clients (e.g., using SMB or NFS from Linux), and discuss failover/remounting procedures for Linux systems.
- Mention Linux-native tools (e.g., rsync, cron, systemd timers) for custom redundancy or backup solutions.
- Present Azure CLI and Linux workflows before or alongside PowerShell/Windows examples to ensure parity.
- Clarify the requirements and installation steps for jq and other Linux tools in the CLI example.
- Discuss Azure File Sync alternatives for Linux environments, or explicitly state limitations and recommend best practices for Linux users.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: Windows and PowerShell are prioritized in examples and troubleshooting, Windows-specific tools and registry edits are referenced without Linux equivalents, and there is a lack of Linux-specific operational guidance for SMB features such as Multichannel and encryption settings. While Azure CLI (cross-platform) is included, all client-side configuration and troubleshooting examples are Windows-centric, with no Linux or macOS client configuration or troubleshooting steps provided for advanced SMB features.
Recommendations
- Add Linux (and macOS, if relevant) client configuration and troubleshooting examples for SMB Multichannel, encryption, and protocol settings. For example, show how to verify and enable SMB Multichannel on Linux clients using smb.conf and test tools.
- When referencing PowerShell or Windows registry changes, provide equivalent Linux commands or configuration file edits (e.g., for Samba client settings).
- Balance the order of examples and guidance: present Azure CLI and cross-platform instructions before or alongside PowerShell, and avoid assuming Windows as the default client environment.
- Include notes or links to Linux/macOS-specific documentation for mounting, securing, and optimizing SMB shares, especially for advanced features.
- Explicitly state any limitations or differences for Linux/macOS SMB clients in relevant sections (e.g., support for encryption algorithms, Multichannel, or Kerberos).