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 401-425 of 896 flagged pages
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-cool-access.md ...main/articles/azure-netapp-files/manage-cool-access.md
High Priority View Details →
Scanned: 2025-08-10 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 Azure PowerShell commands as the primary example for feature registration, with Azure CLI (cross-platform) commands only mentioned in passing and without explicit usage examples. There are no Linux- or macOS-specific instructions or screenshots, and the UI instructions reference right-click actions, which are more typical of Windows environments. No Linux shell or bash equivalents are shown for command-line operations.
Recommendations
  • Provide explicit Azure CLI (az) command examples alongside PowerShell for all registration and configuration steps, including sample output.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide bash/zsh shell usage examples where appropriate.
  • Avoid UI instructions that assume a Windows-style right-click; instead, describe actions in a platform-neutral way (e.g., 'open the context menu for the capacity pool').
  • Include screenshots or instructions that are not specific to Windows UI conventions.
  • Add a section or callout for Linux/macOS users, highlighting any differences or confirming parity.
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-10 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 the Windows GUI, referencing Windows administration hosts, and using Azure PowerShell cmdlets as the primary example for feature registration. While Linux/NFS is mentioned, equivalent step-by-step instructions for setting Audit ACEs on Linux are missing, and the documentation does not provide Linux CLI or GUI examples for these tasks. Azure CLI is mentioned only as an alternative, not the primary method.
Recommendations
  • Provide step-by-step instructions for setting Audit ACEs on NFSv4.1 volumes from a Linux client, including example commands (e.g., using nfs4_setfacl).
  • Include Linux CLI examples for registering the feature (using az CLI) alongside or before PowerShell examples.
  • Balance the order of presentation so that Linux/NFS instructions are given equal prominence to Windows/SMB instructions.
  • Reference common Linux tools and patterns where appropriate, not just Windows tools and workflows.
  • Ensure all key workflows (enabling/disabling logs, setting permissions) have both Windows and Linux examples.
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-09 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 bash examples, and the PowerShell examples are 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 context.
  • Present both PowerShell and CLI examples in parallel or in separate tabs to ensure parity.
  • Explicitly mention that all commands can be run from any OS where Azure CLI is available, not just Windows.
  • Include bash shell examples for interacting with Azure CLI, especially for Linux users.
  • Avoid assuming PowerShell as the default interface; clarify that both PowerShell and CLI are supported and provide equal guidance for both.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/cross-region-replication-create-peering.md ...etapp-files/cross-region-replication-create-peering.md
