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 326-350 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-29 00:01
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 primarily in the registration steps for enabling cool access features. All command-line examples use Azure PowerShell cmdlets, which are most familiar to Windows users, and these are presented before mentioning Azure CLI alternatives. There are no explicit Linux/Unix shell examples, and the Azure CLI commands are only referenced in text, not shown as full command blocks. The UI instructions also use Windows-centric terminology (e.g., 'right-click'), which may not be as intuitive for Linux users.
Recommendations
  • Provide full Azure CLI command examples (e.g., 'az feature register ...') alongside PowerShell, formatted as code blocks, not just referenced in text.
  • When listing command-line options, present Azure CLI (cross-platform) examples before or alongside PowerShell to avoid Windows-first bias.
  • Clarify that both Azure PowerShell and Azure CLI are cross-platform, but that Azure CLI is often preferred on Linux/macOS.
  • Replace or supplement 'right-click' UI instructions with alternatives suitable for non-Windows environments (e.g., 'select the context menu for the item').
  • Explicitly mention that all steps can be performed from Linux/macOS as well as Windows, and provide any necessary prerequisites or environment notes for non-Windows users.
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-29 00:01
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 to another page. The (commented-out) feature registration example uses Azure PowerShell first, with Azure CLI only mentioned secondarily. There are no Linux command-line examples for setting audit ACEs or SACLs, and Windows administration hosts and tools are referenced explicitly and in 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 nfs4_setfacl).
  • When describing feature registration, present Azure CLI and PowerShell examples side-by-side or in parallel, not with PowerShell first.
  • Avoid referring to 'Windows administration host' exclusively; mention 'Linux administration host' or 'Linux client' where appropriate.
  • Include screenshots or command-line examples for Linux-based workflows, not just Windows GUI.
  • Ensure that all procedures (enabling/disabling logs, setting ACLs) have both Windows and Linux instructions where applicable.
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-29 00:01
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, mentioning it alongside Azure CLI and REST API, but not providing any Linux/Unix shell or scripting examples. The ordering of tools often places PowerShell before or alongside cross-platform options, and there are no explicit Linux/Unix command-line examples or references to Linux-native tooling or scripting patterns. This may make Linux users feel less directly supported or require them to infer how to use the service from Windows-centric instructions.
Recommendations
  • Add explicit Linux/Unix shell (bash) examples for snapshot management using Azure CLI, demonstrating common Linux scripting patterns.
  • When listing tools, alternate or randomize the order of Azure CLI and PowerShell, or list Azure CLI first to reflect its cross-platform nature.
  • Include references or links to Linux/Unix automation and scripting guides for Azure NetApp Files.
  • Provide sample scripts or walkthroughs for both Windows (PowerShell) and Linux (bash) environments.
  • Clarify that all features are available and supported on both Windows and Linux clients, and highlight any OS-specific considerations where relevant.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/understand-data-encryption.md ...icles/azure-netapp-files/understand-data-encryption.md
High Priority View Details →
Scanned: 2025-08-29 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows/SMB and Active Directory scenarios, referencing Windows-specific tools and features (e.g., Group Policy, registry settings), and providing detailed explanations for Windows-centric encryption mechanisms. Linux/NFS examples are present but less detailed, and there are no explicit Linux command-line or configuration examples. LDAP and Kerberos sections also focus on Microsoft Active Directory, with little mention of non-Windows LDAP/Kerberos environments.
Recommendations
  • Provide parallel Linux/NFS examples and configuration steps where Windows/SMB examples are given, including relevant Linux commands or configuration file snippets.
  • When discussing LDAP, include examples and notes for common Linux LDAP servers (e.g., OpenLDAP) and clients, not just Active Directory.
  • Balance the order of presentation: introduce NFS/Linux scenarios before or alongside SMB/Windows scenarios, rather than always after.
  • Reference Linux tools (e.g., kinit, nfs-utils, sssd, ldap-utils) and configuration files (e.g., /etc/krb5.conf, /etc/nfsmount.conf) where appropriate.
  • Clarify which features and encryption options are available and supported for both Windows and Linux clients, and note any differences.
  • Add troubleshooting and best practices sections for Linux environments, similar to the Windows/SMB performance and security notes.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/application-volume-group-considerations.md ...etapp-files/application-volume-group-considerations.md
