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 326-350 of 1657 flagged pages
Storage
Understand Azure File Sync Cloud Tiering
.../storage/file-sync/file-sync-cloud-tiering-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation page is heavily oriented toward Windows environments. It references Windows Server features (such as NTFS, StorageSync.sys, and Data Deduplication), uses Windows terminology (Event Viewer, reparse points, NTFS attributes), and provides instructions and examples only for Windows tools (e.g., PowerShell cmdlets like Invoke-StorageSyncFileRecall). There are no Linux equivalents, examples, or mentions of how cloud tiering works on non-Windows platforms, nor any cross-platform guidance.
Recommendations
- Add explicit statements about platform support, clarifying whether Azure File Sync cloud tiering is available or not on Linux and other OSes.
- If Linux support exists, provide equivalent examples and instructions for Linux environments, including relevant commands, file system details, and troubleshooting steps.
- Include Linux-specific terminology and tools (e.g., ext4/XFS file systems, Linux event logging, relevant CLI commands) where appropriate.
- If Azure File Sync is Windows-only, make this clear at the beginning of the documentation to set expectations for cross-platform users.
- Avoid using Windows-centric terms (NTFS, Event Viewer, PowerShell) exclusively; provide cross-platform context or alternatives where possible.
Create Pull Request
Storage
Best practices for disaster recovery with Azure File Sync
...ile-sync/file-sync-disaster-recovery-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page for Azure File Sync disaster recovery demonstrates a Windows bias. It exclusively references Windows-centric tools and patterns, such as Volume Shadow Copy Service (VSS), the Previous Versions tab, DFS-N, and PowerShell, without mentioning Linux equivalents or providing Linux-specific guidance. There are no examples or instructions for Linux servers, nor is there discussion of cross-platform considerations, despite Azure File Sync supporting SMB and potentially being used in mixed environments.
Recommendations
- Add explicit guidance for disaster recovery scenarios involving Linux servers, including supported backup and restore strategies.
- Provide Linux-specific examples for backup, restore, and failover operations, such as using rsync, cron, or native Linux snapshot tools (e.g., LVM snapshots).
- Mention cross-platform limitations and considerations, clarifying which features (e.g., VSS, Previous Versions tab) are Windows-only and suggesting Linux alternatives.
- Include PowerShell alternatives for Linux, such as Azure CLI or REST API commands, for enabling features and performing restores.
- Reorder sections or add parallel Linux guidance so that Windows and Linux are treated equally, rather than Windows-first.
Storage
Install the Azure File Sync Agent on Arc-enabled Windows Servers
...main/articles/storage/file-sync/file-sync-extension.md
High Priority
View Details →
Detected Bias Types
Windows Only
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is exclusively focused on installing and managing the Azure File Sync agent extension for Arc-enabled Windows Servers. It explicitly states that Linux servers are not supported, and all examples, settings, and instructions are tailored for Windows environments (e.g., Windows file paths, Windows services, Windows-specific tools like PowerShell). There are no Linux equivalents, examples, or alternative guidance provided, and Windows terminology and tools are used throughout.
Recommendations
- Clearly state Linux is not supported at the top of the article and link to alternatives for Linux file sync if available.
- Provide a comparison table or section outlining file sync options for Linux Arc-enabled servers, even if Azure File Sync is not supported.
- If future support for Linux is planned, add a note about roadmap or preview features.
- Where possible, use more platform-neutral language in introductory sections and clarify platform-specific limitations.
- Add links to documentation for Linux file sharing/sync solutions in Azure (e.g., NFS, SMB on Linux, third-party sync tools) to help Linux users find alternatives.
Storage
How to manage Azure File Sync tiered files
...rage/file-sync/file-sync-how-to-manage-tiered-files.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All examples and instructions use Windows-specific tools (PowerShell, Command Prompt, reg.exe, fsutil), Windows registry paths, and NTFS file attributes. There is no mention of Linux support, nor are any Linux equivalents or cross-platform alternatives provided. The documentation assumes the reader is using Windows Server and does not address how (or if) Azure File Sync tiering features can be managed from Linux systems.
Recommendations
- Clarify platform support: Explicitly state whether Azure File Sync tiering features are available on Linux, and if not, mention this limitation up front.
- Provide Linux parity: If Linux support exists, add equivalent examples using Linux tools (e.g., shell commands, file attribute checks, service management) and paths.
- Cross-platform guidance: Where features are Windows-only (such as registry settings or NTFS attributes), explain why and suggest alternatives or workarounds for Linux users.
- Tool alternatives: If PowerShell cmdlets are required, mention if they can be run from Azure Cloud Shell or via remote management, and whether any REST API or CLI alternatives exist for Linux users.
- Documentation structure: Consider organizing examples by platform, with clear headings for Windows and Linux, to help users quickly find relevant instructions.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias. Azure File Sync is described as a solution that transforms Windows Server into a cache for Azure Files, and all on-premises monitoring instructions reference Windows Server tools such as Event Viewer and Performance Monitor. There are no examples or guidance for Linux systems, nor any mention of Linux-compatible monitoring methods or tools. Windows terminology and tools are used exclusively when discussing local server monitoring, and protocols are described as 'available on Windows Server' without reference to Linux equivalents.
Recommendations
- Explicitly state Azure File Sync's platform requirements and whether Linux servers are supported or not. If Linux is unsupported, clarify this early in the documentation.
- If Linux support exists or is planned, provide equivalent monitoring instructions for Linux systems, including how to access logs, metrics, and performance counters using Linux-native tools (e.g., journalctl, sysstat, etc.).
- Include examples or references for monitoring Azure File Sync from Linux-based environments, such as using Azure Monitor APIs, CLI, or cross-platform scripting.
- When listing protocols (SMB, NFS, FTPS), clarify their availability and support on both Windows and Linux servers.
- Avoid exclusive use of Windows terminology (Event Viewer, Perfmon.exe) without mentioning cross-platform or Linux alternatives where applicable.
Storage
Azure File Sync networking considerations
...les/storage/file-sync/file-sync-networking-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All examples and instructions are focused on Windows Server environments, with repeated references to Windows file servers and exclusive use of PowerShell cmdlets for configuration tasks. There are no Linux-specific examples, nor is there mention of Linux support or equivalent Linux tools for Azure File Sync. The documentation assumes the reader is operating in a Windows ecosystem and does not address cross-platform scenarios.
Recommendations
- Explicitly state platform support for Azure File Sync, clarifying whether Linux servers are supported or not.
- If Linux is supported, provide equivalent instructions and examples for Linux environments, including relevant tools (e.g., shell commands, configuration files, Linux networking/firewall settings).
- Include Linux-specific guidance for proxy configuration, firewall rules, and DNS setup, using common Linux utilities (e.g., curl, iptables, systemd-resolved, etc.).
- When demonstrating DNS resolution, provide both PowerShell and Linux command examples (e.g., dig, nslookup).
- If Azure File Sync is Windows-only, add a prominent note at the beginning of the documentation clarifying this limitation, and suggest alternatives for Linux users (such as mounting Azure Files directly via SMB/NFS).
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation for Azure File Sync is heavily Windows-centric. It exclusively references Windows Server as the supported platform, with no mention of Linux or cross-platform support. All operational instructions, troubleshooting, and agent installation steps are tailored for Windows Server versions. Examples and tools referenced (such as PowerShell cmdlets, Robocopy, .NET Framework, and Windows Update) are Windows-specific, with no Linux alternatives or parity guidance. There are no examples or instructions for Linux-based file servers, nor any mention of Linux compatibility, limitations, or migration paths.
Recommendations
- Clearly state platform limitations at the top of the documentation, including lack of Linux support if applicable.
- If Linux support is planned or available, add equivalent instructions, examples, and troubleshooting steps for Linux environments.
- Reference cross-platform tools (such as Azure CLI, REST API) where possible, and provide examples for both Windows and Linux.
- If only Windows is supported, provide rationale and guidance for organizations with mixed environments, including migration or integration strategies.
- Consider adding a section comparing Azure File Sync to other Azure file solutions that support Linux, to help users choose the right service.
Storage
Replace a drive on an Azure File Sync server
.../articles/storage/file-sync/file-sync-replace-drive.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows environments. All examples use Windows-specific tools (Robocopy), Windows command line syntax, and reference Windows services (Storage Sync Agent Service). There are no Linux equivalents or instructions for performing these steps on Linux servers, nor is there any mention of cross-platform alternatives. The documentation assumes the server endpoints are hosted on Windows Server or Windows VMs, with no consideration for Linux-based Azure File Sync scenarios.
Recommendations
- Provide equivalent instructions and examples for Linux environments, including supported file copy tools (e.g., rsync, cp, or smbclient) and relevant command syntax.
- Clarify whether Azure File Sync supports Linux servers, and if not, explicitly state this limitation at the beginning of the documentation.
- If Linux is supported, include steps for managing SMB access, endpoint creation/deletion, and service management on Linux.
- Mention cross-platform tools or approaches where possible, and avoid assuming all users are on Windows.
- If Robocopy is required, explain why and suggest alternatives for non-Windows users.
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 page exhibits a Windows bias in several ways: Azure File Sync is described as a solution for 'Windows file servers' only, with no mention of Linux support or alternatives. PowerShell is heavily featured, with detailed scripts and output examples, while Linux-specific tools or shell commands are either absent or only briefly mentioned (e.g., nslookup). In some cases, only PowerShell instructions are provided (such as disabling the Storage Sync Service public endpoint), and the CLI tab explicitly states that the functionality is not available in Azure CLI. Output examples are shown for Windows but not for Linux/macOS, and there is no discussion of Linux-based file server scenarios or parity.
Recommendations
- Clarify whether Azure File Sync supports Linux file servers, and if not, mention alternatives for Linux environments.
- Provide equivalent Linux shell commands and output examples alongside PowerShell instructions, especially for DNS and network validation steps.
- Where functionality is only available in PowerShell, note this limitation and suggest workarounds or roadmap plans for CLI/Linux parity.
- Include references to Linux-based file sharing solutions or Azure Files usage from Linux, if relevant.
- Ensure that examples and screenshots are not exclusively Windows-centric; add Linux/macOS variants where possible.
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 for Azure File Sync is heavily focused on Windows Server environments, with all deployment, management, and troubleshooting examples and requirements referencing Windows Server and Windows-specific tools (e.g., PowerShell cmdlets, NTFS, BitLocker, DFS, Data Deduplication). There are no Linux or macOS examples for Azure File Sync, and the service itself is described as only compatible with Windows Server. Even when discussing general Azure Files usage, Windows tools and patterns are mentioned first or exclusively. Linux is only referenced in passing for direct SMB mounting, not for sync scenarios.
Recommendations
- Clearly state at the beginning that Azure File Sync is a Windows Server-only solution, and provide guidance for Linux users on alternative approaches for file synchronization with Azure Files.
- Where possible, include parity information for Linux and macOS, such as how to mount Azure file shares directly, and link to relevant documentation.
- Add a comparison table or section outlining differences and limitations between Windows, Linux, and macOS clients for Azure Files, especially regarding sync capabilities.
- For PowerShell-heavy sections, provide CLI or REST API equivalents where applicable, or clarify that these tools are Windows-only.
- Mention third-party or open-source sync solutions for Linux, if any exist, and clarify their support status.
- Ensure that references to file system features (NTFS, ReFS, etc.) are contextualized for Windows, and provide notes for Linux file systems (e.g., ext4, XFS) regarding compatibility or alternatives.
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 First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell-only examples for resource management tasks, referencing Windows-centric tools and patterns (such as PowerShell and service principals), and omitting equivalent Linux or cross-platform CLI instructions. The guidance assumes users are familiar with Windows tooling and does not offer parity for Linux administrators or those using Azure CLI or REST APIs.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, especially for managed identity and resource moves.
- Include instructions for performing resource moves and RBAC assignments using REST API or ARM templates, which are platform-agnostic.
- Explicitly mention that all portal-based steps are cross-platform, but clarify any steps that may require Windows-specific tooling.
- Add troubleshooting and operational notes relevant to Linux-based Azure File Sync agents or hybrid scenarios.
- Ensure terminology and screenshots do not assume a Windows environment unless strictly necessary.
Storage
Create an Azure File Sync Server Endpoint
.../storage/file-sync/file-sync-server-endpoint-create.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows concepts (drive letters, RoboCopy), PowerShell cmdlets (Invoke-StorageSyncFileRecall), and Windows-specific terminology (volumes, F:\sync1). There are no examples or instructions for Linux systems, nor is there mention of Linux-compatible tools or workflows. The documentation assumes the reader is using Windows servers and omits Linux parity in both examples and tool references.
Recommendations
- Add explicit instructions and examples for Linux-based servers, including supported distributions and any prerequisites.
- Provide Linux command-line equivalents for PowerShell cmdlets, or clarify if Linux is unsupported for Azure File Sync server endpoints.
- Reference Linux file system paths (e.g., /mnt/sync1) alongside Windows paths to illustrate cross-platform applicability.
- Mention whether tools like RoboCopy have Linux equivalents (e.g., rsync) and how similar migration scenarios would be handled on Linux.
- Clarify in prerequisites and throughout the documentation whether Azure File Sync supports Linux servers, and if not, state this clearly to avoid confusion.
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 First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All operational steps reference Windows-specific tools (Task Scheduler, Event Viewer), PowerShell cmdlets/scripts, and file paths. There are no examples or guidance for Linux systems, nor mention of cross-platform alternatives. The instructions assume the use of a Windows server for Azure File Sync, with no consideration for Linux-based endpoints or management.
Recommendations
- Explicitly state platform requirements and limitations at the beginning of the documentation.
- If Azure File Sync is Windows-only, clarify this and link to alternatives for Linux users.
- If Linux support exists or is planned, provide equivalent instructions and examples for Linux environments (e.g., using cron, system logs, bash scripts).
- Where possible, offer cross-platform PowerShell Core examples or Azure CLI alternatives.
- Note file paths and tool usage differences for Linux (e.g., /var/log/ instead of Event Viewer, shell scripts instead of .ps1 files).
Storage
Manage Registered Servers with Azure File Sync
...les/storage/file-sync/file-sync-server-registration.md
High Priority
View Details →
Detected Bias Types
Windows Only
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is exclusively focused on Windows Server environments, with all instructions, prerequisites, and examples tailored to Windows. Only Windows tools (e.g., Server Manager, PowerShell, netsh, Windows-specific paths) are mentioned, and there is no mention of Linux support, equivalents, or examples. All command-line instructions use PowerShell or Windows command-line utilities, and the documentation assumes the use of Windows Server throughout.
Recommendations
- Explicitly state whether Azure File Sync supports Linux servers. If not, clarify this early in the documentation.
- If Linux support exists or is planned, provide equivalent instructions, prerequisites, and examples for Linux environments (e.g., using Bash, Azure CLI, Linux file paths).
- Where PowerShell is used, offer Azure CLI or REST API alternatives that are cross-platform.
- Avoid Windows-specific terminology and tools in general sections, or provide Linux alternatives alongside them.
- Include a section on interoperability or limitations for non-Windows platforms, if applicable.
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 presenting PowerShell examples before Azure CLI, referencing Windows-specific troubleshooting tabs, and omitting Linux-specific usage patterns or examples (e.g., Bash, shell scripting, or Linux mounting scenarios). The guidance and screenshots focus on generic Azure portal usage, but command-line examples and troubleshooting links prioritize Windows tools and workflows.
Recommendations
- Add Linux/Bash examples alongside PowerShell, especially for metric queries and automation.
- Reference Linux mounting and monitoring scenarios (e.g., using NFS, SMB on Linux, or Linux client performance).
- Ensure troubleshooting links and examples include Linux tabs or parity with Windows guidance.
- Mention cross-platform tools (e.g., Python SDK, REST API) and provide sample code for Linux environments.
- Clarify that Azure CLI is cross-platform and provide usage notes for both Windows and Linux shells.
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, requires installation of the Azure File Sync agent (which is Windows-only), and provides a Robocopy command (a Windows tool) for data recovery. There are no Linux equivalents or examples, nor any mention of Linux support or alternative procedures.
Recommendations
- Clarify whether Azure File Sync supports Linux servers. If not, explicitly state this limitation early in the documentation.
- If Linux support exists or is planned, provide equivalent instructions and examples for Linux environments, including agent installation, registration, and data copy procedures (e.g., using rsync instead of Robocopy).
- When mentioning tools or commands, offer cross-platform alternatives or note platform-specific requirements.
- Consider restructuring the documentation to address both Windows and Linux users, or create separate guides for each platform.
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 page exhibits a strong Windows bias. All migration instructions and tooling references are centered around Windows environments, such as Windows Server, PowerShell cmdlets, and Robocopy. There is no mention of Linux-based alternatives, nor are there examples or guidance for performing migrations from Linux clients or using cross-platform tools. Windows terminology and patterns (e.g., drive letters, Windows VMs, Storage Migration Service) are used exclusively and presented as the default or only option.
Recommendations
- Add equivalent Linux migration instructions, including examples using SMB mounting and file copy tools such as rsync or cp.
- Mention and demonstrate how to mount Azure file shares on Linux (using cifs-utils or smbclient).
- Provide PowerShell and Bash/CLI examples side-by-side for key steps, such as recalling tiered files and copying data.
- Reference cross-platform tools (e.g., azcopy, rsync) for file migration, and explain their usage in Azure File Sync scenarios.
- Clarify any Azure File Sync agent support or limitations for Linux, and provide guidance for hybrid or Linux-only environments.
- Avoid assuming Windows-only environments by using neutral terminology (e.g., 'local server' instead of 'Windows Server', 'mount point' instead of drive letters).
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 PowerShell and Windows-centric tools (AzCopy, Storage Explorer) in its examples and explanations. PowerShell is featured prominently with detailed step-by-step instructions, while Linux-native tools and workflows are not mentioned or exemplified. The CLI section is present, but examples are generic and do not address Linux-specific usage or considerations. There is no mention of Linux file system integration, shell scripting, or cross-platform nuances, and all code samples and tool references assume a Windows environment.
Recommendations
- Add explicit Linux shell (bash) examples for REST API calls, using curl or wget, to demonstrate OAuth authentication and file operations.
- Include instructions for using Azure CLI on Linux, highlighting any differences in authentication, file path handling, or permissions.
- Reference Linux-native tools (e.g., smbclient, mount.cifs with Kerberos/OAuth, or third-party REST clients) where applicable.
- Provide parity in step-by-step guides for Linux users, such as installing Azure CLI or SDKs on Linux distributions.
- Mention cross-platform considerations for file path formats, environment variables, and access control differences.
- List and describe any limitations or caveats for Linux environments, such as support for OAuth in SMB mounts or REST API tooling.
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 listing PowerShell as a primary method for command-line operations, often before Azure CLI, and never mentioning Linux-specific shell usage or examples. All command-line examples are either PowerShell or Azure CLI, with no explicit Bash, Linux shell, or cross-platform scripting guidance. There are no references to Linux tools, nor any notes about platform differences or considerations for Linux users.
Recommendations
- Explicitly mention that Azure CLI commands can be run in Bash or other Linux shells, and provide example syntax for Bash (e.g., using export for environment variables, handling line continuations, etc.).
- Add notes or sections clarifying platform differences, such as how to install and use Azure CLI on Linux, and any differences in authentication or environment setup.
- Include Linux/Bash-specific examples alongside PowerShell, especially for common tasks like setting variables, piping output, or using tools like jq for JSON parsing.
- Avoid listing PowerShell before Azure CLI when presenting cross-platform options, or alternate the order to avoid implicit prioritization.
- Reference Linux-native tools where appropriate (e.g., AzCopy for Linux, or mention that manual migration can use rsync or other Linux file copy tools).
- Add a brief statement at the start of command-line sections indicating that all examples are cross-platform unless otherwise noted, and provide links to platform-specific installation guides.
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 a Windows bias by prioritizing Windows-centric tools and workflows. Azure PowerShell is featured as a primary method for backup and restore, and Azure File Sync (a Windows Server feature) is highlighted for hybrid cloud backups. There is no mention of Linux-specific tools or workflows, and Windows technologies are presented before cross-platform alternatives like Azure CLI or REST API.
Recommendations
- Add explicit Linux-focused examples and workflows, such as using Azure CLI from Linux, mounting Azure Files via NFS, and backup/restore scenarios for Linux clients.
- Include parity for hybrid backup solutions, e.g., guidance for rsync or other Linux-native tools to synchronize with Azure Files.
- Ensure that cross-platform tools (Azure CLI, REST API) are presented before or alongside Windows-specific tools like PowerShell.
- Mention limitations or considerations for Linux users, such as SMB/NFS support and integration with Linux backup utilities.
- Provide sample scripts and step-by-step instructions for Linux environments, not just Windows/PowerShell.
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 AD, and Windows DNS. All examples and instructions use Windows tools (Server Manager, PowerShell, DFS Management console, Windows DNS), with no mention of Linux equivalents or cross-platform alternatives. There are no Linux or non-Windows examples, and the documentation assumes a Windows-based infrastructure throughout.
Recommendations
- Clarify early that DFS Namespaces is a Windows Server feature and note any cross-platform limitations.
- If possible, mention or link to alternative solutions for namespace virtualization or SMB share management on Linux (e.g., autofs, Samba DFS, or other open-source tools).
- Provide guidance for accessing Azure Files SMB shares from Linux clients, including mounting instructions and authentication considerations.
- Discuss DNS aliasing and management using Linux-based DNS servers (e.g., BIND), with example commands.
- Explicitly state that PowerShell and Windows tools are required for DFS-N management, and suggest any available REST APIs or cross-platform management options if they exist.
- Add a section comparing DFS-N with Linux-based approaches to namespace management, highlighting differences and interoperability considerations.
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 exhibits Windows bias by consistently mentioning Azure PowerShell before Azure CLI and other cross-platform tools when describing how to query properties or initiate failover. There are no explicit Linux or macOS-specific examples, nor are Linux tools or workflows (such as shell scripts or mounting/unmounting via Linux commands) discussed. The documentation references SMB (a Windows-centric protocol) more frequently than NFS, and Azure File Sync (a Windows-only feature) is highlighted without Linux alternatives.
Recommendations
- Provide Linux-specific examples for key operations, such as querying the Last Sync Time property and initiating failover, using Azure CLI and REST API.
- Explicitly mention and demonstrate how to mount/unmount Azure Files shares on Linux (e.g., using mount.cifs or mount.nfs), especially in failover scenarios.
- Balance protocol coverage by including more NFS use cases and examples, not just SMB.
- When listing tools (PowerShell, CLI, portal), alternate the order or provide parallel examples for both Windows and Linux environments.
- Reference Linux disaster recovery best practices and link to relevant documentation for cross-platform parity.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by prioritizing Windows terminology, tools, and examples throughout. Windows and PowerShell are referenced first and most frequently, with detailed PowerShell scripts and registry instructions for enabling features on Windows versions. There are no equivalent Linux-specific configuration or troubleshooting examples, and references to client-side configuration (such as enabling encryption ciphers) are exclusively for Windows/PowerShell. The limitations section also references Windows/NTFS features without mentioning Linux or Samba-specific considerations.
Recommendations
- Add Linux-specific examples for client configuration, such as how to enable or verify SMB Multichannel and encryption settings on Linux clients (e.g., using smb.conf or mount options).
- Include troubleshooting steps or notes for common Linux SMB client issues, such as required kernel versions or cifs-utils options.
- When referencing PowerShell or Windows registry changes, provide parallel instructions for Linux (or explicitly state if not applicable).
- Balance the order of examples and explanations so that Linux and macOS are not always listed after Windows, and ensure that Linux tools (like mount.cifs, smbclient, or relevant CLI commands) are mentioned where appropriate.
- In the limitations section, mention any Linux/Samba-specific limitations or differences in feature support.
- Where client-side configuration is required (e.g., for encryption ciphers), provide Linux equivalents or note if the feature is not available on Linux.
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 for Azure Files and Azure File Sync exhibits a Windows bias in several ways. Windows terminology, features, and tools (such as PowerShell, Windows Server, and NTFS) are mentioned more frequently and often before their Linux equivalents. Examples and instructions for management and configuration (e.g., Azure File Sync agent installation, SMB protocol features) are primarily focused on Windows environments, with limited or no Linux-specific guidance. Windows tools like PowerShell are referenced repeatedly, while Linux alternatives are less visible or absent. Some features (e.g., Azure File Sync agent via Azure Arc) are described as Windows-only, and there is a lack of parity in example commands or operational guidance for Linux users.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows ones, especially for management tasks, agent installation, and file share access.
- Mention Linux tools (such as shell commands, systemd services, or native Linux utilities) wherever PowerShell or Windows tools are referenced.
- Ensure parity in feature descriptions, making it clear when features are available for both Windows and Linux, and explicitly state any limitations.
- Include guidance for Linux administrators in sections that currently focus on Windows, such as Azure File Sync agent deployment, monitoring, and troubleshooting.
- Balance terminology and examples so that both Windows and Linux users can easily find relevant information without feeling secondary.
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, FSLogix), and by omitting Linux-specific examples or guidance. While Linux is mentioned as a supported client, there are no Linux-specific instructions, diagrams, or access patterns described. Windows terminology and workflows dominate the explanations, and links to further reading are Windows-centric.
Recommendations
- Include Linux-specific examples and workflows for enabling and using identity-based authentication with Azure Files over SMB, such as configuration steps for Linux clients.
- Provide parity in diagrams and instructions, showing how Linux and MacOS clients interact with Azure Files identity-based authentication.
- Reference Linux tools and authentication mechanisms (e.g., Samba, Kerberos configuration on Linux) alongside Windows tools.
- Add links to Linux-focused documentation (e.g., the referenced 'storage-files-identity-auth-linux-kerberos-enable.md') in relevant sections, and summarize their content.
- Explicitly mention any differences or additional requirements for Linux clients, such as package dependencies, configuration files, or troubleshooting steps.