High Priority View Details →
Scanned: 2025-08-09 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 Azure PowerShell commands as the primary example for feature registration and status checking, mentioning Azure CLI only secondarily and without explicit command examples. There are no Linux-specific instructions, screenshots, or terminal examples, and the workflow assumes use of the Azure Portal or PowerShell, which are more familiar to Windows users.
Recommendations
  • Provide Azure CLI command examples (e.g., 'az feature register', 'az feature show') alongside or before PowerShell examples, with full syntax and sample output.
  • Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and clarify any platform-specific differences.
  • Include screenshots or terminal snippets from non-Windows environments where applicable.
  • Balance the order of presentation so that CLI and PowerShell are given equal prominence, or alternate which is shown first.
  • Add a section or callout for Linux/macOS users, especially for command-line tasks, to ensure parity and inclusivity.
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-08-09 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell commands are presented prominently and in detail, often before or alongside Azure CLI examples. The registration and feature management sections use PowerShell as the primary example, with Azure CLI mentioned as an alternative. There is no mention of Linux-specific tools, shells, or workflows, and the PowerShell examples assume a Windows environment. The documentation does not provide explicit Linux shell (bash) examples or guidance for Linux users, and the use of PowerShell is assumed as a default for scripting and automation.
Recommendations
  • Provide explicit bash/Linux shell examples for all command-line operations, especially for Azure CLI commands.
  • When referencing PowerShell, clarify that Azure CLI commands can be run natively on Linux/macOS and provide syntax examples in bash.
  • Reorder sections so that Azure CLI (which is cross-platform) examples appear before PowerShell, or present them in parallel tabs.
  • Avoid assuming the use of PowerShell as the default scripting environment; mention that both PowerShell and bash are supported for Azure CLI.
  • Include notes or callouts for Linux/macOS users regarding any platform-specific considerations.
  • Where possible, use neutral language such as 'command line' or 'terminal' instead of 'PowerShell' when referring to general command execution.
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-09 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is generally balanced in its protocol descriptions, but there are subtle Windows biases. SMB is described as 'primarily used with Windows clients', and Windows/Active Directory tools and patterns are referenced more frequently and with more official support than their Linux equivalents. Linux (Samba) SMB support is mentioned as unofficial. There are no concrete Linux command-line examples for SMB, and Active Directory is presented as the default identity management solution, with LDAP as a secondary option. The only example command given is for NFS (rpcinfo), but there are no equivalent SMB/Linux commands or configuration examples.
Recommendations
  • Provide Linux/Samba command-line examples for accessing SMB shares, not just NFS.
  • Explicitly mention and provide examples for configuring Linux clients (using Samba/cifs-utils) to access SMB shares, including any caveats.
  • When discussing identity management, give equal weight to LDAP and Active Directory, and clarify support levels for both.
  • Avoid language that frames Windows/Active Directory as the default or primary solution; instead, present both Windows and Linux/UNIX approaches side by side.
  • Where possible, add Linux-focused troubleshooting steps or references for SMB access.
  • Clarify the support status and best practices for Linux SMB clients, and provide links to relevant documentation.
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-09 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-centric bias by providing only Windows/PowerShell command examples for Active Directory management, referencing Windows-specific tools and policies (such as Group Policy and registry keys), and omitting equivalent Linux or cross-platform instructions for managing AD connections or Kerberos settings. Windows terminology and tools are introduced first and often exclusively, with little to no mention of how to perform similar tasks from Linux environments.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using 'ldapmodify', 'kadmin', or 'adcli') for managing Kerberos encryption types and AD user properties.
  • Include instructions or references for configuring Kerberos and LDAP settings from Linux clients, especially for NFS and dual-protocol scenarios.
  • Mention and link to cross-platform tools (such as Samba, sssd, or realmd) where appropriate.
  • Balance the order of presentation so that Linux and Windows tools are introduced together, or in a neutral order, rather than always presenting Windows first.
  • Clarify which steps are required or optional for Linux-based environments, and provide troubleshooting tips for common Linux AD integration issues.
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-09 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 prioritizing Windows-based tools and workflows, especially in sections about setting SACLs and registering features. Windows (and PowerShell) instructions are provided in detail, while Linux/NFS instructions are either referenced externally or lack step-by-step guidance. Windows terminology and screenshots dominate, and Linux equivalents are not given equal prominence or detail.
Recommendations
  • Provide step-by-step Linux/NFS instructions for setting Audit ACEs directly in the documentation, not just as a link.
  • Include command-line examples for Linux (e.g., using nfs4_setfacl or similar tools) alongside Windows GUI instructions.
  • When registering features, show both Azure PowerShell and Azure CLI commands side by side, with equal detail and prominence.
  • Use neutral language and structure (e.g., parallel tabs or sections) to present Windows and Linux workflows equally.
  • Add Linux screenshots or terminal output examples where appropriate, not just Windows GUI screenshots.
  • Review all sections to ensure Linux/NFS administrators can follow the documentation without needing to consult external links.
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-09 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It provides 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 only explicit example for editing POSIX attributes is via Windows GUI tools, and the section on accessing the Attribute Editor is exclusively for Windows. Linux client configuration is referenced only via a link, with no inline examples or parity in attribute management. Additionally, Windows terminology and tools are mentioned first or exclusively in several sections.
Recommendations
  • Include instructions and examples for managing POSIX attributes using Linux tools such as ldapmodify, ldapvi, or command-line utilities (e.g., ldapadd, ldapmodify) alongside the Windows MMC snap-in.
  • Provide screenshots or command-line examples for editing LDAP attributes from a Linux environment.
  • Balance the order of presentation so that Linux and Windows tools are introduced together or alternate which is mentioned first.
  • Clarify that attribute management can be performed from non-Windows systems and provide references or links to relevant Linux documentation.
  • Where possible, avoid assuming the administrator is using a Windows environment for directory management.
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-09 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 generally maintains a neutral tone between platforms, but in the section addressing NFS access from Windows clients, only Windows-specific tools and PowerShell commands are provided. There are no equivalent Linux examples or troubleshooting steps for Linux NFS clients, and the Windows example is presented without parity. This creates a subtle Windows bias, especially in the practical guidance for mounting and configuring NFS volumes.
Recommendations
  • For every Windows-specific example (such as PowerShell commands and mount instructions), provide equivalent Linux commands (e.g., mount command-line usage, relevant /etc/fstab entries, or troubleshooting steps).
  • When discussing client-side configuration (such as enabling CaseSensitiveLookup), include Linux-specific configuration tips or common issues and their resolutions.
  • Ensure that troubleshooting sections address both Windows and Linux clients equally, or clarify when an issue is specific to one platform.
  • Where possible, present Linux and Windows examples side-by-side, or alternate which platform is presented first to avoid the perception of prioritizing Windows.
  • Review all sections for implicit assumptions about the client OS and explicitly mention when guidance is platform-specific.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-cool-access.md ...main/articles/azure-netapp-files/manage-cool-access.md