High Priority View Details →
Scanned: 2025-08-28 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. Specifically, it references Windows-specific documentation for creating Proximity Placement Groups (PPGs) (linking to /azure/virtual-machines/windows/proximity-placement-groups-portal) without mentioning or linking to equivalent Linux documentation or workflows. There are no explicit PowerShell or Windows command examples, but the absence of Linux-specific guidance or parity in referenced materials may disadvantage Linux users. No Linux tools, commands, or portal links are provided, and the only example for PPG creation is Windows-focused.
Recommendations
  • Include links to both Windows and Linux documentation for tasks such as creating Proximity Placement Groups (e.g., /azure/virtual-machines/linux/proximity-placement-groups-portal).
  • Where referencing Azure portal workflows, clarify that the steps are applicable to both Windows and Linux VMs, or provide separate instructions if there are differences.
  • Add examples or notes relevant to Linux-based SAP HANA deployments, especially in sections discussing VM pinning, PPGs, and availability sets.
  • Audit all external links and references to ensure Linux parity and avoid Windows-first impressions.
  • If any CLI or PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are provided.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md ...-netapp-files/azure-netapp-files-create-volumes-smb.md
High Priority View Details →
Scanned: 2025-08-28 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by providing only Windows-based instructions and tools for managing SMB volumes, such as using the Windows Security tab and Microsoft Management Console (MMC) for permissions. There are no Linux or cross-platform examples for accessing or managing SMB shares, and Windows terminology and tools are referenced exclusively or before any mention of Linux equivalents.
Recommendations
  • Include instructions and examples for managing SMB share and NTFS permissions from Linux clients, such as using 'smbclient', 'smbcacls', or 'setfacl'.
  • Provide Linux command-line examples for mounting SMB volumes (e.g., using 'mount -t cifs' or 'smbclient') alongside or before Windows examples.
  • Mention Linux-compatible tools and workflows for SMB management, not just Windows MMC or File Explorer.
  • Clarify which features (such as SMB3 encryption or access-based enumeration) are supported and how to configure them from Linux clients.
  • Add screenshots or terminal outputs from Linux environments where appropriate.
  • Ensure that all steps referencing Windows tools have Linux equivalents or explicitly state if a feature is only available via Windows.
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-28 00:01
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 in its command-line examples and tooling. PowerShell commands are shown first and in detail for feature registration, with Azure CLI commands only mentioned secondarily and without explicit examples. There are no Linux-specific instructions or screenshots, and the workflow descriptions (e.g., 'right-click') assume a GUI experience typical of Windows environments. No Linux or cross-platform command-line examples are provided for key operations.
Recommendations
  • Provide explicit Azure CLI command examples (e.g., 'az feature register', 'az feature show') alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Include Linux-specific instructions or notes where relevant, especially for command-line operations.
  • Avoid GUI instructions that assume a Windows environment (such as 'right-click') or supplement them with equivalent CLI steps.
  • Ensure screenshots and workflow descriptions are platform-neutral or provide alternatives for Linux users.
  • Where possible, use cross-platform terminology and tools as the primary examples, with Windows-specific tools as secondary.
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-28 00:01
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 the way it presents tooling and examples. In the 'Ways to create snapshots' section, PowerShell is listed as a primary tool alongside Azure Portal, REST API, and Azure CLI, but there is no mention of Linux-specific tools or shell scripting. The only scripting example linked is for SQL Server (a Windows-centric workload). There are no explicit Linux/Bash examples or references to Linux-native patterns, and PowerShell is mentioned before any Linux alternatives. This could make Linux users feel less directly supported.
Recommendations
  • Include explicit Bash/Unix shell examples for snapshot management using Azure CLI, especially for common Linux administration scenarios.
  • When listing tools, present Azure CLI and REST API before PowerShell, or group them neutrally, to avoid the impression of Windows-first bias.
  • Add references or links to Linux scripting guides or examples for automating snapshot tasks.
  • If possible, provide sample scripts for both PowerShell and Bash in the documentation or in linked resources.
  • Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, to reinforce platform neutrality.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/understand-data-encryption.md ...icles/azure-netapp-files/understand-data-encryption.md
