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 451-475 of 896 flagged pages
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/create-volumes-dual-protocol.md ...les/azure-netapp-files/create-volumes-dual-protocol.md
High Priority View Details →
Scanned: 2025-08-02 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows, such as the use of the Active Directory Users and Computers MMC snap-in and detailed steps for accessing the Attribute Editor on Windows. There are no equivalent instructions or examples for managing POSIX attributes or LDAP users/groups from Linux environments, nor are Linux tools or workflows mentioned for these tasks. Additionally, the only example of attribute management is via Windows tools, and the order of presentation often puts Windows/SMB concepts and terminology first.
Recommendations
  • Provide equivalent Linux-based instructions for managing LDAP POSIX attributes, such as using ldapmodify, ldapadd, or tools like Apache Directory Studio.
  • Include examples or references for configuring and managing LDAP users and groups from Linux systems.
  • Balance the order of presentation so that Linux/NFS and Windows/SMB concepts are introduced together or alternate the order to avoid always putting Windows first.
  • Where screenshots or step-by-step guides are given for Windows tools, provide parallel guides for common Linux tools.
  • Explicitly mention cross-platform alternatives and clarify that both Windows and Linux environments are supported for administrative tasks.
GitHub Create Pull Request
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 →
Scanned: 2025-08-02 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally presents Windows/SMB concepts and terminology before or with more emphasis than Linux/NFS equivalents, especially in sections discussing dual-protocol and permissions. Windows tools and patterns (Active Directory, NTFS ACLs, SID translation, Kerberos/NTLM) are described in detail, while Linux equivalents (such as POSIX ACLs, idmapd, Samba configuration) are mentioned but not explained or exemplified. There are no Linux command-line or configuration examples, and Linux/Samba support is described as unofficial, which may discourage Linux users.
Recommendations
  • Provide parallel Linux/NFS examples and explanations wherever Windows/SMB tools or workflows are described (e.g., show how to view or set NFSv4 ACLs on Linux, or how to configure idmapd.conf).
  • Include Linux/Samba configuration guidance or references for connecting to Azure NetApp Files, even if support is limited.
  • Balance the order of presentation: when discussing dual-protocol or permissions, describe both Windows and Linux approaches side by side, rather than focusing on Windows/Active Directory first.
  • Clarify the level of support for Linux/Samba clients and provide troubleshooting tips or links for common interoperability issues.
  • Add Linux command-line examples (e.g., using getfacl/setfacl, mount options, rpcinfo, id mapping) to match the level of detail given for Windows tools.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/create-volumes-dual-protocol.md ...les/azure-netapp-files/create-volumes-dual-protocol.md
High Priority View Details →
Scanned: 2025-08-01 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation exhibits a Windows bias by providing detailed instructions and screenshots for managing LDAP POSIX attributes using Windows-only tools (Active Directory Users and Computers MMC snap-in), without offering equivalent Linux-based methods. The section on accessing the Attribute Editor is exclusively Windows-focused, and there are no examples or guidance for managing POSIX attributes from Linux environments. Additionally, Windows terminology and tools are mentioned first or exclusively in several places, while Linux/NFS client configuration is referenced only via a link, with no in-page examples.
Recommendations
  • Add equivalent instructions and examples for managing LDAP POSIX attributes using common Linux tools (e.g., ldapmodify, ldapadd, or Apache Directory Studio).
  • Include screenshots or command-line examples for Linux-based LDAP management to ensure parity with the Windows MMC snap-in instructions.
  • Where Windows tools or workflows are described, provide Linux alternatives in parallel, or at least mention them explicitly.
  • Ensure that configuration steps for both Windows and Linux clients are given similar prominence and detail, rather than linking out only for Linux.
  • Review the order of presentation to avoid always listing Windows tools or concepts first, especially in dual-protocol or cross-platform contexts.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-government.md ...b/main/articles/azure-netapp-files/azure-government.md
