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 476-500 of 896 flagged pages
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-network-features.md ...icles/azure-netapp-files/configure-network-features.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias primarily through exclusive use of Azure PowerShell commands (e.g., Get-AzProviderFeature) for feature registration checks, with no CLI (az) or Bash/Linux alternatives provided. There are no Linux shell or cross-platform command examples, and the only command-line tooling referenced is PowerShell, which is more familiar to Windows users. This may disadvantage Linux administrators or those who prefer cross-platform tools.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for feature registration checks (e.g., az feature list --namespace Microsoft.NetApp --query ...).
  • Explicitly note that PowerShell commands can be run on any OS with PowerShell Core, but also offer Bash or shell script alternatives where possible.
  • Where screenshots or UI steps are shown, clarify that the Azure portal is cross-platform, and consider mentioning any OS-specific considerations if relevant.
  • In sections discussing Terraform, mention that Terraform is cross-platform and can be used from Linux, macOS, or Windows.
  • Review all command snippets and ensure that for every PowerShell example, a CLI or Bash equivalent is provided to ensure Linux parity.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-smb-share-access-control-lists.md ...-netapp-files/manage-smb-share-access-control-lists.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively presents Windows-based tools and workflows (Windows Explorer, Microsoft Management Console) for managing SMB share ACLs in Azure NetApp Files. There are no Linux or cross-platform alternatives mentioned, and all instructions and screenshots are Windows-specific. This creates a strong Windows bias and leaves out users who may be administering from Linux or other non-Windows environments.
Recommendations
  • Include equivalent instructions for viewing and managing SMB share ACLs from Linux systems, such as using smbclient, smbcacls, or other Samba tools.
  • Explicitly state if certain operations (such as modifying share-level ACLs) are only possible from Windows, and provide any available workarounds or alternatives for non-Windows users.
  • Add a section or note addressing cross-platform management, clarifying limitations and suggesting best practices for Linux/macOS administrators.
  • Where possible, provide command-line examples (e.g., PowerShell and Bash/smbcacls) side by side to improve parity.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/create-volumes-dual-protocol.md ...les/azure-netapp-files/create-volumes-dual-protocol.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias primarily in the management and configuration of LDAP POSIX attributes, where only Windows tools (Active Directory Users and Computers MMC snap-in) are described and illustrated. There are no equivalent instructions or examples for managing POSIX attributes using Linux tools or command-line utilities. Additionally, the step-by-step instructions for accessing the Attribute Editor are exclusively for Windows systems, and Windows terminology and tools are mentioned first or exclusively in several places. There are no PowerShell command examples, but the overall guidance assumes a Windows-centric administrative environment.
Recommendations
  • Add equivalent instructions and examples for managing LDAP POSIX attributes using Linux tools (e.g., ldapmodify, ldapadd, or graphical LDAP editors like Apache Directory Studio).
  • Provide Linux-based workflows for common administrative tasks, such as editing user and group attributes, alongside the Windows MMC snap-in instructions.
  • When referencing tools or workflows, mention both Windows and Linux options, or present them in a neutral order (e.g., 'On Windows, use X; on Linux, use Y').
  • Include screenshots or command-line examples for Linux-based LDAP management where possible.
  • Clarify that administrative tasks can be performed from both Windows and Linux environments, and link to relevant Linux documentation or external resources.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/lightweight-directory-access-protocol-name-mapping.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/lightweight-directory-access-protocol-name-mapping.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by exclusively describing the asymmetric name mapping process using Windows tools (Active Directory Users and Computers MMC) and workflows. There are no equivalent instructions or references for performing similar LDAP attribute modifications using Linux-native tools or command-line utilities, despite the hybrid environment context.
Recommendations
  • Add parallel instructions for modifying LDAP attributes using Linux tools such as ldapmodify, ldapvi, or Apache Directory Studio.
  • Include examples of how to update the UID field for a user in LDAP from a Linux system, possibly with command-line snippets.
  • Present both Windows and Linux methods side-by-side or in separate sections to ensure parity and inclusivity for administrators on either platform.
  • Reference cross-platform LDAP management tools where appropriate, and clarify that the process is not limited to Windows environments.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-attached-file-permissions.md ...zure-netapp-files/network-attached-file-permissions.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by describing Windows SMB inheritance controls first and in more detail, including a screenshot of the Windows interface, while Linux/NFS methods are only briefly mentioned without visual aids or command-line examples. Windows terminology and tools are foregrounded, and there are no Linux/NFS command examples or screenshots.