High Priority View Details →
Scanned: 2025-08-28 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows/SMB and Active Directory scenarios, referencing Windows-specific tools and security features (e.g., Group Policy, UNC hardening, Windows Server registry settings) without providing equivalent Linux or open-source alternatives. Examples and configuration guidance are almost exclusively Windows-centric, with little to no mention of Linux tools, commands, or client configuration steps. Linux/NFS encryption is discussed, but without practical configuration examples or parity in depth compared to Windows/SMB sections.
Recommendations
  • Provide Linux client configuration examples for NFS Kerberos encryption, including commands for setting up krb5, krb5i, and krb5p on common distributions.
  • Include Linux-based LDAP client configuration steps for enabling LDAP signing and StartTLS, such as using OpenLDAP tools and relevant configuration files.
  • When discussing SMB encryption, add guidance for SMB clients on Linux (e.g., using smbclient, mount.cifs with encryption options) and note any differences in support or configuration.
  • Balance references to Windows-specific tools (e.g., Group Policy, registry settings) with Linux equivalents or note when features are not available/can be configured differently on Linux.
  • Add troubleshooting and verification steps for both Windows and Linux clients to ensure encryption is active (e.g., using tcpdump, Wireshark, or relevant logs).
  • Explicitly state support and configuration differences for cross-platform environments, and provide links to Linux documentation where appropriate.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md ...-netapp-files/azure-netapp-files-create-volumes-smb.md
High Priority View Details →
Scanned: 2025-08-27 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for managing SMB permissions and shares using Windows tools (e.g., MMC, Windows SMB client). There are no Linux-based examples or guidance for accessing or managing SMB volumes from Linux clients, despite SMB being a cross-platform protocol. Windows terminology and workflows are prioritized, and Linux alternatives are not mentioned.
Recommendations
  • Include examples for accessing and mounting SMB volumes from Linux clients (e.g., using the 'mount -t cifs' command).
  • Provide instructions for managing SMB permissions from Linux, such as using 'smbclient', 'smbcacls', or 'setfacl' where appropriate.
  • Mention and demonstrate how to view or modify SMB share properties from Linux or cross-platform tools, not just Windows MMC.
  • Balance screenshots and walkthroughs to show both Windows and Linux client perspectives.
  • Clarify that SMB volumes can be accessed from non-Windows systems and link to relevant Linux documentation.
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-27 00:01
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 by listing PowerShell as a primary tool for snapshot management, mentioning it before Linux/Unix equivalents, and omitting explicit Linux/Unix shell or scripting examples. While Azure CLI and REST API are mentioned (which are cross-platform), the only command-line example linked is for PowerShell, and there are no bash or Linux-native workflow examples. This may make Linux users feel less directly supported or require them to infer Linux usage from Windows-centric instructions.
Recommendations
  • Add explicit Linux/bash command-line examples for snapshot management alongside PowerShell, especially in sections listing management methods.
  • When listing tools (Azure portal, REST API, CLI, PowerShell), alternate the order or explicitly note cross-platform parity (e.g., 'Azure CLI (Windows, Linux, macOS)').
  • Provide sample scripts or links for Linux environments (e.g., bash scripts using Azure CLI) similar to the PowerShell examples.
  • Reference Linux-native automation and scripting patterns (e.g., cron jobs with Azure CLI) where automation is discussed.
  • Ensure that any references to scripting or automation do not assume a Windows environment by default.
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-27 00:01
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 in the command-line examples for feature registration, as all code snippets use Azure PowerShell cmdlets (Register-AzProviderFeature, Get-AzProviderFeature) and are formatted as PowerShell. While Azure CLI is mentioned as an alternative, no CLI examples are provided inline, and no Linux/macOS-specific guidance or screenshots are present. The UI instructions also use Windows-centric terminology (e.g., 'right-click'), and there are no explicit Linux or cross-platform instructions or visuals.
Recommendations
  • Provide equivalent Azure CLI examples (e.g., 'az feature register', 'az feature show') alongside PowerShell for all feature registration and status-checking steps, with full command syntax and expected output.
  • Include notes or sections clarifying that all CLI commands can be run on Linux, macOS, and Windows, and provide platform-agnostic instructions.
  • Where UI instructions mention 'right-click', clarify how to perform the same action on macOS/Linux (e.g., 'right-click or use the context menu').
  • Add screenshots or notes that reflect the experience on non-Windows platforms, or state that the UI is consistent across platforms if applicable.
  • Consider a 'Platform requirements' or 'Cross-platform usage' section to explicitly address Linux/macOS users and ensure 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-27 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed, step-by-step instructions for setting SACLs (auditing) on SMB shares using the Windows GUI, while the equivalent Linux/NFS instructions are minimal and refer users to a separate page for details. The document also repeatedly refers to performing actions from a 'Windows administration host' and does not provide Linux command-line examples or GUI walkthroughs for NFS/UNIX environments. Windows tools and workflows are mentioned first and in more detail, while Linux guidance is less direct and less actionable.