High Priority View Details →
Scanned: 2025-08-01 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions and command tables, while omitting equivalent Linux or Bash examples. The CLI section is present but lacks Linux-specific context or troubleshooting. There is no mention of Linux tools or shell environments, and PowerShell is given a dedicated, detailed section, reinforcing a Windows-centric approach.
Recommendations
  • Add explicit Bash/Linux shell examples for connecting to Azure Government, including environment variable setup and troubleshooting tips for common Linux distributions.
  • Include a section or notes on using Azure NetApp Files from Linux/macOS environments, highlighting any differences or additional steps required.
  • Balance PowerShell instructions with equivalent Bash or cross-platform scripting examples, especially for authentication and automation.
  • Mention cross-platform tools (such as Azure CLI in Bash, or REST API usage with curl) before or alongside PowerShell examples.
  • Ensure that references to tools and commands do not assume a Windows environment by default, and clarify when instructions are platform-specific.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/monitor-volume-capacity.md ...articles/azure-netapp-files/monitor-volume-capacity.md
High Priority View Details →
Scanned: 2025-08-01 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation presents Windows (SMB) client instructions and screenshots before Linux (NFS) client instructions, and provides more detailed steps and visual aids for Windows users (e.g., File Explorer, 'dir' command). The REST API section references PowerShell specifically, but does not mention Linux scripting or tools. This ordering and tool emphasis may give the impression of a Windows-centric approach.
Recommendations
  • Present Linux and Windows client instructions in parallel or alternate the order in different sections to avoid always listing Windows first.
  • Provide equivalent screenshots and detailed step-by-step instructions for Linux clients, such as using graphical file managers (e.g., Nautilus, Dolphin) to check NFS mount properties.
  • In the REST API section, mention and provide examples for using curl or other common Linux command-line tools, not just PowerShell.
  • Where possible, use neutral language and tool references (e.g., 'command prompt or terminal') and ensure parity in the depth of examples and visual aids for both platforms.
  • Explicitly state that all major platforms are supported and provide links or references to platform-specific documentation if available.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/create-active-directory-connections.md ...re-netapp-files/create-active-directory-connections.md
High Priority View Details →
Scanned: 2025-08-01 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only Windows/PowerShell command examples for Active Directory management (e.g., Get-ADUser, Set-ADUser), referencing Windows-specific tools and policies (such as Group Policy, registry keys, and Windows security privileges), and focusing on Windows terminology and workflows. There are no equivalent Linux or cross-platform command examples or guidance for managing AD connections from non-Windows environments. Azure CLI is mentioned, but only as an alternative for Azure resource registration, not for AD management. The documentation assumes the admin is operating in a Windows-centric environment.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using ldapmodify, kinit, or samba-tool) for managing AD user properties and Kerberos encryption types.
  • Reference cross-platform tools (such as Samba, sssd, or realmd) for joining and managing Active Directory from Linux systems.
  • Include Linux/Unix-specific considerations and workflows for AD integration, especially for NFS and Kerberos scenarios.
  • Balance the order of presentation so that Linux and Windows tools are introduced together, or provide parallel instructions for both platforms.
  • Clarify which steps are Windows-only and offer alternatives or guidance for non-Windows environments.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/disable-showmount.md .../main/articles/azure-netapp-files/disable-showmount.md
High Priority View Details →
Scanned: 2025-08-01 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for registering and unregistering the feature, mentioning PowerShell commands first, and not including equivalent Linux/Unix shell or Azure CLI examples inline. This may disadvantage users who administer Azure from non-Windows platforms or prefer command-line tools common on Linux.
Recommendations
  • Provide Azure CLI examples alongside PowerShell for all feature registration and status commands, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that all operations can be performed from Linux/macOS terminals using Azure CLI, and provide those command examples in the main steps (not just as a side note).
  • Consider including Bash shell script examples for automation scenarios relevant to Linux administrators.
  • Reorder examples or present both PowerShell and CLI commands together to avoid implying a Windows-first workflow.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-nfs.md ...-docs/blob/main/articles/azure-netapp-files/faq-nfs.md