Recommendations
  • Provide equivalent Linux/NFS examples, such as showing how to set inheritance with setfacl or chmod on NFSv4.1.
  • Include screenshots or command-line snippets for Linux/NFS permission management, not just Windows GUI.
  • Present Windows and Linux/NFS instructions in parallel, rather than describing Windows first and in more detail.
  • Expand on Linux/NFS permission inheritance, including practical steps and best practices.
  • Balance the use of terminology and visuals between Windows and Linux/NFS environments.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azacsnap-release-notes.md .../articles/azure-netapp-files/azacsnap-release-notes.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Linux and Windows binaries for AzAcSnap, but there is a noticeable emphasis on Windows-specific features (e.g., Microsoft SQL Server on Windows) and terminology. Some features are described as available only for Windows (e.g., SQL Server 2022 on Windows), and there are no explicit Linux-specific examples or parity notes for features. Windows is often mentioned first or exclusively in feature announcements, and there is a lack of Linux-focused troubleshooting or configuration examples.
Recommendations
  • Ensure that for every Windows-specific feature or example, a Linux equivalent is provided or the lack thereof is explicitly documented.
  • When listing supported platforms or features, alternate the order (e.g., Linux first in some sections) or use neutral phrasing.
  • Add Linux-specific configuration, troubleshooting, and usage examples where appropriate.
  • Clearly indicate feature parity or gaps between Windows and Linux, and provide timelines or workarounds for missing Linux features.
  • Include Linux tools, logs, and environment variable usage in examples and troubleshooting guidance.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-sdk-cli.md ...icles/azure-netapp-files/azure-netapp-files-sdk-cli.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation lists both Azure CLI and PowerShell as supported CLI tools, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, with no mention of Bash, Linux shell, or cross-platform scripting examples. There are no explicit Linux examples or references to Linux-native tools, and the documentation does not clarify that Azure CLI is cross-platform or provide Linux-specific guidance.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Provide example commands for both Azure CLI (in Bash/shell) and PowerShell, making it clear which is suitable for Linux users.
  • Add a section or note for Linux users, including installation instructions or links for Azure CLI on Linux.
  • If possible, include references to automation or scripting approaches common on Linux (e.g., Bash scripts, cron jobs) alongside PowerShell.
  • Reorder the CLI tools table to list Azure CLI first, emphasizing its cross-platform nature.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/mount-volumes-vms-smb.md ...n/articles/azure-netapp-files/mount-volumes-vms-smb.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is exclusively focused on mounting SMB volumes for Windows VMs, providing only Windows client instructions and screenshots. There are no Linux examples or references to Linux tools for mounting SMB volumes, and the title and content are Windows-centric.
Recommendations
  • Add a section on mounting SMB volumes from Linux clients, including example commands (e.g., using mount.cifs or smbclient).
  • Include Linux-specific screenshots or terminal output where appropriate.
  • Update the title and description to clarify if the guide is Windows-only, or broaden the scope to include Linux.
  • Ensure parity in detail and clarity between Windows and Linux instructions.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-nfs.md ...-docs/blob/main/articles/azure-netapp-files/faq-nfs.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a detailed PowerShell command and mount example for Windows clients accessing NFS volumes, but does not provide equivalent Linux command-line examples for mounting NFS volumes or configuring client settings. This creates a bias toward Windows users and leaves Linux administrators without direct guidance for common NFS tasks.
Recommendations
  • Add explicit Linux command-line examples (e.g., using 'mount' command) for mounting NFS volumes, including recommended mount options.
  • Provide Linux-specific guidance for optimizing NFS client performance (e.g., sysctl settings, mount options for performance, troubleshooting tips).
  • When discussing client configuration (such as case sensitivity or performance tuning), include both Windows and Linux procedures side by side.
  • Ensure that any PowerShell or Windows-specific instructions are matched with equivalent Linux shell commands where applicable.
  • Review the documentation for other places where only Windows tools or patterns are mentioned, and add Linux equivalents to ensure parity.
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-07-13 21:37
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, with Azure CLI (which is cross-platform and more common on Linux) only mentioned in passing and without explicit command examples. There are no Linux-specific or CLI-first instructions, and the only code blocks are PowerShell. This may disadvantage Linux users or those who prefer CLI tools.
Recommendations
  • Provide explicit Azure CLI command examples (e.g., 'az feature register', 'az feature show') alongside or before PowerShell examples, in code blocks.
  • When referencing command-line operations, avoid assuming PowerShell as the default; present CLI and PowerShell options equally.
  • Include notes or sections for Linux/macOS users, clarifying that all operations can be performed via Azure CLI on any platform.
  • Consider alternating the order of examples (CLI first in some sections, PowerShell in others) to avoid 'Windows first' bias.
  • Where screenshots or UI steps are shown, clarify that the Azure Portal is platform-agnostic.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/kerberos.md ...docs/blob/main/articles/azure-netapp-files/kerberos.md