Recommendations
  • Provide explicit, step-by-step instructions for setting Audit ACEs on NFSv4.1 volumes from a Linux client, including example commands (e.g., using nfs4_setfacl or setfacl).
  • Include Linux command-line examples for relevant tasks, such as configuring ACLs, in parity with the detailed Windows GUI steps.
  • Balance the order of presentation so that Linux/NFS instructions are given equal prominence and detail as Windows/SMB instructions.
  • Where possible, avoid referring users to external pages for Linux/NFS instructions if Windows instructions are included inline.
  • If GUI-based instructions are provided for Windows, consider providing equivalent instructions for popular Linux desktop environments or clarify that only command-line methods are available.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/understand-data-encryption.md ...icles/azure-netapp-files/understand-data-encryption.md
High Priority View Details →
Scanned: 2025-08-27 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows/SMB and Active Directory scenarios, referencing Windows-specific tools and features (such as Group Policy, registry settings, and Windows server-side configuration), and providing detailed explanations for Windows security mechanisms (e.g., UNC hardening, LDAP signing) without equivalent Linux or open-source examples. There is a lack of Linux/NFS client configuration guidance, and Linux tools or patterns are not mentioned or are only referenced after Windows equivalents.
Recommendations
  • Provide parallel Linux/NFS client configuration examples for encryption, such as how to enable and verify NFS Kerberos encryption on common Linux distributions.
  • Include references to Linux tools (e.g., sssd, nfs-utils, kinit, ldap-utils) and how they interact with Azure NetApp Files for encryption and authentication.
  • Balance the order of presentation so that Linux/NFS and Windows/SMB scenarios are given equal prominence, or alternate which is presented first.
  • Offer guidance on configuring LDAP signing and StartTLS from Linux/Unix clients and servers, not just Windows Active Directory.
  • Add troubleshooting tips and best practices for Linux environments, including packet capture examples using Linux tools (e.g., tcpdump, Wireshark on Linux).
  • Reference open-source documentation and standards (e.g., MIT Kerberos, OpenLDAP) alongside Microsoft documentation.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md ...etapp-files-mount-unmount-volumes-for-virtual-machines.md