High Priority View Details →
Scanned: 2025-08-09 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 Azure PowerShell examples as the primary (and only) command-line instructions for feature registration, with Azure CLI commands mentioned only secondarily and without explicit examples. There are no Linux-specific instructions, screenshots, or CLI walkthroughs, and the UI instructions use Windows-centric terminology (e.g., 'right-click'), which may not be as intuitive for Linux users. No Linux shell or cross-platform command-line examples are provided.
Recommendations
  • Provide explicit Azure CLI command examples (e.g., 'az feature register ...') alongside PowerShell, not just as a mention.
  • Include Linux shell (bash) equivalents for all command-line operations.
  • Use neutral UI language (e.g., 'select the options menu' instead of 'right-click') to avoid Windows-centric terminology.
  • Add screenshots or instructions that are clearly applicable to both Windows and Linux environments.
  • Where possible, clarify that all operations can be performed from any supported OS, and link to cross-platform CLI installation guides.
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-07 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-centric bias by providing only PowerShell and Windows tool examples for Active Directory management, referencing Windows-specific registry keys and Group Policy settings, and omitting equivalent Linux or cross-platform instructions. Azure CLI is mentioned, but only as an alternative to PowerShell, and no Linux-native AD management tools or workflows are discussed. The documentation assumes a Windows AD DS environment and does not address Linux-based AD integration or management scenarios.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using 'realm', 'adcli', or 'ldapmodify') for managing AD user attributes and Kerberos encryption types.
  • Include guidance for managing Active Directory from Linux systems, such as using Samba tools or openldap utilities.
  • When referencing PowerShell or Windows tools, offer parallel instructions for Azure CLI, Bash, or other cross-platform tools where possible.
  • Explicitly mention any platform limitations or prerequisites (e.g., if certain features require Windows-only tools) and suggest workarounds or alternatives for Linux administrators.
  • Add examples or links for integrating Azure NetApp Files with Linux-based AD environments or with non-Windows clients.
  • Reorder sections or examples to present cross-platform or platform-neutral approaches before Windows-specific instructions where feasible.
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-07 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. The PowerShell examples are presented first and in detail, while no explicit Linux shell or cross-platform CLI examples are shown. This may make it less accessible for Linux users or those who prefer CLI tools.
Recommendations
  • Provide full Azure CLI command examples alongside PowerShell, including registration, status checking, and unregistration steps.
  • Present CLI (az) examples before or alongside PowerShell to avoid implying a Windows-first workflow.
  • Clarify that all actions can be performed from any platform using Azure CLI, and provide shell-friendly command blocks.
  • Consider including screenshots or instructions from the Azure Portal for a platform-neutral approach.
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-07 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is generally neutral and focused on NFS, which is primarily a Linux/UNIX protocol. However, there is a section ('When I try to access NFS volumes through a Windows client...') that provides only Windows-specific troubleshooting and PowerShell commands, without equivalent Linux guidance. Additionally, Windows tools and patterns (PowerShell, Mount command with Windows syntax) are mentioned exclusively in that section, and the Windows client scenario is given its own FAQ entry, which may suggest a slight prioritization of Windows use cases.
Recommendations
  • For every Windows-specific example or troubleshooting step, provide an equivalent Linux example (e.g., how to enable case-sensitive lookups or optimize NFS performance on Linux clients).
  • When mentioning tools or commands (such as PowerShell or the Windows Mount command), also mention the analogous Linux tools (e.g., mount command with appropriate options).
  • If a Windows-specific FAQ is included, consider adding a parallel FAQ for common Linux client issues or optimizations to balance the coverage.
  • Where possible, present Linux and Windows instructions side by side or in parallel sections to avoid the perception of platform prioritization.
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-07 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 as the default or primary use case, with Linux/NFS support described as secondary. Windows terminology (NTFS, Active Directory, SID, NTLM) and tools are referenced without Linux equivalents, and official support is only noted for Windows/macOS SMB clients, not Linux. There are no Linux command-line examples for SMB access or configuration, and Linux tools/patterns (e.g., Samba, mount.cifs) are not described in parity with Windows tools.
Recommendations
  • Provide Linux/Samba command-line examples for SMB access and configuration, similar to the Windows/Active Directory focus.
  • Explicitly mention and provide parity for Linux tools and patterns (e.g., Samba, mount.cifs, Linux ACLs) wherever Windows tools (NTFS, SID, NTLM) are referenced.
  • When discussing dual-protocol and identity mapping, include Linux-centric workflows and troubleshooting steps, not just Active Directory scenarios.
  • Clarify the support status and best practices for Linux SMB clients, and provide links to relevant Linux documentation.
  • Balance the order of presentation so that Linux/NFS and Windows/SMB are introduced and described with equal prominence, rather than Windows/SMB first or exclusively.
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-07 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 providing detailed instructions and screenshots for managing LDAP POSIX attributes using Windows tools (Active Directory Users and Computers MMC snap-in), while omitting equivalent Linux-based methods. The only explicit step-by-step example for attribute management is for Windows, and there are no Linux command-line or GUI alternatives mentioned. Additionally, Windows terminology and tools are referenced first or exclusively in several sections, and Linux client configuration is relegated to a link rather than being included inline.
Recommendations
  • Include Linux-based examples for managing LDAP POSIX attributes, such as using ldapmodify, ldapadd, or tools like Apache Directory Studio.
  • Provide step-by-step instructions or command-line examples for editing user and group attributes on Linux LDAP servers (e.g., OpenLDAP).
  • Balance the documentation by presenting both Windows and Linux methods side-by-side where relevant, especially in sections on attribute management and client configuration.
  • Add screenshots or code snippets for Linux tools or commands to match the level of detail given for Windows.
  • When referencing tools or workflows, avoid defaulting to Windows-first language; instead, introduce both Windows and Linux options together.
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-07 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 tools (File Explorer, dir command). Windows-specific tools and UI patterns are described in greater detail, while Linux instructions are more concise. The REST API section also references PowerShell specifically, without mentioning Linux scripting equivalents.
Recommendations
  • Alternate the order of Windows and Linux sections, or present them in parallel to avoid 'Windows first' bias.
  • Provide equally detailed instructions and screenshots for Linux tools (e.g., showing GNOME/KDE file manager properties or terminal output).
  • Mention Linux scripting or automation options (e.g., Bash scripts, cron jobs) alongside PowerShell in the REST API section.
  • Ensure that Linux commands and tools are given parity in explanation and visual aids.
  • Where possible, use neutral language 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/manage-file-access-logs.md ...articles/azure-netapp-files/manage-file-access-logs.md