High Priority View Details →
Scanned: 2025-07-13 21:37
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 Active Directory as the only supported KDC, referencing Windows tools (such as Event Viewer, MMC, and setspn) for management and troubleshooting, and providing detailed workflows and terminology rooted in Windows environments. Powershell and Windows-specific management consoles are mentioned for SPN management, while Linux/UNIX equivalents are not. There are no Linux command-line examples for managing Kerberos or SPNs, and Linux-specific workflows are only briefly mentioned, often as exceptions or notes, rather than as first-class guidance.
Recommendations
  • Explicitly mention and, where possible, provide parity for Linux/UNIX tools and workflows (e.g., kadmin, ktutil, klist, and relevant Linux commands for SPN/keytab management).
  • Include Linux/UNIX command-line examples for common Kerberos tasks, such as creating and managing keytabs, configuring krb5.conf, and troubleshooting Kerberos authentication.
  • Where Windows tools (e.g., setspn, MMC, Event Viewer) are referenced, also reference Linux/UNIX equivalents or alternatives.
  • Clarify any Azure NetApp Files limitations regarding non-Windows KDCs, and if only Windows AD is supported, explain the rationale and potential roadmap for broader KDC support.
  • Balance the order of presentation so that Linux/NFS and Windows/SMB are treated with equal depth and priority, rather than consistently leading with Windows.
  • Add troubleshooting sections and best practices relevant to Linux environments, including log file locations, common error messages, and diagnostic commands.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/includes/smb-continuous-availability.md ...e-netapp-files/includes/smb-continuous-availability.md