High Priority View Details →
Scanned: 2025-08-26 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows instructions for mounting NFS volumes, but there are subtle biases. The Windows section is presented after Linux, but the Windows mounting process requires first mounting on a Linux/Unix VM and running chmod, which may not be familiar or accessible to Windows-only administrators. The Linux section is detailed with explicit mount command examples, while the Windows section lacks a full, step-by-step example (e.g., enabling NFS client, prerequisites). The Windows example references the 'Mount' command but does not provide parity in detail compared to Linux. There is also an assumption that users have access to a Linux/Unix system for initial setup, which may not be true for all Windows environments.
Recommendations
  • Provide a complete, standalone Windows workflow for mounting NFS volumes, including prerequisites (e.g., enabling NFS client feature in Windows), and any required permissions or configuration steps.
  • Offer alternative approaches for Windows-only environments that do not require a Linux/Unix VM for initial chmod operations, or clarify how to set permissions from Windows if possible.
  • Ensure that both Linux and Windows sections include equally detailed, step-by-step instructions and troubleshooting tips.
  • Include references to Windows-specific NFS documentation and tools in the same level of detail as Linux.
  • Consider adding a table comparing feature support and limitations for NFS on Linux vs. Windows to set clear expectations.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md ...-netapp-files/azure-netapp-files-create-volumes-smb.md
High Priority View Details →
Scanned: 2025-08-26 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools and workflows for managing SMB permissions (e.g., MMC, Windows Security tab), and by omitting Linux-based SMB client instructions or examples. All examples and screenshots are Windows-centric, and there is no mention of how to access or manage SMB volumes from Linux clients, despite SMB being cross-platform.
Recommendations
  • Include instructions and examples for accessing and managing SMB volumes from Linux clients, such as using smbclient, mount.cifs, or Nautilus.
  • Provide Linux command-line examples for mounting SMB shares and setting permissions (where applicable).
  • Mention Linux tools (e.g., smbclient, cifs-utils) alongside Windows tools when discussing SMB access and management.
  • Add screenshots or terminal output from Linux environments to balance the visual representation.
  • Clarify any differences or limitations when using SMB volumes from Linux clients, if applicable.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md ...-netapp-files/azure-netapp-files-create-volumes-smb.md
High Priority View Details →
Scanned: 2025-08-25 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for managing SMB permissions and shares using Windows tools (e.g., MMC, Windows SMB client). There are no examples or guidance for Linux clients or tools, even though SMB is cross-platform and Linux clients are commonly used. The documentation assumes Windows as the primary environment for SMB management and omits Linux equivalents or alternative methods.
Recommendations
  • Add instructions for managing SMB share and NTFS permissions from Linux clients, such as using smbclient, mount.cifs, or setfacl.
  • Include examples of mounting SMB volumes from Linux systems, referencing relevant commands and authentication methods.
  • When describing tools (e.g., MMC), mention Linux alternatives or clarify that similar operations can be performed from Linux with appropriate tools.
  • Ensure that both Windows and Linux client scenarios are covered in sections about access control, permissions, and share management.
  • Where possible, provide parity in screenshots and step-by-step guides for both platforms.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/whats-new.md ...ocs/blob/main/articles/azure-netapp-files/whats-new.md
