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 426-450 of 896 flagged pages
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-05 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation displays a Windows bias by presenting Windows/Powershell examples and workflows first and in more detail, especially for setting SACLs and registering features. Windows tools and UI steps are described explicitly, while Linux/NFS workflows are referenced but not detailed. There is a lack of parity in step-by-step instructions for Linux environments, and Powershell is the primary CLI example given.
Recommendations
  • Provide equivalent, step-by-step instructions for setting Audit ACEs on NFSv4.1 shares from a Linux client, including example commands (e.g., using setfacl or nfs4_setfacl).
  • Include Linux/Unix CLI examples (such as Azure CLI) alongside or before Powershell examples for feature registration and management.
  • Balance the order of presentation so that Linux/NFS and Windows/SMB instructions are given equal prominence, or group them under clear headings.
  • Explicitly mention and link to Linux tools/utilities required for ACL management, and provide troubleshooting tips for common Linux scenarios.
  • Where screenshots or UI steps are provided for Windows, consider providing equivalent terminal screenshots or command output for Linux.
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-05 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally balanced in its protocol descriptions, but there are subtle Windows biases. SMB (the Windows protocol) is described as 'officially supported' for Windows and macOS, while Linux SMB (via Samba) is noted as unsupported. Windows terminology and tools (Active Directory, NTFS ACLs, SID translation, NTLM) are referenced as defaults or requirements, and Linux/UNIX equivalents are not always given equal prominence. There are no Linux command-line examples for SMB access or configuration, and the only example command provided is for NFS (rpcinfo), with no equivalent for SMB. The documentation assumes Active Directory as the primary identity provider, with LDAP as a secondary mention.
Recommendations
  • Provide explicit Linux/Samba examples for SMB access and configuration, including sample mount commands and troubleshooting steps.
  • Clarify the support status for Linux SMB clients and provide guidance or best practices for their use, even if not officially supported.
  • When discussing identity management, give equal detail to LDAP and UNIX/Linux name services as to Active Directory.
  • Include Linux/UNIX terminology and tools (e.g., idmap, getfacl/setfacl, nsswitch.conf) alongside Windows terms like NTFS and SID.
  • Where possible, avoid presenting Windows/Active Directory as the default or only supported scenario; instead, present both Windows and Linux/UNIX options in parallel.
  • Add Linux-focused troubleshooting and configuration sections for dual-protocol environments, including common issues with UID/GID mapping and permissions.
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-05 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias in several areas. It provides detailed instructions and screenshots for managing LDAP POSIX attributes using Windows tools (Active Directory Users and Computers MMC snap-in), but does not offer equivalent guidance for Linux-based management of LDAP attributes. The only example for editing POSIX attributes is via Windows, and there are no Linux command-line or GUI alternatives mentioned. Additionally, the documentation refers to Windows-specific features and tools (e.g., Windows File Browser, 'net view' command) before or instead of Linux equivalents, and the workflow for managing user attributes is presented solely from a Windows perspective.
Recommendations
  • Add instructions and examples for managing LDAP POSIX attributes using Linux tools (e.g., ldapmodify, ldapadd, or graphical LDAP editors like Apache Directory Studio).
  • Include Linux command-line examples for editing user and group attributes in LDAP directories.
  • When referencing features like share browsing, mention Linux/UNIX equivalents (e.g., using smbclient or NFS mount commands) alongside Windows tools.
  • Balance screenshots and step-by-step guides by providing both Windows and Linux workflows where applicable.
  • Explicitly state that both Windows and Linux administrators can manage dual-protocol volumes and provide parity in guidance.
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-05 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 before Linux (NFS) client instructions, with more detailed steps and screenshots for Windows (including both GUI and command-line methods). Windows-specific tools (File Explorer, dir command) are described in detail, while the Linux section is shorter and only mentions the df command. Additionally, in the REST API section, PowerShell is mentioned explicitly, but there is no mention of Linux shell or curl examples.
Recommendations
  • Present Linux and Windows client instructions in parallel or alternate the order in different documentation sections to avoid always listing Windows first.
  • Provide equivalent detail and screenshots for Linux clients, including both GUI (if applicable, e.g., GNOME Files) and command-line methods.
  • Include Linux shell or curl examples in the REST API section, not just PowerShell.
  • Mention and explain common Linux tools (e.g., ls, stat, ncdu) where relevant, similar to how Windows tools are described.
  • Ensure parity in troubleshooting notes and caveats for both platforms.
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-04 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Windows/PowerShell examples for key administrative tasks (such as enabling Kerberos encryption), referencing Windows-specific tools and policies (e.g., Group Policy, Windows registry keys, Set-ADUser), and omitting equivalent Linux/Unix commands or workflows. Windows terminology and tools are consistently mentioned first or exclusively, while Linux/Unix administration scenarios are not addressed, despite the relevance for NFS and dual-protocol volumes.
Recommendations
  • Provide equivalent Linux/Unix command-line examples (e.g., using 'kadmin', 'ldapmodify', or 'realm' for Kerberos and LDAP configuration) alongside PowerShell commands.
  • Include guidance for managing Active Directory integration from Linux hosts, especially for NFS and dual-protocol scenarios, such as joining AD from Linux or configuring Kerberos tickets.
  • Reference Linux tools and configuration files (e.g., /etc/krb5.conf, sssd, realmd) where relevant, and explain how to achieve required settings without Windows tools.
  • Balance the order of presentation so that Linux/Unix workflows are described alongside or before Windows-specific instructions where applicable.
  • Clarify which steps are required or different for Linux-based environments, especially for customers managing mixed or non-Windows infrastructures.
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-04 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 presenting Windows/Powershell examples and instructions first, providing detailed steps for setting SACLs via the Windows GUI, and referencing Windows tools (e.g., robocopy) without Linux equivalents. There is a lack of step-by-step Linux command examples for managing Audit ACEs or SACLs on NFS shares, and Linux tooling is only referenced indirectly or via links.
Recommendations
  • Provide equivalent step-by-step instructions for setting Audit ACEs on NFSv4.1 shares from a Linux client, including example commands (e.g., using setfacl or nfs4_setfacl).
  • Include Linux CLI examples for feature registration and management, not just Azure PowerShell and CLI references.
  • Mention Linux tools (e.g., rsync) alongside Windows tools like robocopy when discussing migration operations.
  • Ensure that instructions for both Windows and Linux are presented in parallel or with equal prominence, rather than Windows-first.
  • Add screenshots or terminal output examples for Linux-based workflows where applicable.
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-04 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 managing the 'Disable showmount' feature, with only a brief mention of Azure CLI as an alternative. There are no explicit Linux shell or Bash examples, and the PowerShell approach is presented first and in detail, which may disadvantage users on Linux or macOS platforms.
Recommendations
  • Provide equivalent Azure CLI command examples alongside PowerShell, with full syntax and usage.
  • Include Bash shell examples for Linux users where applicable (e.g., using az CLI in Bash).
  • Present both PowerShell and CLI options in parallel, or lead with the more cross-platform Azure CLI.
  • Clarify that all commands can be run on any platform where Azure CLI is available, not just Windows.
  • Add a note or section specifically for Linux/macOS users, ensuring parity in instructions and screenshots if interface differences exist.
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-04 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 step-by-step guidance for Windows users (including both GUI and command-line methods). Windows-specific tools (File Explorer, dir command) are highlighted, while Linux instructions are briefer and limited to the df command. REST API usage references PowerShell specifically, but does not mention Linux shell scripting or tools.
Recommendations
  • Alternate the order of Windows and Linux sections in different documentation updates, or present them in parallel to avoid always prioritizing Windows.
  • Provide equally detailed Linux instructions, including both GUI (if applicable, e.g., GNOME Files/Nautilus) and command-line methods.
  • For REST API usage, include examples for both PowerShell (Windows) and bash/curl/jq (Linux/macOS) to ensure parity.
  • Mention Linux-native tools (such as lsblk, ncdu, or graphical disk usage analyzers) where relevant, not just df.
  • Ensure screenshots and examples are balanced between platforms, and avoid implying Windows is the default or primary environment.
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-04 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing on Windows-native tools (Active Directory Users and Computers MMC snap-in) for managing LDAP POSIX attributes, providing step-by-step instructions and screenshots only for Windows environments. There are no equivalent instructions or examples for managing POSIX attributes from Linux or cross-platform tools. The documentation also references Windows-specific features and tools (e.g., Windows File Browser, 'net view' command) before or instead of Linux equivalents, and omits Linux-based workflows for common administrative tasks.
Recommendations
  • Provide equivalent instructions and screenshots for managing LDAP POSIX attributes using Linux tools (e.g., ldapmodify, ldapadd, or Apache Directory Studio) alongside the Windows MMC snap-in.
  • Include examples of how to access and modify LDAP attributes from Linux command-line utilities or cross-platform GUI tools.
  • When referencing Windows-specific tools or commands (e.g., Windows File Browser, 'net view'), also mention Linux/NFS equivalents (e.g., using 'showmount', 'ls', or 'mount' commands) and describe how similar tasks can be performed from Linux clients.
  • Ensure that all configuration and management steps are documented for both Windows and Linux environments, especially for tasks relevant to dual-protocol (NFS and SMB) scenarios.
  • Consider reordering sections or examples so that Linux and Windows instructions are presented with equal prominence, or grouped together for parity.
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-04 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. SMB/Windows terminology and tools are introduced before or with more detail than Linux/NFS equivalents. Official support is highlighted for Windows and macOS SMB clients, while Linux (Samba) is described as unsupported. Windows-specific features (NTFS ACLs, SID translation, NTLM fallback) are explained in detail, but Linux/NFS equivalents (such as POSIX ACLs, idmapd, or Samba configuration) are not equally covered. No practical Linux/NFS configuration or troubleshooting examples are provided, and there is a lack of parity in example commands or references for Linux administrators.
Recommendations
  • Provide equal emphasis and detail for Linux/NFS and Windows/SMB throughout the documentation.
  • Include practical Linux/NFS client configuration and troubleshooting examples (e.g., mounting NFS shares, configuring idmapd, setting POSIX/NFSv4 ACLs).
  • When describing dual-protocol or identity mapping, include Linux-specific tools and workflows (such as nsswitch.conf, getent, idmapd.conf) alongside Windows/Active Directory concepts.
  • Clarify the support status for Linux SMB clients and provide guidance or references for best-effort interoperability.
  • Balance the order of presentation: do not always introduce Windows/SMB first; alternate or present both platforms together.
  • Add Linux-focused links in the 'Next steps' section (e.g., guides for configuring NFS clients, troubleshooting Linux access issues, using Samba with Azure NetApp Files).
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-04 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. In the section 'Ways to create snapshots', PowerShell is explicitly mentioned alongside Azure CLI, REST API, and the Azure portal, but there is no mention of Linux shell scripting or examples using Bash. The ordering of tools often lists PowerShell before or alongside CLI, with no explicit Linux-focused guidance or examples. There are no Linux-specific commands or references to Linux-native tools or workflows, and no examples are provided for Linux users. This may make the documentation less accessible or immediately useful for Linux administrators.
Recommendations
  • Add explicit Linux/Bash examples for creating and managing snapshots, such as using Azure CLI from a Bash shell.
  • When listing tools, alternate or randomize the order of Azure CLI and PowerShell, or list Azure CLI first, as it is cross-platform.
  • Include sample scripts or command lines for both Windows (PowerShell) and Linux (Bash) environments.
  • Reference Linux-native automation and scripting patterns where appropriate, such as cron jobs for automation.
  • Ensure that all instructions and examples are platform-neutral or provide parity between Windows and Linux wherever possible.
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-04 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation exhibits Windows bias in the section addressing NFS access from Windows clients. It provides detailed PowerShell commands and mounting instructions for Windows, but does not offer equivalent Linux examples or commands. Additionally, Windows-specific troubleshooting is covered, while Linux client troubleshooting is not. In the persistent mount section, Linux is mentioned first, but the linked documentation is generic and not expanded upon here. Overall, the page assumes Windows users need more explicit guidance, while Linux users are expected to infer or seek information elsewhere.
Recommendations
  • For every Windows-specific example (such as PowerShell commands and mount instructions), provide equivalent Linux commands (e.g., mount command with options, NFS client configuration).
  • Include troubleshooting tips for Linux NFS clients, similar to the Windows CaseSensitiveLookup guidance.
  • Where Windows tools or patterns are mentioned, ensure Linux tools (such as nfs-utils, mount.nfs, /etc/fstab configuration) are also described.
  • Balance the depth of explanation between Windows and Linux, ensuring that Linux administrators receive as much actionable detail as Windows administrators.
  • Consider adding a dedicated FAQ entry for common Linux NFS client issues and their solutions.
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-03 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows-centric bias by providing only PowerShell commands for Active Directory configuration, referencing Windows-specific tools and registry keys, and omitting equivalent Linux/Unix commands or tools for managing Kerberos, LDAP, or AD integration. Windows terminology and tools are used exclusively or introduced before any mention of cross-platform or Linux alternatives. There are no examples or guidance for Linux-based AD management or Kerberos configuration, despite the relevance for NFS and dual-protocol volumes.
Recommendations
  • Provide equivalent Linux/Unix command-line examples (e.g., using 'kadmin', 'ldapmodify', or 'realm' for Kerberos and LDAP configuration) alongside PowerShell commands.
  • Reference cross-platform tools and procedures for managing AD integration, such as Samba, SSSD, or MIT Kerberos, especially for NFS and dual-protocol scenarios.
  • Avoid Windows-specific registry and Group Policy references without mentioning how similar settings can be managed on Linux systems.
  • Include explicit sections or notes for Linux administrators, especially where NFS, Kerberos, or LDAP integration is discussed.
  • Balance the order of presentation so that Linux and Windows methods are introduced together, or provide parallel instructions for both platforms.
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-03 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 detail than Linux/NFS equivalents, especially in the SMB section. Windows tools and patterns (Active Directory, NTFS ACLs, Kerberos/NTLM, SID translation) are referenced as defaults, while Linux/Samba support is described as unofficial. There are no Linux command-line examples for SMB access or identity mapping, and Linux tools for SMB (e.g., smbclient, mount.cifs) are not mentioned. The NFS section is more Linux-focused, but the SMB section lacks Linux parity.
Recommendations
  • Provide Linux command-line examples for accessing SMB shares (e.g., using smbclient or mount.cifs) alongside Windows examples.
  • Mention and briefly describe Samba and its configuration for Linux clients, including any caveats or best practices for interoperability with Azure NetApp Files.
  • Clarify the support status for Linux SMB clients, and provide guidance or links for troubleshooting common interoperability issues.
  • When discussing identity management and permissions, include Linux/Samba equivalents (e.g., mapping POSIX users/groups to SMB SIDs, using winbind or sssd).
  • Balance the order of presentation so that Linux and Windows tools/concepts are introduced together, or alternate which is presented first in each section.
  • Add references to Linux documentation for SMB and NFS, not just Windows/NTFS/Active Directory.
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-03 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 in several areas. It provides detailed instructions and screenshots for managing LDAP POSIX attributes using Windows-only tools (Active Directory Users and Computers MMC snap-in), without mentioning or providing equivalent Linux-based methods. The only explicit example for editing POSIX attributes is via Windows, and there are no Linux or cross-platform alternatives shown. Additionally, the order of presentation and terminology often assumes a Windows-centric environment, with Windows tools and workflows described first or exclusively.
Recommendations
  • Include equivalent Linux-based instructions for managing LDAP POSIX attributes, such as using ldapmodify, ldapadd, or graphical tools like Apache Directory Studio.
  • Provide examples or references for configuring and managing dual-protocol volumes from Linux clients, including attribute management and troubleshooting.
  • Balance the documentation by presenting both Windows and Linux workflows side by side, especially in sections that currently only mention Windows tools.
  • Add screenshots or command-line examples for Linux environments where appropriate, to ensure parity and inclusivity for non-Windows administrators.
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-03 00:00
Reviewed by: Unknown
Issues: 3 bias types
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-oriented tools (PowerShell) are mentioned explicitly and often before or instead of Linux equivalents. There are no explicit Linux shell (bash) or scripting examples, and the documentation does not mention Linux-native tools or provide Linux-specific guidance, despite Azure NetApp Files being commonly used in Linux environments (e.g., NFS volumes).
Recommendations
  • When listing management tools, mention Azure CLI and REST API before or alongside PowerShell, as these are cross-platform and commonly used in Linux environments.
  • Provide explicit Linux shell (bash) command examples for snapshot management, especially when referencing scripting or automation.
  • Include references or links to Linux-native tools or workflows (e.g., using cron jobs with Azure CLI for automated snapshots).
  • When discussing client-side restore operations, include both Windows (SMB) and Linux (NFS) client examples, showing how to access and restore files from snapshots on each platform.
  • Ensure that any scripting guidance is cross-platform, or provide parallel examples for both PowerShell and bash.
  • Review the order of tool mentions to avoid always listing Windows/PowerShell first, especially in summary or introductory lists.
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-03 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation 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 cross-platform examples, and the PowerShell examples are presented first and in detail, which may disadvantage Linux users.
Recommendations
  • Provide explicit Azure CLI command examples alongside PowerShell for all steps, not just as a note.
  • Include Linux shell (bash) command examples where relevant, especially for NFS-related operations.
  • Present CLI and PowerShell examples in parallel or in separate tabs to avoid prioritizing Windows tools.
  • Clarify that all operations can be performed from any OS using Azure CLI, not just from Windows/PowerShell environments.
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-03 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page is generally neutral and focused on NFS, which is predominantly a Linux/UNIX protocol. However, in the section addressing Windows client performance, only Windows-specific tools and PowerShell commands are provided, with no equivalent Linux examples for mounting or configuration. This introduces a subtle Windows bias by assuming or prioritizing Windows client scenarios in a Linux-centric context.
Recommendations
  • When providing Windows-specific commands (such as PowerShell for enabling CaseSensitiveLookup), also provide equivalent Linux commands or configuration steps for common Linux NFS client scenarios.
  • For mount examples, include both Windows and Linux command-line examples side by side, especially since NFS is more commonly used in Linux environments.
  • If discussing client-side configuration or troubleshooting, ensure parity by addressing both Windows and Linux clients, or clarify when a scenario is Windows-specific.
  • Consider reordering or grouping examples so that Linux (the primary NFS use case) is presented first, or at least equally, before Windows-specific guidance.
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-03 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, while the equivalent Linux (NFSv4.1) instructions are minimal and defer to another page. PowerShell is used as the primary example for feature registration, with Azure CLI only mentioned secondarily. There are no Linux command-line examples for managing ACLs or auditing, and Windows tools and workflows are described in more detail and appear first.
Recommendations
  • Provide equivalent, step-by-step instructions for setting Audit ACEs on NFSv4.1 volumes from a Linux host, including example commands (e.g., using setfacl or nfs4_setfacl).
  • Present Azure CLI commands before or alongside PowerShell commands for feature registration, to avoid implying Windows is the default platform.
  • Include screenshots or terminal output examples for Linux-based workflows, similar to the Windows GUI screenshots.
  • Explicitly mention and link to Linux tools for managing ACLs and auditing, not just refer to another documentation page.
  • Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or use tabs to separate platform-specific instructions.
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-02 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 operations, referencing Windows-specific tools and policies (such as Group Policy and registry keys), and omitting equivalent Linux/Unix commands or tools for managing Kerberos, LDAP, or AD integration. Windows terminology and tools are introduced first or exclusively, and there are no examples or guidance for Linux administrators who may need to interact with AD or configure Kerberos/NFS integration from non-Windows environments.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using 'kinit', 'ktutil', 'adcli', or 'realm' for Kerberos/AD integration) alongside PowerShell commands.
  • Reference and explain Linux/Unix tools and configuration files (such as /etc/krb5.conf, /etc/sssd/sssd.conf, or /etc/nsswitch.conf) where relevant, especially for NFS and Kerberos setup.
  • Include guidance for managing Kerberos encryption types and LDAP settings on Linux systems, not just via Windows Group Policy or registry.
  • Clarify which steps are required or different for Linux-based clients or administrators, especially in sections discussing SMB, NFS, and dual-protocol volumes.
  • Add troubleshooting tips and best practices for Linux environments, including how to verify AD connectivity, Kerberos ticket acquisition, and LDAP queries from Linux hosts.
  • Where screenshots or UI steps are shown, note any differences for Linux-based management tools or CLI workflows.
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-02 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, while Linux/NFS instructions are minimal and refer users elsewhere. Feature registration examples use Azure PowerShell by default, with Azure CLI only mentioned secondarily. There are no Linux command-line examples for setting audit ACEs, and Windows administration tools are referenced first and in more detail.
Recommendations
  • Provide equivalent, step-by-step instructions for setting Audit ACEs on NFSv4.1 volumes from a Linux client, including example commands (e.g., using setfacl or nfs4_setfacl).
  • When describing feature registration, present both Azure PowerShell and Azure CLI examples side-by-side, or default to CLI for cross-platform parity.
  • Avoid referring to 'Windows administration host' as the default; instead, clarify that either Windows or Linux administration hosts can be used, depending on the protocol/security style.
  • Include screenshots or terminal output for Linux-based workflows, similar to the Windows GUI screenshots provided.
  • Explicitly state that all operations can be performed from both Windows and Linux where applicable, and provide links to relevant Linux documentation or tools.
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-02 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only Azure PowerShell examples for registering and unregistering the feature, with Azure CLI mentioned only as an aside. There are no Linux shell (bash) or cross-platform CLI examples shown, and the PowerShell commands are presented first and in detail, which may disadvantage Linux users or those who prefer CLI tools.
Recommendations
  • Provide full Azure CLI (az) command examples alongside PowerShell, not just as a mention or link.
  • Consider listing Azure CLI (cross-platform) commands first or in parallel with PowerShell to avoid Windows-first bias.
  • Explicitly state that both PowerShell and CLI methods are supported, and clarify which is recommended for Linux/macOS users.
  • If relevant, include bash script examples for automation on Linux.
  • Ensure screenshots and UI references are not Windows-specific unless necessary.
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-02 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page generally maintains a neutral stance between Windows and Linux, especially in the context of NFS, which is predominantly a Unix/Linux protocol. However, in the section addressing performance issues when accessing NFS volumes from Windows clients, only Windows-specific tools and PowerShell commands are provided, with no equivalent Linux troubleshooting or configuration examples. This creates a 'powershell_heavy' and 'windows_tools' bias. Additionally, the absence of Linux examples in this context ('missing_linux_example'), and the fact that the only detailed mounting example is for Windows, may give the impression of 'windows_first' bias.
Recommendations
  • For every Windows-specific example (such as PowerShell commands or mount instructions), provide equivalent Linux commands (e.g., using mount, /etc/fstab, or nfs-utils).
  • In the section about improving folder lookup performance, add troubleshooting steps or configuration tips for Linux NFS clients, such as adjusting mount options or client-side caching.
  • Where Windows tools or patterns are mentioned, ensure Linux tools (e.g., nfsstat, showmount, or systemd mount units) are also referenced.
  • If a section is only relevant to Windows (such as CaseSensitiveLookup), clarify this and, if possible, provide a parallel section for Linux users, even if just to state that the issue does not apply.
  • Review all examples and ensure Linux is not omitted, especially since NFS is most commonly used in Linux/Unix environments.
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-02 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 before Linux (NFS) client instructions, with more detailed steps and screenshots for Windows (including both GUI and command-line methods). Windows-specific tools and patterns (File Explorer, 'dir' command) are described in detail, while the Linux section is shorter and only mentions the 'df' command. The REST API section references PowerShell specifically, but does not mention Linux scripting or tools.
Recommendations
  • Present Windows and Linux client instructions in parallel or alternate the order to avoid always listing Windows first.
  • Expand the Linux section to include both GUI (if applicable, e.g., GNOME Files or KDE Dolphin) and command-line methods, similar to the Windows section.
  • Provide equivalent Linux shell commands for all Windows command-line examples (e.g., show both 'dir' and 'df' outputs side by side).
  • In the REST API section, mention Linux scripting options (e.g., curl, bash, Python) alongside PowerShell.
  • Ensure screenshots and step-by-step instructions are balanced between Windows and Linux 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-02 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell as a primary tool for snapshot management and automation, and by referencing Windows-centric scripting (PowerShell) before or instead of Linux/Unix equivalents. There are no explicit Linux/Unix command-line examples (such as Bash or shell scripts), and the examples and tooling references (e.g., PowerShell cmdlets) are not balanced with Linux-native alternatives. While the documentation mentions NFS and SMB, which are cross-platform, the operational guidance and scripting focus is skewed toward Windows tools.
Recommendations
  • Provide Linux/Unix CLI examples (e.g., Bash scripts using Azure CLI) alongside or before PowerShell examples.
  • Mention and demonstrate Linux-native tools (such as shell scripting with az CLI) for snapshot management and automation.
  • Ensure that scripting and automation sections include parity for both Windows (PowerShell) and Linux (Bash/shell) environments.
  • Where possible, use cross-platform tools (like Azure CLI) as the primary example, and reference platform-specific tools (PowerShell, Bash) as alternatives.
  • Explicitly state that all features are accessible from both Windows and Linux environments, and provide links or references to relevant Linux documentation.
GitHub Create Pull Request
← Previous Page 18 of 36 Next →