High Priority View Details →
Scanned: 2025-08-01 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides a Windows-specific example (PowerShell command and mount syntax) for NFS client configuration but does not provide equivalent Linux commands or examples. Windows tools and patterns are mentioned explicitly, and Linux examples are missing in sections where both platforms are relevant. In the section about persistent NFS mounts, the Linux method is mentioned first, but no example is given, while the Windows section later provides detailed commands.
Recommendations
  • For every Windows-specific example (such as enabling CaseSensitiveLookup or mounting NFS volumes), provide an equivalent Linux example (e.g., relevant mount commands, configuration file edits).
  • When mentioning tools or commands (like PowerShell or Mount), also mention the Linux/Unix equivalents (e.g., mount command, /etc/fstab editing).
  • Ensure that Linux and Windows instructions/examples are presented in parallel or side-by-side, rather than focusing on one platform.
  • Where possible, use neutral language and avoid assuming the reader is using Windows unless the section is explicitly Windows-only.
  • Add explicit Linux troubleshooting tips for NFS client issues, similar to the Windows guidance provided.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-file-access-logs.md ...articles/azure-netapp-files/manage-file-access-logs.md
High Priority View Details →
Scanned: 2025-08-01 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed, step-by-step instructions for setting SACLs using Windows GUI tools, referencing Windows administration hosts, and using PowerShell commands for feature registration. Equivalent Linux/NFS instructions are either missing, less detailed, or deferred to external links. The registration section leads with PowerShell examples, and the process for setting Audit ACEs on NFS volumes is not described inline, but instead refers to another document.
Recommendations
  • Provide step-by-step instructions for setting Audit ACEs on NFSv4.1 volumes directly in this document, similar to the Windows SACL steps.
  • Include Linux command-line examples (e.g., using setfacl or nfs4_setfacl) for configuring Audit ACEs.
  • When presenting feature registration, show Azure CLI examples before or alongside PowerShell, not after.
  • Balance the prominence of Windows and Linux tools and terminology throughout the document.
  • Add screenshots or command examples for Linux/NFS workflows where Windows GUI screenshots are provided.
GitHub Create Pull Request
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 →
Scanned: 2025-08-01 00:00
Reviewed by: Unknown
Issues: 3 bias types
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 (NTFS, SID, Active Directory, NTLM) is used as the default or primary reference, and there are no Linux command-line examples for SMB/Samba access. Official support is stated for Windows and macOS SMB clients, but not for Linux, despite Samba being widely used. Linux/NFS examples are present, but Linux SMB usage is downplayed and lacks parity in guidance.
Recommendations
  • Provide explicit Linux/Samba command-line examples for accessing SMB shares, similar to the NFS rpcinfo example.
  • Clarify and expand support guidance for Linux SMB clients, including common troubleshooting tips.
  • Balance the order of presentation so that Linux/NFS and Windows/SMB are introduced with equal prominence.
  • When discussing permissions and ACLs, include both NTFS and POSIX/NFSv4 ACLs side by side, with examples.
  • Reference Linux tools (e.g., mount.cifs, smbclient) and configuration patterns where appropriate.
  • Avoid language that implies Windows is the default or primary environment (e.g., 'SMB is primarily used with Windows clients'), and instead acknowledge the prevalence of mixed environments.
GitHub Create Pull Request
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 →
Scanned: 2025-08-01 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. In sections describing how to create and manage snapshots, PowerShell is mentioned explicitly and linked alongside Azure Portal, REST API, and Azure CLI, but there are no explicit Linux shell or Bash examples. The order of tools often lists PowerShell before or alongside CLI, but never provides Linux-specific command-line examples or scripts. There are no references to Linux-native tools or workflows, and no sample commands for Linux users. This may make Linux administrators feel less directly supported.
Recommendations
  • Add explicit Bash/Azure CLI examples for common snapshot operations (e.g., creating, listing, deleting snapshots) to demonstrate parity with PowerShell.
  • When listing management tools, alternate the order or group Azure CLI and PowerShell together, or mention CLI first to avoid a Windows-first impression.
  • Include example scripts or links for Linux environments, not just PowerShell or Windows-centric scripting.
  • Reference Linux-native workflows or tools where applicable, especially for scripting and automation.
  • Clarify that all operations can be performed equally from Linux environments using Azure CLI and REST API, and provide sample commands.
  • If referencing PowerShell, consider also referencing Bash or shell scripting for Linux users.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-nfs.md ...-docs/blob/main/articles/azure-netapp-files/faq-nfs.md