High Priority View Details →
Scanned: 2025-08-25 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation for Azure NetApp Files demonstrates a mild Windows bias. Features and enhancements related to Windows technologies (such as SMB, Active Directory, and Windows File Explorer) are frequently mentioned, sometimes with more detail or prominence than their Linux/NFS counterparts. Several features are described primarily in the context of Windows clients or tools, and some security or access features are explained with reference to Windows behaviors. While Linux/NFS support is present and discussed, there are areas where Linux-specific examples, tools, or workflows are less emphasized or missing.
Recommendations
  • Ensure that for every Windows/SMB example or feature description, an equivalent Linux/NFS example or workflow is provided, including command-line examples where appropriate.
  • When describing features like Access-based Enumeration or non-browsable shares, include explicit details on how these behave or can be managed from Linux/NFS clients, not just Windows clients.
  • Avoid language that frames Windows tools or behaviors as the default (e.g., 'Windows client hides the folder'), and instead present both Windows and Linux behaviors in parallel.
  • For troubleshooting and management tools, mention or provide Linux-native tools and commands alongside Windows/Powershell tools.
  • Review the order of protocol mentions (e.g., 'SMB and NFS' vs. 'NFS and SMB') to ensure Linux/NFS is not consistently listed after Windows/SMB.
  • Where features are described as being for 'Windows File Explorer', also mention the equivalent experience for Linux file managers or CLI tools.
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-25 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed, step-by-step instructions for setting SACLs (auditing) on SMB shares using the Windows GUI, while the equivalent Linux/NFS instructions lack step-by-step guidance and instead refer users to a separate document. Windows tools and patterns (such as right-clicking in Windows Explorer) are described explicitly, whereas Linux/UNIX methods are not. Additionally, the Windows method is presented first, reinforcing the bias.
Recommendations
  • Provide step-by-step instructions for setting Audit ACEs on NFSv4.1 exports from a Linux client, including example commands (e.g., using nfs4_setfacl or setfacl).
  • Ensure that Linux/NFS instructions are as detailed and accessible as the Windows/SMB instructions, possibly using side-by-side tabs or sections.
  • Avoid always presenting Windows instructions first; alternate the order or present both equally.
  • Include command-line examples for both Windows (e.g., PowerShell) and Linux (e.g., Bash) where applicable.
  • Reference Linux-native tools and workflows explicitly, not just by linking to other documentation.
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-25 00:01
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 in its command-line examples and tooling. All registration and feature management examples use Azure PowerShell cmdlets, with Azure CLI (cross-platform) only mentioned in passing and without explicit command examples. There are no Linux- or macOS-specific instructions or screenshots, and the workflow assumes familiarity with Windows-centric patterns (e.g., right-click context menus in the Azure Portal).
Recommendations
  • Provide explicit Azure CLI command examples (e.g., 'az feature register', 'az feature show') alongside PowerShell for all registration steps, with full syntax and example output.
  • Include notes or sections clarifying that all Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific prerequisites if needed.
  • Balance the order of presentation: list Azure CLI examples before or alongside PowerShell, not only as an afterthought.
  • Where UI instructions are given (e.g., 'right-click'), clarify that these actions are performed in the Azure Portal web interface, which is OS-agnostic.
  • Add a brief section or note for Linux/macOS users, confirming that all features are accessible via CLI and Portal, and link to relevant cross-platform setup guides.
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-25 00:01
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 'Ways to create snapshots' section, PowerShell is listed as a primary tool alongside Azure Portal, REST API, and Azure CLI, but there is no mention of Linux shell scripting or specific Linux tooling. The order of tools often places PowerShell before or alongside CLI, and there are no explicit Linux/Unix shell examples or references. Additionally, scripting examples reference a Microsoft blog post about SQL Server and T-SQL, which are Windows-centric technologies, without providing Linux/NFS-focused examples. There is no mention of Linux-native management patterns, and the documentation does not provide parity for Linux administrators.
Recommendations
  • Provide explicit Linux shell (bash) examples for snapshot management using Azure CLI, demonstrating commands in a Linux terminal context.
  • Include references to Linux/Unix scripting and automation patterns (e.g., bash scripts, cron jobs) for automating snapshot operations.
  • Ensure that tool lists do not always place PowerShell before CLI or REST API; consider listing CLI and REST API first, as they are cross-platform.
  • Add examples or references for managing NFS volumes and snapshots from Linux clients, including mounting and accessing .snapshot directories.
  • Reference Linux-native backup and restore workflows, especially for NFS volumes, and provide guidance for Linux administrators.
  • Balance scripting examples by including both PowerShell and bash script samples where scripting is discussed.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md ...-netapp-files/azure-netapp-files-create-volumes-smb.md
