Azure Netapp Files
252
Total Pages
149
Linux-Friendly Pages
103
Pages with Bias
40.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
896 issues found
Showing 551-575 of 896 flagged pages
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-attached-file-permissions.md
...zure-netapp-files/network-attached-file-permissions.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by describing Windows SMB inheritance controls first and in more detail, including a screenshot of the Windows interface, while Linux/NFS equivalents are described more abstractly and without visual aids or command examples. There are no Linux (e.g., chmod, setfacl) command-line examples or screenshots, and the explanation of NFS inheritance is less actionable.
Recommendations
- Provide equivalent Linux/NFS command-line examples (e.g., using chmod, setfacl, or nfs4_setfacl) for managing file permissions and inheritance.
- Include screenshots or step-by-step instructions for configuring NFSv4.1 ACL inheritance, similar to the Windows example.
- Present SMB and NFS instructions in parallel structure, ensuring neither platform is consistently prioritized.
- Expand the explanation of NFS permission inheritance with practical examples and common Linux administration patterns.
Create Pull Request
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-attached-storage-permissions.md
...e-netapp-files/network-attached-storage-permissions.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the SMB section by exclusively referencing Windows tools (e.g., MMC console, Windows Explorer, 'net view') for managing and viewing SMB share permissions. There are no examples or instructions for managing SMB shares or permissions from Linux or macOS clients. The documentation also describes SMB share enumeration and access scenarios solely from a Windows perspective, with screenshots and workflows based on Windows environments. NFS sections are platform-neutral, but SMB sections lack Linux parity.
Recommendations
- Include instructions or examples for managing SMB share permissions from Linux clients, such as using smbclient, mount.cifs, or setfacl.
- Provide screenshots or command-line examples for accessing SMB shares and viewing permissions from Linux or macOS systems.
- Mention Linux/macOS tools (e.g., Nautilus, Dolphin, Finder, smbclient) alongside Windows tools when describing how to browse or mount SMB shares.
- Clarify that SMB shares can be accessed and managed from non-Windows clients and provide relevant guidance.
- Balance the order of presentation so that Linux and Windows tools are introduced together, or alternate which platform is mentioned first.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-attached-storage-protocols.md
...ure-netapp-files/network-attached-storage-protocols.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation generally presents Windows/SMB concepts and tools before or with more detail than Linux/NFS equivalents. Windows terminology (e.g., NTFS, SID, NTLM) is explained in depth, while Linux/UNIX-specific tools and configuration examples are minimal or absent. Official support is emphasized for Windows and macOS SMB clients, but Linux SMB (Samba) is mentioned as unsupported, with no guidance or examples. There are no Linux command-line examples for NFS or SMB usage, and Windows-centric patterns (Active Directory, NTFS ACLs) are foregrounded.
Recommendations
- Provide Linux command-line examples for both NFS and SMB (e.g., show how to mount NFS and SMB shares from Linux clients, including required packages and configuration).
- Include parity in tool references: if referencing Windows tools (e.g., NTFS, SID, NTLM), also reference and explain Linux/UNIX equivalents (e.g., POSIX ACLs, UID/GID, Kerberos setup on Linux).
- Offer troubleshooting tips and configuration steps for Linux clients (e.g., Samba configuration for SMB, idmapd.conf for NFSv4, LDAP integration).
- Clarify the support status for Linux SMB clients and provide best-effort guidance or links to community resources.
- Balance the order of presentation so that Linux/NFS and Windows/SMB are treated equally, or alternate which is presented first in each section.
- Add explicit Linux-focused 'Next steps' or quickstart links, similar to those for Windows/SMB.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-file-system-group-memberships.md
...-netapp-files/network-file-system-group-memberships.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Microsoft Active Directory as the LDAP implementation, using Windows-centric terminology and tools (such as ldp.exe), and providing only Windows-based examples and screenshots. There are no examples or instructions for equivalent Linux/OpenLDAP environments, nor are Linux tools or patterns mentioned. The documentation assumes a Windows/AD context for LDAP group management, which may not be applicable to organizations using Linux-based LDAP servers.
Recommendations
- Include equivalent examples and screenshots for Linux/OpenLDAP environments, such as using ldapsearch or other standard Linux LDAP tools.
- Mention and explain how supplemental groups and GID management work in non-Active Directory LDAP servers.
- Provide instructions or references for modifying group membership and LDAP attributes in Linux/OpenLDAP, not just in Windows/AD.
- Balance the order of presentation so that Linux/OpenLDAP approaches are described alongside or before Windows/AD approaches where possible.
- Reference Linux documentation and tools (e.g., openldap, nslcd, sssd) in addition to Microsoft tools.
- Clarify when a feature or limitation is specific to Active Directory versus generic to LDAP or NFS.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/performance-azure-vmware-solution-datastore.md
...p-files/performance-azure-vmware-solution-datastore.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools and concepts (such as NTFS, volume shadow copies, and Windows Server striped volumes) are mentioned alongside or before Linux equivalents. In the 'Next steps' section, Windows-specific guidance ('Creating striped volumes in Windows Server') is listed before Linux-specific content, and there is no direct example or link for Linux disk striping (e.g., using LVM or mdadm). While Linux is referenced (e.g., Ubuntu VMs, XFS, LVM), explicit Linux command examples or links to Linux disk striping documentation are missing, and Windows terminology appears more frequently or is prioritized.
Recommendations
- Add explicit Linux disk striping examples and documentation links (e.g., guides for LVM or mdadm) in the 'Next steps' section, ideally placed before or alongside Windows equivalents.
- When discussing file system freeze/snapshot operations, provide equal detail for Linux (e.g., xfs_freeze, LVM snapshots) as for Windows (NTFS, VSS).
- Ensure that Linux tools and patterns are mentioned with equal prominence and detail as Windows tools throughout the document.
- Include example commands or configuration snippets for both Linux and Windows where relevant (e.g., how to stripe disks, monitor performance, or perform snapshots).
- Review the order of presenting Windows and Linux content to avoid consistently listing Windows first, which can reinforce perceived bias.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/performance-oracle-multiple-volumes.md
...re-netapp-files/performance-oracle-multiple-volumes.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is largely platform-neutral in its narrative, but there are subtle biases favoring Windows/Azure-native paradigms. While the article focuses on Oracle on Azure NetApp Files (which is inherently cross-platform), it assumes familiarity with Azure-specific tooling and does not provide Linux-specific or cross-platform command-line examples except in the context of network interface validation. There is a lack of explicit Linux administration examples (e.g., for mounting, automation, or troubleshooting), and Azure/Windows-centric tools and patterns are mentioned without always offering Linux alternatives or parity.
Recommendations
- Provide explicit Linux and cross-platform examples for common administrative tasks (e.g., mounting NFS volumes, validating network performance, troubleshooting).
- When referencing Azure-native tools or patterns, also mention or link to equivalent Linux-native tools or open-source alternatives where applicable.
- Ensure that automation and scripting examples (e.g., for deployment, configuration, validation) are shown for both PowerShell and Bash/shell, or clarify when Bash/Ansible is used.
- Highlight any differences or special considerations for Linux environments, especially in areas like network configuration, performance tuning, and monitoring.
- Include troubleshooting steps and diagnostic commands for both Windows and Linux environments to ensure parity.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/sever-message-block-support.md
...cles/azure-netapp-files/sever-message-block-support.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Windows Heavy Context
Summary
The documentation page demonstrates a Windows-centric bias in its discussion of SMB support in Azure NetApp Files. The content and examples are almost exclusively focused on Windows environments, tools, and semantics (e.g., NTFS, Active Directory, Hyper-V, MS SQL Server, Windows client behaviors), with little to no mention of Linux or macOS SMB client usage, configuration, or differences. Linux-specific SMB client considerations, tools, or configuration steps are missing, and Windows terminology and tools are referenced first or exclusively throughout.
Recommendations
- Add examples and explanations for configuring and accessing Azure NetApp Files SMB shares from Linux and macOS clients, including common tools (e.g., smbclient, mount.cifs) and authentication considerations.
- Include a section comparing Windows and Linux SMB client behaviors, especially for features like file permissions, symbolic links, and delete semantics.
- Mention Linux/UNIX equivalents when referencing Windows tools or features (e.g., explain how 'share permissions' or 'offline files' map to Linux clients, or note differences).
- Provide guidance on troubleshooting SMB access from non-Windows clients, including common error messages and solutions.
- Reference Linux documentation or man pages where appropriate (e.g., for smb.conf, mount.cifs, or Kerberos configuration on Linux).
- Clarify when features or limitations are specific to Windows clients versus cross-platform SMB clients.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/snapshots-introduction.md
.../articles/azure-netapp-files/snapshots-introduction.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. In sections describing how to create and manage snapshots, Windows tools (PowerShell) are mentioned explicitly and often listed before or alongside cross-platform tools, but there is no mention of Linux/Unix-specific tools or command-line examples (such as Bash scripts or Linux CLI usage). There are no Linux/Unix-specific usage patterns or examples, and the scripting example provided is linked to a SQL Server (a Windows-centric workload) scenario. The documentation does not provide parity in examples or tool references for Linux users.
Recommendations
- Include explicit Linux/Unix command-line examples (e.g., Bash scripts using Azure CLI) for creating, managing, and restoring snapshots.
- When listing tools, alternate or randomize the order of Azure CLI and PowerShell, or list Azure CLI first as it is cross-platform.
- Provide example scripts for both PowerShell and Bash to demonstrate parity.
- Reference Linux/Unix workloads and use cases (e.g., restoring files from NFS volumes using Linux commands) alongside Windows/SMB examples.
- Ensure that links to scripting examples include both Windows and Linux scenarios.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/solutions-benefits-azure-netapp-files-sql-server.md
...es/solutions-benefits-azure-netapp-files-sql-server.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page exclusively discusses SQL Server deployment scenarios, performance, and benchmarking in the context of Windows environments. There are no references to Linux-based SQL Server deployments, Linux tools, or cross-platform considerations. All examples, performance metrics, and tooling (such as SSB and perfmon) are implicitly or explicitly Windows-centric. The 'Next Steps' section also only references SMB (a Windows-native protocol), with no mention of NFS or Linux-based workflows.
Recommendations
- Include explicit mention of SQL Server on Linux as a supported scenario for Azure NetApp Files, if applicable.
- Provide performance and cost analysis examples for SQL Server running on Linux VMs, including relevant VM series and storage configurations.
- Reference Linux-native benchmarking and monitoring tools (e.g., iostat, sysstat, sar) alongside or instead of Windows tools like perfmon.
- Add guidance or links for creating NFS volumes and connecting them to Linux-based SQL Server deployments.
- Ensure that all diagrams, benchmarks, and configuration examples include both Windows and Linux perspectives where possible.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/tools-reference.md
...ob/main/articles/azure-netapp-files/tools-reference.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation lists a variety of tools for Azure NetApp Files, but the only automation example provided is ANFHealthCheck, which is explicitly described as a PowerShell runbook. There are no equivalent Linux/bash examples or mentions of cross-platform automation tools. This suggests a bias toward Windows and PowerShell environments, with a lack of parity for Linux users.
Recommendations
- Provide equivalent Linux/bash or cross-platform automation examples for tools like ANFHealthCheck.
- Mention or link to Linux-compatible alternatives or scripts where PowerShell is referenced.
- Explicitly state platform compatibility for each tool, clarifying if they are Windows-only, Linux-only, or cross-platform.
- Add examples or documentation for using these tools in Linux environments, especially for monitoring and automation tasks.
- Encourage contributions or community solutions for Linux users if official tools are not yet available.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/understand-guidelines-active-directory-domain-service-site.md
...rstand-guidelines-active-directory-domain-service-site.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows-centric bias. It consistently references Windows tools (such as 'Active Directory Sites and Services'), provides step-by-step instructions and screenshots for Windows GUI utilities, and describes AD DS concepts and operations primarily from a Windows Server perspective. While Linux client authentication via Kerberos is mentioned, there are no Linux-specific configuration examples, tools, or screenshots. The documentation assumes familiarity with Windows administration and omits equivalent Linux-based approaches for managing AD DS integration or site topology.
Recommendations
- Provide Linux-based examples for AD DS integration, such as using Samba tools (e.g., samba-tool, net ads) for site discovery and domain controller management.
- Include command-line examples for querying DNS SRV records and validating AD DS connectivity using Linux utilities (e.g., dig, host, kinit, ldapsearch).
- Offer guidance or references for managing AD DS from Linux environments, such as using RSAT alternatives or open-source LDAP management tools.
- Balance screenshots and step-by-step instructions by including both Windows and Linux workflows where applicable.
- Clarify that while the Windows GUI tools are commonly used, equivalent operations can be performed from Linux systems, and provide links or instructions for those workflows.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/troubleshoot-volumes.md
...in/articles/azure-netapp-files/troubleshoot-volumes.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: troubleshooting steps and error messages are predominantly focused on SMB and Active Directory scenarios, which are Windows-centric. PowerShell commands are provided for AD configuration, but equivalent Linux/Unix commands or tools are not mentioned. In dual-protocol and NFS sections, while some Linux-specific instructions are present (such as using kinit and systemctl), Windows/AD/SMB issues are discussed first and in greater detail. There is a lack of parity in providing Linux/Unix troubleshooting examples, especially for NFS-only or LDAP-only environments.
Recommendations
- Provide Linux/Unix command-line examples (e.g., using ldapsearch, klist, systemctl, or nfsstat) alongside or before Windows/PowerShell examples.
- Include troubleshooting steps for common Linux/Unix NFS and LDAP scenarios, such as checking mount options, verifying Kerberos tickets, or inspecting /etc/krb5.conf and /etc/hosts.
- Balance the order of presentation: do not always list Windows/SMB/AD errors and solutions before Linux/NFS/LDAP ones; consider grouping by protocol or alternating order.
- Where PowerShell or Windows AD tools are referenced, add equivalent Linux/Unix commands (e.g., samba-tool, kadmin, or openldap utilities) for managing Kerberos and LDAP.
- Expand on Linux-specific troubleshooting for dual-protocol and NFSv4.1 Kerberos volumes, including more detailed steps for debugging on Linux clients.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/understand-data-encryption.md
...icles/azure-netapp-files/understand-data-encryption.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows/SMB and Active Directory scenarios, referencing Windows-specific tools and features (such as Group Policy, registry settings, and Microsoft advisories), and omitting Linux or non-Windows client configuration examples. SMB encryption and UNC hardening are discussed in depth, with references to Windows documentation and tools, while NFS/Kerberos and LDAP sections lack equivalent Linux-focused guidance or examples. There are no Linux command-line or configuration examples, and Windows terminology and tools are mentioned first or exclusively in several sections.
Recommendations
- Add Linux/NFS client configuration examples for enabling and verifying Kerberos encryption, including relevant commands (e.g., mount options, krb5.conf settings).
- Provide equivalent Linux LDAP client configuration steps for LDAP signing and StartTLS, including example commands and configuration file snippets.
- Balance the order of presentation so that NFS/Linux and SMB/Windows scenarios are given equal prominence, or alternate which is presented first.
- Reference Linux documentation and tools (e.g., sssd, nsswitch, OpenLDAP, MIT Kerberos) alongside Windows tools like Group Policy.
- Include troubleshooting steps and best practices for both Windows and Linux environments.
- Where screenshots or packet captures are shown, provide examples from both Windows and Linux clients where applicable.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/understand-path-lengths.md
...articles/azure-netapp-files/understand-path-lengths.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows/SMB path length details, providing extensive instructions and screenshots for Windows-specific configurations (such as registry edits and Group Policy), and referencing Windows tools and error dialogs. Linux/NFS sections are present but less detailed, with fewer practical examples and no equivalent visual aids or troubleshooting steps. Linux tools are mentioned only in the context of character byte size calculation, not for path length management or troubleshooting.
Recommendations
- Add equivalent Linux/NFS troubleshooting steps and error examples, such as common error messages and how to resolve them.
- Include screenshots or terminal output for Linux/NFS path length errors, similar to the Windows dialog screenshots.
- Provide Linux-specific guidance for extending or querying path limits, such as relevant sysctl settings or mount options, if applicable.
- Balance the order of presentation: introduce NFS/Linux and SMB/Windows path limits in parallel, rather than focusing on Windows first.
- Reference Linux documentation or tools (e.g., getconf, limits.h) more prominently and provide practical usage scenarios.
- Offer parity in practical examples, such as how to map NFS mounts deeper into the directory structure to work around path length issues, similar to the SMB mapping workaround.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/understand-volume-languages.md
...cles/azure-netapp-files/understand-volume-languages.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 tools (Explorer, PowerShell, Notepad, Notepad++, chcp, Windows Terminal, PowerShell ISE) are frequently mentioned, often before or in more detail than their Linux equivalents. PowerShell and Windows-specific commands are shown for encoding conversion and file operations, while Linux examples are sometimes present but less detailed or introduced after Windows. Some sections (e.g., file encoding viewing/conversion) provide more step-by-step guidance for Windows than for Linux. The page also refers to Windows-specific behaviors (e.g., 8.3 filenames, region settings) in greater depth.
Recommendations
- Ensure Linux and macOS examples are provided alongside Windows examples for all key operations (e.g., file encoding conversion, viewing file encodings, troubleshooting).
- Present Linux and Windows examples in parallel, or alternate which OS is presented first, to avoid a 'Windows-first' impression.
- Expand Linux tool coverage: for example, show how to use Linux text editors (vim, nano, gedit) to view and change file encodings, and provide more details on Linux locale and font configuration.
- Include more screenshots or command outputs from Linux terminals, not just Windows tools.
- When referencing Windows-specific tools or settings (e.g., PowerShell ISE, chcp, region settings), provide equivalent Linux/macOS guidance (e.g., locale, iconv, file, terminal font settings).
- Explicitly mention macOS behaviors where relevant, especially since it is referenced briefly but not covered in detail.
- Balance troubleshooting advice and error message explanations for both Windows and Linux clients.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/use-dfs-n-and-dfs-root-consolidation-with-azure-netapp-files.md
...s-n-and-dfs-root-consolidation-with-azure-netapp-files.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 Server DFS Namespaces (DFS-N), Windows AD, and Windows DNS management. All examples, instructions, and tooling references are for Windows GUI or PowerShell, with no mention of Linux equivalents or cross-platform alternatives. There are no Linux-based examples, and the documentation assumes a Windows-based infrastructure throughout.
Recommendations
- Acknowledge that DFS Namespaces is a Windows Server feature and clarify if there are any cross-platform alternatives or limitations.
- If possible, mention or link to any open-source or Linux-compatible DFS-like solutions (e.g., Samba DFS, autofs, or other namespace/virtualization tools) and explain interoperability or lack thereof.
- Provide guidance for Linux clients accessing DFS-N namespaces (e.g., using smbclient, cifs-utils, or mount.cifs), including sample commands for mounting DFS-N shares from Linux.
- Clarify that management and configuration of DFS-N is only supported on Windows, but accessing shares may be possible from non-Windows clients, and provide relevant instructions.
- Where DNS changes are required, include generic instructions or note how to perform similar steps using BIND or other non-Windows DNS servers.
- Consider adding a section on limitations or considerations for mixed Windows/Linux environments, especially for organizations with heterogeneous infrastructure.
Azure Netapp Files
Azure NetApp Files for Azure Government
...b/main/articles/azure-netapp-files/azure-government.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed PowerShell instructions and a dedicated PowerShell section, but does not offer equivalent Linux/macOS shell (e.g., Bash) or cross-platform scripting examples for connecting to Azure Government. While Azure CLI is mentioned (which is cross-platform), the PowerShell section is more extensive, and no Linux-specific guidance or examples are provided. The ordering also places PowerShell after CLI, but the PowerShell section is more detailed and includes multiple command types.
Recommendations
- Add explicit Bash or Linux/macOS shell examples for connecting to Azure Government and using Azure NetApp Files, especially for authentication and endpoint configuration.
- Clarify that Azure CLI commands are cross-platform and can be used on Linux/macOS as well as Windows.
- Where PowerShell is referenced, consider providing equivalent Bash or shell script snippets, or at least link to Linux/macOS-specific guidance.
- Add a brief section or note for Linux/macOS users to ensure parity and inclusivity.
Azure Netapp Files
Create an SMB volume for Azure NetApp Files
...-netapp-files/azure-netapp-files-create-volumes-smb.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is focused on creating SMB volumes for Azure NetApp Files, which is a protocol supported by both Windows and Linux clients. However, the instructions and examples for managing and controlling access to SMB volumes are exclusively Windows-centric. Only Windows tools (MMC, Windows File Browser, Control Panel) are mentioned for setting permissions and managing shares, with no guidance for Linux or macOS users. The documentation does not provide Linux-based examples for mounting SMB volumes or managing permissions, nor does it mention Linux SMB clients or tools such as smbclient, mount.cifs, or setfacl.
Recommendations
- Add instructions or references for managing SMB share and NTFS permissions from Linux/macOS clients, such as using smbclient, mount.cifs, or setfacl.
- Include examples for mounting SMB volumes on Linux and macOS, or link to relevant documentation.
- Mention cross-platform SMB client compatibility and any caveats for non-Windows environments.
- Clarify which management tasks require Windows tools and which can be performed from Linux/macOS.
Azure Netapp Files
SMB performance best practices for Azure NetApp Files
...ure-netapp-files/azure-netapp-files-smb-performance.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily Windows-focused: all examples, commands, and monitoring instructions use Windows tools (PowerShell cmdlets, netstat, perfmon). There are no Linux/macOS client examples or equivalent instructions, despite SMB being a cross-platform protocol. Linux tools and configuration steps are not mentioned, and all performance testing and monitoring guidance assumes a Windows environment.
Recommendations
- Add equivalent Linux/macOS client examples for mounting SMB shares, verifying SMB Multichannel, and measuring performance (e.g., using smbclient, mount.cifs, or relevant Linux tools).
- Include Linux-specific commands for checking RSS/network interface capabilities (e.g., ethtool, lshw, or ip commands).
- Provide guidance for monitoring SMB performance on Linux (e.g., using iostat, nload, or atop).
- Clarify which recommendations are Windows-specific and add Linux/macOS sections where appropriate.
- If Azure NetApp Files SMB support is intended for Windows clients only, explicitly state this in the documentation.
Azure Netapp Files
Create volume replication for Azure NetApp Files
...etapp-files/cross-region-replication-create-peering.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page provides feature registration and status check examples using Azure PowerShell first and in detail, with only a brief mention of Azure CLI alternatives. This prioritizes Windows/PowerShell usage, which may create friction for Linux/macOS users who typically use Azure CLI. No Linux/macOS-specific examples or screenshots are provided, and the workflow is described primarily through Azure Portal UI and PowerShell commands.
Recommendations
- Provide full Azure CLI command examples for feature registration and status checks, not just links.
- Include CLI command syntax side-by-side with PowerShell examples where applicable.
- Add notes or screenshots showing the Azure Portal UI on non-Windows platforms if there are differences.
- Clarify that all steps can be performed using Azure CLI or Portal on any OS, and link to relevant CLI documentation.
- Consider listing CLI examples before or alongside PowerShell to avoid Windows-first impression.
Azure Netapp Files
Create a capacity pool for Elastic zone-redundant service in Azure NetApp Files
...icles/azure-netapp-files/elastic-capacity-pool-task.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation mentions PowerShell usage and provides update instructions for the Az.NetAppFiles PowerShell module before mentioning Azure CLI or REST API alternatives. PowerShell is a Windows-centric tool, and its explicit update instructions are given, while equivalent Linux/macOS CLI instructions are not. No Linux/macOS-specific examples or parity guidance are provided.
Recommendations
- Provide Azure CLI update instructions alongside PowerShell, especially since Azure CLI is cross-platform.
- Include explicit examples or references for Linux/macOS users where PowerShell is mentioned.
- Clarify that PowerShell instructions are for Windows users and offer CLI or REST API alternatives for Linux/macOS users.
- Consider listing Azure CLI before PowerShell in prerequisites to avoid Windows-first ordering.
Azure Netapp Files
Create an SMB volume for Azure NetApp Files
...-netapp-files/azure-netapp-files-create-volumes-smb.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation is focused on creating and managing SMB volumes in Azure NetApp Files, which is a protocol supported by both Windows and Linux. However, the instructions and examples for managing access and permissions are exclusively Windows-centric, referencing Windows tools (MMC, Windows SMB client, Windows File Browser) and omitting Linux methods for mounting and managing SMB shares. Windows terminology and screenshots are used throughout, and Linux alternatives are not mentioned or provided.
Recommendations
- Add examples and instructions for mounting SMB volumes from Linux clients (e.g., using the mount.cifs command).
- Include guidance on managing SMB share and NTFS permissions from Linux, such as using smbclient, setfacl, or other relevant tools.
- Provide parity in screenshots and step-by-step instructions for Linux environments where applicable.
- Clarify which steps are Windows-only and which are cross-platform, and link to Linux-specific documentation where relevant.
Azure Netapp Files
SMB performance best practices for Azure NetApp Files
...ure-netapp-files/azure-netapp-files-smb-performance.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily Windows-centric, with all examples, commands, and monitoring instructions using Windows tools (PowerShell cmdlets, Performance Monitor, etc.). There are no Linux/macOS SMB client examples, nor any mention of how to monitor or tune SMB performance from non-Windows clients. Windows terminology and tools are presented exclusively and first throughout, creating friction for Linux/macOS users wishing to optimize SMB performance with Azure NetApp Files.
Recommendations
- Add equivalent SMB performance tuning and monitoring instructions for Linux/macOS clients (e.g., using smbclient, mount.cifs, or FIO on Linux).
- Provide Linux/macOS command examples for checking SMB Multichannel, encryption, and signing status.
- Include guidance on relevant Linux kernel options (e.g., cifs.ko module parameters) for SMB performance.
- Mention Linux tools for network and SMB performance monitoring (e.g., iostat, nload, atop, Wireshark, etc.).
- Clarify which recommendations are Windows-only and which are applicable to all SMB clients.
Azure Netapp Files
Create volume replication for Azure NetApp Files
...etapp-files/cross-region-replication-create-peering.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides Azure PowerShell examples first and in detail for feature registration, with only a brief mention of Azure CLI as an alternative. This prioritizes Windows/PowerShell usage, which may create friction for Linux/macOS users who typically use Azure CLI. The rest of the guide relies on Azure Portal UI steps, which are cross-platform, but the initial registration step is notably PowerShell-centric.
Recommendations
- Provide full Azure CLI command examples for feature registration and status checking, not just links.
- Present CLI and PowerShell examples side-by-side or in parallel sections, rather than PowerShell first.
- Clarify that both PowerShell and CLI are supported and equally valid for all steps.
- Where possible, include bash script snippets or Linux/macOS-specific notes for command-line steps.
Azure Netapp Files
Troubleshoot volume errors for Azure NetApp Files
...in/articles/azure-netapp-files/troubleshoot-volumes.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation provides a mix of troubleshooting steps for SMB, dual-protocol, and NFS volumes. However, there is a notable Windows bias: Active Directory (AD) and Microsoft Entra Domain Services (formerly Azure AD DS) are referenced throughout, and several steps require the use of Windows tools (e.g., 'Active Directory Users and Computers', PowerShell commands like Set-ADComputer). In the NFSv4.1 Kerberos section, PowerShell is suggested for setting Kerberos encryption types, and Windows UI tools are referenced before any Linux alternatives. Windows-centric terminology and tools are often mentioned first or exclusively, even when Linux clients are involved.
Recommendations
- For every PowerShell or Windows UI example (e.g., Set-ADComputer, Active Directory Users and Computers), provide equivalent Linux/Unix-based commands or workflows where possible (e.g., using ldapmodify, samba-tool, or other standard LDAP utilities).
- When referencing AD user/group membership or permissions, clarify how these can be managed from Linux (e.g., via ldapmodify or other cross-platform tools), or explicitly state if a Windows environment is required.
- In sections where troubleshooting involves NFS clients, ensure Linux-centric troubleshooting steps are given equal prominence and detail.
- When referencing tools like 'nslookup', clarify that these are available on both Windows and Linux, and provide example commands for both platforms.
- Where possible, avoid referencing Windows tools first if the issue is cross-platform, or alternate the order of examples.