High Priority View Details →
Scanned: 2025-08-07 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. Feature registration examples are shown first in Azure PowerShell, with Azure CLI (cross-platform) only mentioned as an alternative. There are no explicit Linux command-line examples for setting audit ACEs or managing file access logs, and Windows tools and patterns are prioritized or exclusively described.
Recommendations
  • Provide step-by-step command-line examples for setting Audit ACEs on NFSv4.1 volumes using Linux tools (e.g., setfacl, nfs4_setfacl).
  • Present Azure CLI examples alongside or before PowerShell examples for feature registration and management tasks.
  • Balance the detail level between Windows and Linux instructions, ensuring both platforms have clear, actionable steps.
  • Include screenshots or terminal output for Linux-based workflows, similar to the Windows GUI walkthrough.
  • Explicitly mention and link to Linux tools and commands where Windows tools are referenced.
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-07 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by listing PowerShell as a primary tool for snapshot management alongside Azure Portal, REST API, and Azure CLI, but does not provide Linux-specific command-line examples or mention Linux-native tools. While the Azure CLI is cross-platform, there is no explicit guidance or examples for Linux users, and PowerShell is mentioned before any Linux alternatives. No Linux/Unix shell (bash) examples or references to Linux-specific patterns are present, and the only scripting example links to a SQL Server (Windows-centric) use case.
Recommendations
  • Add explicit Linux/Unix shell (bash) command examples for snapshot management using Azure CLI.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample commands in a Linux shell context.
  • Balance the mention of PowerShell with equivalent bash or shell script examples for common snapshot tasks.
  • Include references or links to Linux/Unix documentation or community resources for managing Azure NetApp Files snapshots.
  • If scripting is discussed, provide at least one example using bash or Python, not just PowerShell or Windows-centric 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-06 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 by providing detailed instructions and screenshots for managing LDAP POSIX attributes using Windows-only tools (Active Directory Users and Computers MMC snap-in), and by describing access steps exclusively for Windows systems. There are no equivalent instructions or examples for managing POSIX attributes from Linux or cross-platform tools. Additionally, Windows terminology and tools are mentioned first or exclusively in several sections, while Linux/NFS client configuration is referenced only via a link, without in-page guidance or parity in detail.