High Priority View Details →
Scanned: 2025-07-13 21:37
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 focusing exclusively on Windows-based workloads and tools (e.g., Citrix, FSLogix, MSIX app attach, SQL Server on Windows), explicitly stating that Linux SQL Server is not supported, and omitting any Linux-specific examples or guidance. Additionally, it references Windows/Active Directory security privileges without mentioning Linux equivalents.
Recommendations
  • Clearly state the lack of Linux support up front and provide a roadmap or estimated timeline for Linux parity, if available.
  • Include examples or guidance for Linux workloads if/when support becomes available.
  • Where Windows-specific tools or privileges (e.g., SeSecurityPrivilege, Active Directory) are mentioned, provide Linux equivalents or clarify that these steps are not applicable to Linux environments.
  • Add a section addressing common Linux use cases and their current support status, to inform Linux administrators.
  • If Linux support is planned, invite feedback or provide a link for users to request Linux support.
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-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All examples and instructions for managing SMB volume permissions and share properties are provided exclusively for Windows environments, specifically referencing Windows SMB clients, Microsoft Management Console (MMC), and Windows File Explorer. There are no examples or guidance for Linux clients, even though SMB is cross-platform and Linux clients (e.g., using smbclient, mount.cifs, or Nautilus) are common in enterprise environments. The documentation assumes Windows as the default or only client, omitting Linux tools and workflows.
Recommendations
  • Add parallel instructions and screenshots for managing SMB share and NTFS permissions from Linux clients, using tools such as smbclient, mount.cifs, or GUI file managers (e.g., Nautilus, Dolphin).
  • Include examples of mounting the SMB volume from Linux, with sample mount commands and troubleshooting tips.
  • Mention Linux equivalents for tasks like viewing shares (e.g., smbclient -L), modifying permissions (e.g., setfacl, or using smbclient's 'chmod' and 'chown' commands where supported).
  • Clarify that SMB volumes can be accessed and managed from both Windows and Linux clients, and provide links to relevant Linux documentation.
  • Avoid assuming Windows as the only or primary environment by rephrasing sections to be platform-neutral where possible.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/enable-continuous-availability-existing-SMB.md ...p-files/enable-continuous-availability-existing-SMB.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All operational steps and verification commands are presented exclusively for Windows environments, specifically referencing Windows systems and PowerShell commands. There are no examples or guidance for Linux or macOS clients, nor is there mention of how to verify or interact with SMB CA from non-Windows platforms.
Recommendations
  • Add equivalent instructions for Linux clients, including how to remount SMB shares after enabling CA and how to verify CA status using Linux tools (e.g., 'smbstatus', 'mount', or 'smbclient').
  • Mention that SMB CA is a Windows-centric feature but clarify any relevant behaviors or limitations for Linux/macOS clients.
  • Provide command-line examples for Linux (and optionally macOS) environments, or explicitly state if verification is not possible or not supported from those platforms.
  • Avoid assuming all users are on Windows; update language to be inclusive of cross-platform scenarios.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-smb-performance.md ...ure-netapp-files/azure-netapp-files-smb-performance.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias: all command-line examples use Windows PowerShell cmdlets (e.g., Get-SmbClientNetworkInterface, set-SmbClientConfiguration), and only Windows tools (Performance Monitor, Hyper-V adapters) are referenced for monitoring and configuration. There are no Linux or macOS SMB client examples, nor is there any mention of how to achieve similar monitoring or tuning on non-Windows platforms. References and links are exclusively to Windows documentation, and Windows terminology is used throughout.
Recommendations
  • Include equivalent Linux (e.g., smbclient, mount.cifs, smbstatus, /proc/fs/cifs) and macOS (mount_smbfs, system profiler) commands and examples for all configuration and monitoring steps.
  • When referencing tools like Performance Monitor or PowerShell cmdlets, also mention and provide examples for open-source or cross-platform alternatives (e.g., iostat, iftop, netstat, atop, nload, or perf tools on Linux).
  • Add a section or callouts for Linux and macOS SMB client tuning, including sysctl parameters, mount options, and relevant kernel modules.
  • When describing SMB features (Multichannel, Signing, Encryption), clarify support and configuration steps for non-Windows clients, including any limitations or differences.
  • Provide links to official Samba and Linux SMB client documentation alongside Windows references.
  • Avoid assuming the reader is using Windows by default; use neutral language and structure sections to address all major platforms equally.
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-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by mentioning Windows tools (robocopy) alongside Linux tools (rsync), but consistently lists the Windows tool second. There is a slight preference for Windows terminology and tools, and the only SMB example given is robocopy, which is Windows-specific. There are no explicit Linux SMB examples (such as smbclient or Linux mount/cp commands), and no PowerShell or command-line examples are provided, but the tool recommendations lean toward Windows environments for SMB.
Recommendations
  • Provide explicit Linux-based SMB migration examples (e.g., using smbclient, mount.cifs with cp/rsync, or other Linux-native tools).
  • When listing tools, alternate the order or group by protocol rather than platform, or explicitly state parity (e.g., 'For NFS, use rsync (Linux/macOS) or robocopy (Windows); for SMB, use robocopy (Windows) or smbclient (Linux)').
  • Include example commands for both Windows and Linux environments for each protocol (NFS and SMB).
  • Mention cross-platform tools (e.g., rclone, or third-party migration tools that run on both OSes) where appropriate.
  • Clarify that migration can be performed from both Windows and Linux clients, and provide links to relevant documentation for both.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-kerberos-encryption.md ...es/azure-netapp-files/configure-kerberos-encryption.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a Windows bias by requiring the use of PowerShell commands (Set-ADComputer) and referencing Windows-specific tools (RSAT) for critical configuration steps, such as setting Kerberos encryption types on Active Directory computer accounts. These steps are presented without Linux or cross-platform alternatives, and the Windows/PowerShell approach is described first and exclusively, even though the NFS client is Linux-based.
Recommendations
  • Provide equivalent instructions for setting Kerberos encryption types using Linux-based tools such as 'ldapmodify', 'adcli', or 'samba-tool', for environments where administrators do not have access to Windows or PowerShell.
  • Include examples of how to perform Active Directory-related tasks from a Linux host, especially since the NFS client is Linux.
  • Clearly indicate whether the PowerShell/RSAT steps are mandatory or if there are alternative approaches for non-Windows environments.
  • Consider restructuring the documentation to present both Windows and Linux methods side by side, or at least mention Linux alternatives where only Windows tools are referenced.
  • Add a note or section addressing cross-platform administration scenarios, acknowledging that not all environments will have Windows domain controllers or administrators with Windows access.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-attached-file-permissions-smb.md ...-netapp-files/network-attached-file-permissions-smb.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively discusses SMB file permissions in the context of NTFS ACLs, referencing only Microsoft/Windows concepts and documentation. There are no examples or mentions of Linux tools, commands, or perspectives for managing SMB permissions, nor is there guidance for Linux administrators.
Recommendations
  • Include examples of managing SMB/NTFS permissions from Linux clients, such as using the 'smbcacls' or 'setfacl' tools where applicable.
  • Reference Linux documentation or community resources for interacting with SMB shares and NTFS ACLs.
  • Clarify whether and how Linux clients can view or modify SMB permissions on Azure NetApp Files, and provide guidance if there are limitations.
  • Present both Windows and Linux approaches in parallel, or at least acknowledge Linux scenarios and provide links to further information.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/data-plane-security.md ...ain/articles/azure-netapp-files/data-plane-security.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by consistently mentioning SMB (a Windows protocol) before NFS (a Linux/UNIX protocol) in several sections, and by providing more detailed explanations for Windows/SMB features such as ACLs and permission inheritance. Integration with Active Directory (a Windows-centric directory service) is highlighted as the only supported LDAP service, with no mention of alternatives or Linux-based directory services. There are no command-line examples or configuration snippets for either platform, but the text assumes familiarity with Windows tools and patterns, while Linux/UNIX equivalents are less emphasized or described in less detail.
Recommendations
  • Alternate the order of SMB and NFS discussions to avoid always placing Windows protocols first.
  • Provide equal depth and detail for NFS (Linux/UNIX) features, including advanced NFSv4.x ACLs and Linux-based permission management.
  • Include practical configuration examples for both Windows (PowerShell, GUI) and Linux (command-line, shell scripts) environments.
  • Mention or acknowledge Linux-based directory services (such as OpenLDAP) even if not currently supported, and clarify roadmap or alternatives.
  • Ensure that terminology and explanations are balanced, avoiding the assumption that Active Directory or Windows ACLs are the default or only approach.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md ...etapp-files/azure-netapp-files-set-up-capacity-pool.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell commands and update instructions before or instead of equivalent Linux/Azure CLI examples. PowerShell (a Windows-centric tool) is mentioned and exemplified in detail, while Azure CLI (cross-platform) is referenced but not exemplified. There are no explicit Linux shell or Bash examples, and the PowerShell module update process is described in more detail than the Azure CLI update process.
Recommendations
  • Provide explicit Azure CLI command examples alongside PowerShell examples for all operations, especially for feature registration and status checking.
  • Include Linux/Bash-specific instructions for updating Azure CLI and using CLI commands.
  • When listing prerequisites or steps, present Azure CLI (cross-platform) instructions before or alongside PowerShell (Windows-centric) instructions to avoid a 'Windows-first' impression.
  • Ensure that all command-line examples are provided in both PowerShell and Bash/Azure CLI syntax, with clear labels for each.
  • Consider adding a table or section comparing PowerShell and Azure CLI commands for common tasks.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/dual-protocol-permission-behaviors.md ...ure-netapp-files/dual-protocol-permission-behaviors.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a subtle Windows bias by frequently referencing Windows tools and concepts (such as NTFS, Windows RPC, and Active Directory) before or more prominently than their Linux/NFS equivalents. There are no practical Linux/NFS command examples (e.g., no explicit 'chmod' or 'chown' usage shown), and management tools for NFS/UNIX permissions are only briefly mentioned (e.g., nfs4_getfacl/nfs4_setfacl) without examples. The documentation assumes familiarity with Windows-centric identity and permission management, and Linux/NFS scenarios are less detailed.
Recommendations
  • Provide practical Linux/NFS examples (e.g., show how to use chmod, chown, nfs4_getfacl, nfs4_setfacl for managing permissions).
  • Balance the order of presentation so that Linux/NFS tools and workflows are described alongside or before Windows/SMB equivalents where appropriate.
  • Include explicit Linux/NFS troubleshooting scenarios and command-line outputs, similar to the detail given for Windows/SMB/NTFS.
  • Expand on NFS/UNIX identity management, including example LDAP configurations and group mapping for Linux environments.
  • Add diagrams or workflows that illustrate both Windows and Linux client interactions with Azure NetApp Files.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/lightweight-directory-access-protocol.md ...-netapp-files/lightweight-directory-access-protocol.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing Microsoft Active Directory as the only supported LDAP server, focusing on AD DS and Microsoft Entra Domain Services. It describes LDAP security and schema extensions primarily in the context of Windows tools and features (e.g., Identity Management for UNIX, Service for UNIX, Centrify). The only concrete example for querying LDAP SRV records uses Windows nslookup syntax, with a brief mention of the Linux dig command but no example. There are no Linux/OpenLDAP-specific instructions, examples, or parity in tool usage, and the documentation repeatedly positions Windows/Active Directory as the default or only scenario.
Recommendations
  • Provide equivalent Linux/OpenLDAP examples where possible, such as showing how to query LDAP SRV records using the dig command with a full example.
  • Clarify early in the documentation that only Microsoft Active Directory is supported, but also acknowledge common Linux LDAP servers (e.g., OpenLDAP) and explain any limitations or roadmap for support.
  • When discussing LDAP schema extensions, mention Linux/UNIX approaches (such as using RFC 2307 attributes in OpenLDAP) and how they compare to Windows extensions.
  • Include examples or notes for Linux administrators, such as how to configure LDAP clients on Linux to work with Azure NetApp Files, even if only Active Directory is supported.
  • Balance the discussion of tools and terminology by not assuming a Windows-centric environment; reference both Windows and Linux tools and patterns where applicable.
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-07-13 21:37
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 secondarily in text and not shown as code blocks. There are no explicit Linux/CLI examples or screenshots, and the UI instructions reference right-click actions, which are more typical of Windows environments. No Linux-specific tools or workflows are discussed.
Recommendations
  • Provide Azure CLI command examples in code blocks alongside PowerShell, not just as a mention in text.
  • Include explicit Linux/macOS instructions or notes where workflows may differ (e.g., right-click actions in the Azure Portal).
  • Ensure screenshots and UI instructions are platform-neutral or clarify that the steps apply equally across OSes.
  • Where possible, add Bash shell examples for scripting or automation tasks.
  • Review for any terminology or workflow that assumes a Windows environment and generalize for cross-platform users.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-smb.md ...-docs/blob/main/articles/azure-netapp-files/faq-smb.md
High Priority View Details →
Scanned: 2025-07-13 21:37
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 strong Windows bias. All examples, tools, and troubleshooting steps reference Windows environments, utilities, and protocols (e.g., MMC, Active Directory Users and Computers, Windows Server DFS, Windows clock sync, Windows Update). There are no Linux or cross-platform examples, nor is there mention of how to interact with Azure NetApp Files SMB shares from Linux clients (e.g., using smbclient, mount.cifs, or Samba). The documentation assumes the reader is using Windows or Windows Server, omitting guidance for Linux administrators.
Recommendations
  • Add examples and troubleshooting steps for accessing Azure NetApp Files SMB shares from Linux clients (e.g., using smbclient, mount.cifs, or gvfs).
  • Include Linux equivalents for Windows tools mentioned (e.g., how to view share/session/open files using smbstatus or similar).
  • When discussing Active Directory integration, mention how to join Linux clients to AD domains and access SMB shares securely.
  • Provide parity in configuration and troubleshooting guidance for both Windows and Linux environments.
  • Avoid assuming the administrator is always using Windows; clarify when a step is Windows-specific and offer alternatives for other platforms.
  • Reference relevant Linux documentation or man pages where appropriate.
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-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows bias by presenting Windows/Powershell examples and instructions first, providing detailed step-by-step instructions for setting SACLs via the Windows GUI, and referencing Windows tools (e.g., robocopy) without Linux equivalents. There are no equivalent step-by-step instructions or command-line examples for Linux users, especially for setting Audit ACEs on NFSv4.1 shares. The registration section also prioritizes Azure PowerShell, with only a brief mention of Azure CLI. This may hinder Linux administrators from easily following the documentation.
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 nfs4_setfacl).
  • Include Linux command-line examples for relevant operations, such as registering the feature with Azure CLI, alongside or before PowerShell examples.
  • Mention Linux tools (e.g., rsync) alongside Windows tools like robocopy when discussing migration scenarios.
  • Ensure that instructions and screenshots are balanced between Windows and Linux environments, or provide tabs for each platform where applicable.
  • Clarify in each section which steps are for Windows and which are for Linux, and avoid assuming a Windows administration host as the default.
GitHub Create Pull Request
← Previous Page 20 of 36 Next →