High Priority View Details →
Scanned: 2025-07-17 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides a detailed answer for troubleshooting NFS access from Windows clients, including explicit PowerShell commands and Windows mount examples, but does not provide equivalent troubleshooting or usage examples for Linux clients. The only Linux-specific guidance is a brief mention of editing /etc/fstab for persistent mounts, without concrete commands or troubleshooting steps. This results in a Windows-first and Windows-tools bias, with missing Linux examples for common scenarios.
Recommendations
  • For every Windows-specific example (such as enabling CaseSensitiveLookup or mounting NFS volumes), provide equivalent Linux commands and troubleshooting steps (e.g., using mount options, nfs-utils, or systemd automount).
  • When mentioning PowerShell or Windows tools, ensure Linux tools (such as mount, nfsstat, or showmount) are also referenced and described.
  • If a scenario is described for Windows (e.g., slow folder lookup), include a comparable Linux scenario or note if it is not applicable.
  • Avoid placing Windows examples or tools before Linux equivalents in sections that apply to both platforms; present both in parallel or start with Linux if the technology (NFS) is more commonly associated with Unix/Linux.
  • Expand the Linux guidance beyond /etc/fstab to include troubleshooting, mount options, and common issues, matching the depth given to Windows.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/disable-showmount.md .../main/articles/azure-netapp-files/disable-showmount.md
High Priority View Details →
Scanned: 2025-07-17 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page primarily uses Azure PowerShell commands for feature registration and management, with only a brief mention of Azure CLI as an alternative. There are no Linux shell or bash examples, and the PowerShell examples are presented first and in detail, which may disadvantage Linux users or those who prefer CLI/bash environments.
Recommendations
  • Provide equivalent Azure CLI (az) command examples alongside or before PowerShell examples, especially for feature registration and status checking.
  • Include explicit bash/Linux shell command blocks for tasks that can be performed from non-Windows environments.
  • Clarify that all operations can be performed from any OS using Azure CLI, and provide links or instructions for installing and using Azure CLI on Linux.
  • Ensure screenshots and UI references are OS-agnostic or supplemented with CLI output examples.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/create-volumes-dual-protocol.md ...les/azure-netapp-files/create-volumes-dual-protocol.md
High Priority View Details →
Scanned: 2025-07-17 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily in the 'Manage LDAP POSIX Attributes' section, where only Windows-based tools (Active Directory Users and Computers MMC snap-in) are described for managing POSIX attributes. There are no equivalent instructions or examples for performing these tasks from Linux or cross-platform tools. Additionally, the instructions for accessing the Attribute Editor are Windows-specific, and the documentation does not mention or provide guidance for Linux-based LDAP management tools. While NFS client configuration is referenced, it is only linked out and not described inline, and the overall flow assumes Windows administrative environments for directory and attribute management.
Recommendations
  • Add equivalent instructions for managing LDAP POSIX attributes using Linux-based tools such as ldapmodify, ldapadd, or graphical tools like Apache Directory Studio.
  • Include examples or references for editing LDAP attributes from Linux command line or cross-platform tools, not just Windows MMC.
  • When describing attribute management, present both Windows and Linux methods, or at least mention that Linux-based alternatives exist.
  • Consider reordering sections or providing parallel instructions so that Linux and Windows administrative tasks are given equal prominence.
  • Where screenshots are provided for Windows tools, consider adding screenshots or command examples for Linux tools to improve parity.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/disable-showmount.md .../main/articles/azure-netapp-files/disable-showmount.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page primarily provides Azure PowerShell commands for feature registration and management, with only a brief mention of Azure CLI as an alternative. There are no Linux shell or cross-platform CLI examples, and the PowerShell commands are presented first and in detail, which may disadvantage Linux users or those who prefer CLI tools.