High Priority View Details →
Scanned: 2025-08-24 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: it provides only Windows-based instructions and screenshots for managing SMB permissions (using Windows MMC and the Security tab in Windows SMB clients), does not mention or provide Linux client examples for accessing or managing SMB shares, and references Windows-specific tools and workflows without Linux equivalents. Linux SMB clients and tools (such as smbclient, mount.cifs, or setfacl) are not discussed, and the documentation assumes a Windows administrative environment.
Recommendations
  • Add instructions and examples for accessing and managing SMB shares from Linux clients, including mounting SMB volumes using mount.cifs and managing permissions with setfacl or similar tools.
  • Include Linux command-line examples (e.g., using smbclient or mount.cifs) alongside or after Windows examples to ensure parity.
  • Mention Linux tools and workflows for SMB management where Windows tools (like MMC) are referenced.
  • Provide screenshots or terminal output from Linux environments where relevant.
  • Clarify in the 'Control access to an SMB volume' section how permissions can be managed from non-Windows clients, and note any limitations or differences.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md ...etapp-files-mount-unmount-volumes-for-virtual-machines.md
High Priority View Details →
Scanned: 2025-08-24 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows instructions for mounting NFS volumes, but there are subtle biases. The Windows section is presented after Linux, but the Windows instructions require first mounting on Linux and running chmod, which may not be intuitive for Windows-only administrators. The Windows example uses the Windows 'Mount' command and references Windows documentation, but does not provide a PowerShell example or alternative. The Linux section is more detailed, with explicit mount command examples and fstab configuration, while the Windows section is brief and lacks troubleshooting or advanced options. There is also an implicit assumption that Linux is the primary platform for NFS, with Windows as a secondary, less-supported use case.
Recommendations
  • Provide a more complete Windows example, including PowerShell syntax and troubleshooting tips for common issues.
  • Clarify the prerequisite for mounting on Linux (chmod) and explain why this is necessary for Windows users.
  • Offer parity in detail between Linux and Windows sections, such as automounting on Windows (e.g., via persistent mounts or scripts).
  • Include references to Linux and Windows tools equally, and consider presenting both platforms' instructions side by side for each step.
  • Add troubleshooting guidance for both Linux and Windows, not just Linux.
  • Explicitly mention any limitations or differences in NFS support between Linux and Windows early in the document.
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-24 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 feature registration, mentioning PowerShell before Azure CLI, and omitting explicit Linux/CLI/bash examples. The registration steps are shown with PowerShell commands, and while Azure CLI is mentioned, no CLI command-line examples are provided. There are no Linux-specific instructions or screenshots, and the workflow assumes a GUI experience typical of Windows environments.
Recommendations
  • Provide explicit Azure CLI command examples alongside PowerShell for all registration and configuration steps, including full command syntax and expected output.
  • Include bash shell examples for Linux users where appropriate, especially for scripting or automation tasks.
  • Ensure that any GUI instructions clarify that the Azure Portal is cross-platform, and avoid language that assumes a Windows-only environment (e.g., 'right-click' could be replaced with 'select the context menu').
  • Add a section or callout for Linux/macOS users, highlighting any differences or confirming parity.
  • Where screenshots are used, ensure they do not display Windows-specific UI elements or clarify that the experience is the same across platforms.
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-24 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by providing detailed, step-by-step instructions for setting SACLs (auditing) on SMB shares using the Windows GUI, while the equivalent Linux/NFSv4.1 instructions are minimal and refer users to another page. The registration example (in the commented-out section) uses Azure PowerShell first, with Azure CLI only mentioned as an alternative. There are no Linux command-line examples for setting Audit ACEs, and Windows tools and workflows are described in more detail and appear first.
Recommendations
  • Provide step-by-step Linux command-line examples for setting Audit ACEs on NFSv4.1 shares, similar to the detailed Windows instructions for SMB.
  • When describing feature registration, present both Azure PowerShell and Azure CLI examples side by side, or lead with the CLI, which is cross-platform.
  • Avoid referring to Windows administration hosts and tools as the default; instead, clarify that equivalent operations can be performed from Linux systems and provide those instructions.
  • Ensure parity in detail and clarity between Windows and Linux/NFS sections, including screenshots or command examples where appropriate.
  • Explicitly mention and link to Linux tools (such as setfacl or nfs4_setfacl) for managing ACLs on NFS shares.
GitHub Create Pull Request
← Previous Page 14 of 36 Next →