Recommendations
  • Add equivalent instructions for managing LDAP POSIX attributes using Linux tools (e.g., ldapmodify, ldapadd, or Apache Directory Studio) with example commands and screenshots.
  • Provide cross-platform guidance for accessing and editing LDAP attributes, including both Windows and Linux environments.
  • Ensure that examples and tool references are balanced between Windows and Linux, or presented in parallel where possible.
  • Include in-page, step-by-step instructions for configuring NFS clients on Linux, not just a link to another page.
  • Where Windows-specific features or tools are discussed, clarify Linux alternatives or note any limitations.
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-06 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 Windows-specific instructions for mounting NFS volumes and troubleshooting performance, but does not provide equivalent Linux command examples or troubleshooting steps. Windows tools and patterns (e.g., Set-NfsClientConfiguration, Mount command with Windows syntax) are mentioned exclusively in the relevant section, and Linux mounting is only referenced via a link, not with inline examples. This creates a bias toward Windows users and leaves Linux administrators without direct, actionable guidance.
Recommendations
  • For every Windows-specific example (such as PowerShell commands and mount syntax), provide an equivalent Linux example (e.g., mount command with NFS options, editing /etc/fstab).
  • When discussing troubleshooting or configuration steps, present Linux and Windows instructions in parallel, or lead with Linux if the context is NFS (which is more commonly used on Linux).
  • Avoid mentioning only Windows tools or patterns; always include Linux-native tools and workflows, especially for NFS topics.
  • Where links to further documentation are provided, supplement them with at least one inline Linux example for quick reference.
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-05 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, referencing Windows-specific tools and policies (e.g., Group Policy, registry keys), and omitting equivalent Linux or cross-platform methods for managing AD connections. Windows terminology and tools are introduced first and often exclusively, with no mention of Linux-based AD management or integration approaches.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using 'ldapmodify', 'kinit', 'realm', or 'adcli') for managing Kerberos encryption types and AD user properties.
  • Include references to cross-platform tools (such as Samba, sssd, or realmd) for AD integration and configuration.
  • Document how to perform AD-related administrative tasks from Linux systems, not just via PowerShell or Windows Group Policy.
  • Clarify which features or steps are Windows-only and offer Linux alternatives where possible.
  • Add guidance for Linux administrators on troubleshooting and configuring Azure NetApp Files AD connections from non-Windows environments.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-data-migration-protection.md ...es/azure-netapp-files/faq-data-migration-protection.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 mentions both Linux (rsync) and Windows (robocopy) tools for file-based migration, but the examples and tool references are not fully balanced. Robocopy (a Windows tool) is specifically called out for SMB workloads, while rsync is mentioned for NFS. There are no explicit Linux-native SMB migration tool examples (such as smbclient or cifs-utils), and the only SMB example is robocopy, which is Windows-specific. Additionally, the order of presentation sometimes puts Windows tools or patterns first, and there is a lack of parity in example depth for Linux-based SMB migration.