Recommendations
  • Provide equivalent Azure CLI command examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that all operations can be performed from Linux, macOS, or Windows using Azure CLI.
  • Include example shell commands (bash) for Linux users where applicable, especially for NFS-related tasks.
  • Balance the order of examples so that CLI and PowerShell are given equal prominence, or lead with the more cross-platform option.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/convert-nfsv3-nfsv41.md ...in/articles/azure-netapp-files/convert-nfsv3-nfsv41.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias in the feature registration section, where Azure PowerShell commands are presented first and in detail, while Azure CLI (more common on Linux) is only briefly mentioned in passing. The rest of the guide focuses on NFS operations, which are inherently Linux/UNIX-centric, and provides Linux command examples (e.g., umount, mount) exclusively, with no Windows or PowerShell client-side examples. However, the initial registration steps may disadvantage Linux users by not providing full CLI examples up front.
Recommendations
  • Provide full Azure CLI command examples for feature registration and status checking, not just a reference link.
  • Present Azure CLI and PowerShell registration examples side by side, or list CLI first to better support Linux users.
  • Clarify that the NFS client operations are intended for Linux/UNIX systems, and if Windows NFS client support is relevant, provide equivalent instructions or a note.
  • Review future documentation for similar patterns where Windows tooling is prioritized or Linux tooling is only referenced indirectly.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/create-volumes-dual-protocol.md ...les/azure-netapp-files/create-volumes-dual-protocol.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows, such as the Active Directory Users and Computers MMC snap-in, and providing detailed steps and screenshots for Windows-based attribute management. There are no equivalent instructions or examples for managing LDAP POSIX attributes from Linux or cross-platform tools. The documentation also references Windows-specific commands and features (e.g., 'net view', Windows File Browser) without Linux or macOS alternatives, and generally presents Windows approaches before Linux ones.
Recommendations
  • Provide equivalent instructions and examples for managing LDAP POSIX attributes using Linux tools (e.g., ldapmodify, ldapadd, or Apache Directory Studio) alongside the Windows MMC snap-in.
  • Include Linux/macOS examples for relevant administrative tasks, such as viewing or editing LDAP attributes, mounting NFS shares, and managing permissions.
  • When referencing Windows-specific commands (e.g., 'net view', Windows File Browser), also mention Linux equivalents (e.g., smbclient, Nautilus, or command-line tools).
  • Balance the order of presentation so that Linux and Windows approaches are given equal prominence, or group them under clear OS-specific headings.
  • Add screenshots or command-line examples from Linux environments where appropriate, especially in sections discussing NFS or LDAP configuration.
GitHub Create Pull Request
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 →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally presents Windows/SMB concepts and tools before or with more emphasis than their Linux/NFS counterparts. SMB (Windows) is described as the primary use case for dual-protocol and identity management, and Windows terminology (NTFS, SID, NTLM, Active Directory) is used extensively. Official support is stated for SMB on Windows/macOS, but not for Linux (Samba), and there is a lack of Linux command-line or configuration examples compared to references to Windows tools and concepts. Linux/NFS details are present, but practical Linux usage examples (e.g., mounting, permissions, troubleshooting) are missing.
Recommendations
  • Provide parallel Linux/NFS examples for all Windows/SMB concepts, such as showing Linux mount commands, permission management, and troubleshooting steps.
  • Explicitly mention and provide guidance for using Samba on Linux, including any limitations or best practices.
  • Balance the order of presentation so that Linux/NFS and Windows/SMB are introduced and discussed with equal prominence.
  • Include Linux-specific tools and configuration file references (e.g., /etc/fstab, idmapd.conf, nfs-utils) alongside Windows tools (e.g., NTFS, SID, Active Directory).
  • Clarify support status and provide troubleshooting resources for Linux clients (including Samba) to avoid the perception of Windows preference.
  • Add practical Linux-focused scenarios and FAQs, especially for dual-protocol and identity mapping situations.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-nfs.md ...-docs/blob/main/articles/azure-netapp-files/faq-nfs.md
High Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides a detailed PowerShell command and Windows-specific instructions for resolving NFS client performance issues on Windows, but does not offer equivalent Linux commands or troubleshooting steps. This creates an imbalance, as Linux is a primary platform for NFS usage. Other sections reference Linux (e.g., /etc/fstab) but do not provide Linux-centric troubleshooting or examples where Windows-specific guidance is given.
Recommendations
  • For every Windows-specific example (such as enabling CaseSensitiveLookup via PowerShell), provide an equivalent Linux example or troubleshooting step, or explicitly state if the issue is Windows-only.
  • When discussing mounting or configuring NFS, ensure both Linux and Windows procedures are included, especially in troubleshooting scenarios.
  • If a problem or configuration is unique to Windows, clarify this in the documentation to avoid confusion for Linux users.
  • Include Linux command-line examples (e.g., using mount options, sysctl, or nfs-utils configuration) where appropriate, especially in sections where only Windows commands are currently shown.
  • Review the document for other places where Windows tools or patterns are mentioned without Linux parity, and add Linux equivalents or cross-references.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/disable-showmount.md .../main/articles/azure-netapp-files/disable-showmount.md
High Priority View Details →
Scanned: 2025-07-15 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for registering and unregistering the feature, mentioning Azure CLI only as an aside without examples, and omitting any Linux shell or cross-platform command-line instructions. The primary workflow is presented using PowerShell, which is most familiar to Windows users.
Recommendations
  • Provide equivalent Azure CLI command examples (e.g., 'az feature register', 'az feature show', 'az feature unregister') alongside PowerShell commands, with full syntax and example output.
  • Present Azure CLI (cross-platform) commands before or alongside PowerShell to avoid the impression of Windows-first bias.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide guidance for users on those platforms.
  • Where possible, include screenshots or terminal output from Linux/macOS environments to reinforce cross-platform support.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-nfs.md ...-docs/blob/main/articles/azure-netapp-files/faq-nfs.md
High Priority View Details →
Scanned: 2025-07-15 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a detailed PowerShell example and troubleshooting steps specifically for Windows NFS clients, including a PowerShell command and a Windows mount example. However, there are no equivalent Linux command examples or troubleshooting steps for Linux NFS clients, despite Linux being a primary NFS use case. This creates a Windows bias by prioritizing Windows tools, commands, and scenarios, while omitting Linux-specific guidance.
Recommendations
  • Add equivalent Linux troubleshooting guidance for common NFS client issues (e.g., case sensitivity, mount performance).
  • Provide Linux command-line examples (e.g., mount commands, NFS client configuration) wherever Windows examples are given.
  • Ensure that Linux tools and workflows are mentioned at least as prominently as Windows ones, especially in sections discussing mounting, configuration, and troubleshooting.
  • When referencing external documentation, ensure parity by linking to both Windows and Linux guides.
  • Consider adding a dedicated FAQ entry for Linux client issues, similar to the Windows client troubleshooting section.
GitHub Create Pull Request
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 →
Scanned: 2025-07-15 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation generally provides a balanced overview of both NFS (Linux/UNIX) and SMB (Windows) protocols, but there are subtle Windows biases. Windows tools and terminology (Active Directory, NTFS ACLs, SID translation, Entra ID) are referenced more frequently and with more official support. SMB/Windows scenarios are described as the default or primary use case, while Linux/UNIX (especially Samba/SMB on Linux) is described as unsupported or secondary. There are no Linux-specific command examples for SMB (e.g., using smbclient or mount.cifs), and the only command-line example given is for NFS (rpcinfo). Linux/UNIX tools and patterns are mentioned, but not as prominently or with as much detail as their Windows counterparts.
Recommendations
  • Provide Linux-specific SMB usage examples (e.g., mounting SMB shares with mount.cifs, using smbclient) alongside Windows/Active Directory scenarios.
  • Clarify support status for SMB/Samba on Linux and provide guidance or references for best-effort interoperability.
  • Balance the order of protocol/tool presentation: when discussing dual-protocol or identity management, mention Linux/UNIX (e.g., LDAP, nsswitch) equally or before Windows/Active Directory.
  • Include more Linux/UNIX-focused troubleshooting and configuration tips, especially for dual-protocol environments.
  • Reference both Windows and Linux tools/utilities for managing permissions and shares (e.g., getfacl/setfacl for NFSv4 ACLs, as well as Windows ACL tools).
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-kerberos-encryption.md ...es/azure-netapp-files/configure-kerberos-encryption.md
High Priority View Details →
Scanned: 2025-07-14 21:48
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a Windows bias by requiring the use of PowerShell commands (Set-ADComputer) and Windows-specific tools (RSAT) for essential Active Directory configuration steps. These instructions are presented before any Linux client configuration, and there are no equivalent Linux-based methods or alternatives provided for managing the necessary AD computer account settings. The documentation assumes access to a Windows environment for directory management, which may not be available to all Linux-focused administrators.
Recommendations
  • Provide equivalent instructions for configuring the Kerberos encryption type on the AD computer account using Linux-based tools, such as 'ldapmodify' or 'adcli', for environments where Windows or RSAT is not available.
  • Clearly indicate that the PowerShell/RSAT steps are required only if no Linux-based AD management tools are available, and offer cross-platform alternatives.
  • Reorder sections to present Linux client configuration and mounting steps before or alongside Windows/AD configuration to avoid the impression of Windows primacy.
  • Add a note or appendix with guidance for organizations that use Samba or other non-Windows AD-compatible services for directory management.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-network-features.md ...icles/azure-netapp-files/configure-network-features.md
High Priority View Details →
Scanned: 2025-07-14 21:48
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through exclusive use of Azure PowerShell commands for feature registration status checks, with no equivalent Azure CLI (cross-platform) or Bash examples provided. The only command-line examples are in PowerShell, and there are no Linux-specific or cross-platform instructions for these tasks. The documentation also references the Azure portal (web UI), which is platform-neutral, but all scripting/automation is Windows-centric.
Recommendations
  • Provide Azure CLI (az) command equivalents for all Azure PowerShell examples, especially for feature registration checks (e.g., az feature show --namespace Microsoft.NetApp --name ANFBasicToStdNetworkFeaturesUpgrade).
  • Where possible, include Bash shell examples for scripting tasks, or clarify that the steps can be performed on any OS using the Azure CLI.
  • Explicitly state that both Azure PowerShell and Azure CLI can be used for management tasks, and link to relevant cross-platform tool documentation.
  • If any automation or scripting is shown, ensure parity by including both PowerShell and Bash/Azure CLI snippets.
  • Review for any terminology or tool references that are Windows-specific and provide Linux/macOS equivalents where applicable.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/convert-nfsv3-nfsv41.md ...in/articles/azure-netapp-files/convert-nfsv3-nfsv41.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the feature registration section, where Azure PowerShell commands are presented first and in detail, while Azure CLI (more common on Linux) is only mentioned in passing. The use of PowerShell-specific code blocks and terminology (e.g., Register-AzProviderFeature, Get-AzProviderFeature) prioritizes Windows tooling. However, the main NFS conversion workflow and client-side examples are Linux-centric, using Linux commands (umount, mount, /etc/fstab) and terminology.
Recommendations
  • Provide Azure CLI examples alongside (or before) Azure PowerShell examples for feature registration and status checking, with full command syntax and output samples.
  • Explicitly mention that both Windows and Linux clients are supported, and clarify any differences in steps for each platform.
  • Where possible, use platform-neutral language and tooling, or present both Windows and Linux options equally.
  • Ensure screenshots and UI references are not Windows-specific unless necessary.
  • Add a section or note for Windows NFS clients if they are supported, or clarify if the instructions are Linux-only.
GitHub Create Pull Request
← Previous Page 19 of 36 Next →