Recommendations
  • Add Linux-native SMB migration tool examples (e.g., smbclient, cifs-utils, or Linux rsync with SMB mounts) alongside robocopy for SMB workloads.
  • Ensure that both Windows and Linux tools are presented together and with equal detail for both NFS and SMB scenarios.
  • Where possible, provide cross-platform command examples or clarify the OS context for each tool.
  • Consider including a table or section explicitly comparing migration tool options for both Windows and Linux 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-05 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 Bash examples, and the PowerShell commands are presented first and in detail, which may disadvantage users on Linux or macOS platforms.
Recommendations
  • Provide equivalent Azure CLI command examples alongside or before PowerShell commands, as Azure CLI is cross-platform and commonly used on Linux.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI, and provide step-by-step CLI instructions.
  • Include example commands in Bash syntax for Linux users, especially for checking feature registration and status.
  • Clarify that PowerShell is not required and that the Azure Portal and CLI are fully supported for these operations.
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-05 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page is generally neutral and focused on NFS, which is primarily a Unix/Linux protocol. However, there is a notable Windows bias in the section addressing NFS access from Windows clients: only Windows-specific (PowerShell) commands and tools are provided, with no equivalent Linux examples. The Windows client troubleshooting section appears before any Linux troubleshooting, and the only explicit command-line examples are for Windows/PowerShell. There are no Linux-specific troubleshooting or mounting examples, which may disadvantage Linux users.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., mount commands, NFS client configuration) wherever Windows/PowerShell examples are given.
  • Include Linux troubleshooting steps for common NFS issues, similar to the Windows client troubleshooting section.
  • When discussing configuration or troubleshooting, present Linux and Windows instructions in parallel or with equal prominence.
  • Avoid assuming Windows as the default client environment in NFS documentation, given NFS's strong association with Unix/Linux.
  • Where possible, link to both Linux and Windows documentation for mounting and configuring NFS volumes.
GitHub Create Pull Request
← Previous Page 17 of 36 Next →