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 526-550 of 896 flagged pages
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-08 04:23
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 examples for feature registration and status checking, with Azure CLI commands only briefly mentioned in text and not shown as code examples. There are no explicit Linux shell or cross-platform CLI examples, and the step-by-step instructions and screenshots are focused on the Azure Portal UI, which is platform-agnostic but the scripting focus is Windows/Powershell-centric.
Recommendations
  • Provide explicit Azure CLI (az) command examples alongside PowerShell for all feature registration and status steps, formatted as code blocks.
  • When referencing command-line operations, present CLI examples first or in parallel with PowerShell to avoid a Windows-first impression.
  • Include notes or sections clarifying that all CLI steps can be performed from Linux, macOS, or Windows, and provide any OS-specific considerations if relevant.
  • Where possible, add bash/zsh shell command snippets for tasks that can be performed outside the Azure Portal, ensuring Linux users have clear guidance.
  • Ensure parity in screenshots or UI walkthroughs by noting that the Azure Portal 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/configure-ldap-over-tls.md ...articles/azure-netapp-files/configure-ldap-over-tls.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively describes root CA certificate generation and export using Windows Server tools (Certification Authority, MMC snap-in), with no mention of Linux-based alternatives or cross-platform methods. All certificate management steps assume a Windows environment, and there are no examples or instructions for performing these tasks on Linux systems.
Recommendations
  • Add instructions for generating and exporting root CA certificates using common Linux tools such as OpenSSL.
  • Include Linux command-line examples for certificate management alongside or before Windows-specific instructions.
  • Mention that both Windows and Linux-based CAs are supported, and provide guidance for both environments.
  • Balance screenshots and tool references by including Linux terminal output or GUI alternatives where applicable.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-network-features.md ...icles/azure-netapp-files/configure-network-features.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell command examples (e.g., Get-AzProviderFeature) for feature registration checks, without offering equivalent Azure CLI (cross-platform) or Bash examples. There are no Linux/Unix command-line instructions or screenshots, and all command-line guidance assumes the use of PowerShell, which is most common on Windows. No mention is made of Linux-native tools or workflows.
Recommendations
  • For every PowerShell command example, provide an equivalent Azure CLI (az) command, which is cross-platform and commonly used on Linux and macOS.
  • Include explicit instructions or code snippets for Bash or shell environments when referencing command-line operations.
  • Clarify that the Azure portal and Terraform steps are platform-agnostic, and avoid implying a Windows-only workflow.
  • Where screenshots show command-line tools, ensure at least some are from a Linux terminal or a cross-platform shell.
  • Add a note at the beginning stating that all operations can be performed from Windows, Linux, or macOS, and link to platform-specific setup guides if needed.
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-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. PowerShell and Windows-centric tools (such as Set-ADUser, Group Policy, and Windows registry keys) are used exclusively for configuration and management tasks, with no equivalent Linux or cross-platform examples. Windows terminology and patterns are presented first or exclusively, and there is a lack of guidance for administrators using Linux-based AD management tools or environments.
Recommendations
  • Provide equivalent Linux/Unix command-line examples (e.g., using 'ldapmodify', 'kinit', or 'adcli') for configuring Kerberos encryption types and managing AD accounts.
  • Include instructions or references for managing Active Directory from Linux systems, such as using Samba tools or openldap utilities.
  • When discussing Group Policy or registry settings, mention if and how similar configurations can be managed from non-Windows environments.
  • Balance the order of presentation so that Linux/NFS and Windows/SMB use cases are given equal prominence, especially in sections relevant to both.
  • Add troubleshooting steps and best practices for Linux clients, particularly for NFS and Kerberos integration.
  • Explicitly state any limitations or requirements for Linux-based AD management, and provide links to relevant Microsoft or community documentation.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/cross-zone-region-replication-configure.md ...etapp-files/cross-zone-region-replication-configure.md
High Priority View Details →
Scanned: 2025-07-08 04:23
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 and status checking, mentioning PowerShell commands first and in detail, and relegating Azure CLI (cross-platform) commands to a brief mention without examples. No Linux-specific or cross-platform shell examples are provided, which may disadvantage users on non-Windows platforms.
Recommendations
  • Provide full Azure CLI command examples (e.g., 'az feature register' and 'az feature show') alongside PowerShell, not just as a mention.
  • Present CLI examples before or alongside PowerShell to avoid the impression of Windows-first bias.
  • Explicitly state that both PowerShell and CLI are supported and clarify which environments are required for each.
  • Consider including Bash shell usage examples for Linux/macOS users where relevant.
  • Review other sections for similar patterns and ensure parity in tooling and instructions for all major platforms.
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-08 04:23
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 by focusing on Windows-based tools and workflows for managing LDAP POSIX attributes (e.g., exclusively referencing the Active Directory Users and Computers MMC snap-in and providing step-by-step instructions for accessing the Attribute Editor on Windows). 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 or NFS client configuration is only referenced via a link, not with inline examples.
Recommendations
  • Provide equivalent instructions for managing LDAP POSIX attributes using Linux tools (e.g., ldapmodify, ldapadd, or Apache Directory Studio) alongside the Windows MMC snap-in example.
  • Include examples or screenshots of editing POSIX attributes from a Linux environment or using cross-platform LDAP management tools.
  • When describing workflows or tools, present both Windows and Linux options in parallel, or alternate which platform is mentioned first to avoid a 'Windows-first' impression.
  • Expand the 'Configure the NFS client' section with at least a basic example of mounting the volume from a Linux client, rather than only linking to another page.
  • Where possible, use neutral terminology (e.g., 'LDAP management tool') and clarify when a step is platform-specific.
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-08 04:23
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 SMB/Windows-specific features (such as ACLs and permission inheritance). There are no explicit Linux command-line or configuration examples, and the integration with Active Directory (a Windows-centric directory service) is highlighted without mention of alternatives. Linux/UNIX tools, commands, or perspectives are underrepresented or missing.
Recommendations
  • Alternate the order of SMB and NFS discussions to avoid always foregrounding Windows technologies.
  • Provide concrete Linux/UNIX command-line examples (e.g., using chmod, setfacl, or mount commands for NFS permissions and inheritance).
  • Include references or examples for integrating with non-Active Directory LDAP servers (such as OpenLDAP) if supported, or clarify if only Windows-based directory services are available.
  • Expand on NFS advanced permissions and inheritance with practical Linux examples, not just theoretical descriptions.
  • Where possible, add parity in detail and depth between SMB (Windows) and NFS (Linux/UNIX) sections, ensuring both audiences are equally served.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/disable-showmount.md .../main/articles/azure-netapp-files/disable-showmount.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page primarily uses Azure PowerShell commands to demonstrate how to disable showmount, with Azure CLI only mentioned secondarily and without examples. There are no Linux shell or cross-platform command examples, and the workflow assumes familiarity with PowerShell and the Azure Portal UI, both of which are more common in Windows environments.
Recommendations
  • Provide explicit Azure CLI command examples (e.g., 'az feature register', 'az feature show', 'az feature unregister') alongside or before PowerShell examples.
  • Include bash/Linux shell command snippets for interacting with Azure CLI, making it clear that the process is cross-platform.
  • Clarify in the introduction that the feature can be managed equally from Windows, Linux, or macOS environments using Azure CLI.
  • Balance the order of examples so that CLI and PowerShell are presented together, or alternate which comes first.
  • Add notes or links for users who may not have PowerShell available, guiding them to install and use Azure CLI on Linux/macOS.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/domain-name-system-concept.md ...icles/azure-netapp-files/domain-name-system-concept.md
High Priority View Details →
Scanned: 2025-07-08 04:23
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 DNS concepts, providing Windows-centric instructions and screenshots, referencing Microsoft best practices and tools first, and offering more detailed Windows (nslookup) examples before Linux (dig). Linux/BIND is mentioned but not explored in depth, and Linux-specific configuration or troubleshooting steps are minimal or missing.
Recommendations
  • Provide Linux/BIND DNS configuration and troubleshooting steps alongside or before Windows/Active Directory instructions.
  • Include Linux/BIND screenshots and examples for DNS management, not just Windows DNS Manager.
  • Expand the 'dig' section to match the detail and troubleshooting depth of the 'nslookup' (Windows) section.
  • Offer parity in packet capture and DNS update examples for Linux environments (e.g., using tcpdump, journalctl, or BIND logs).
  • Reference Linux/BIND best practices and documentation links in parallel to Microsoft/Windows links.
  • Clarify when features (like secure DDNS) are exclusive to Microsoft DNS and suggest alternatives or workarounds for Linux/BIND users.
  • Balance terminology by not assuming Active Directory or Windows DNS as the default; explicitly address both Windows and Linux DNS scenarios throughout.
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-08 04:23
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 frequently referencing Windows/Active Directory tools and concepts first or exclusively, providing more detail on Windows/NTFS behaviors, and omitting concrete Linux/NFS client command examples for permission management. While both UNIX and NTFS security styles are described, practical guidance and examples for Linux/NFS environments are limited, and Windows terminology and tools (such as Windows RPC, SIDs, and NTFS ACLs) are often mentioned before or instead of their Linux equivalents.
Recommendations
  • Include explicit Linux/NFS client command examples for managing permissions (e.g., show usage of nfs4_setfacl, chown, chmod) alongside or before Windows/NTFS examples.
  • Balance the order of presentation so that Linux/NFS concepts and tools are described with equal prominence as Windows/NTFS ones.
  • Provide practical Linux/NFS troubleshooting scenarios and solutions, similar to the detailed Windows/Active Directory authentication flows.
  • Reference Linux identity management solutions (such as sssd, nsswitch, or local passwd/group files) where relevant, not just Active Directory/LDAP.
  • Clarify limitations and best practices for Linux/NFS environments (e.g., how to manage NFSv4.x ACLs, what to expect with POSIX permissions) with concrete examples.
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-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively references Windows systems and PowerShell commands for verifying SMB Continuous Availability. There are no examples or instructions for Linux clients, nor are Linux tools or workflows mentioned. The reboot step explicitly refers to 'Windows systems', and the verification step uses a Windows-only PowerShell cmdlet.
Recommendations
  • Add equivalent instructions for Linux clients, such as how to remount SMB shares or restart relevant services after enabling CA.
  • Provide Linux command-line examples (e.g., using smbstatus, smbclient, or mount options) to verify CA status from a Linux system.
  • Clarify whether CA is relevant or supported for non-Windows SMB clients, and if not, state this explicitly.
  • Avoid assuming all users are on Windows by using more neutral language (e.g., 'client systems' instead of 'Windows systems') where appropriate.
  • If certain features or verification steps are only available on Windows, note this clearly and provide any possible alternatives for Linux users.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-application-resilience.md ...icles/azure-netapp-files/faq-application-resilience.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits some Windows bias, particularly in the SMB-focused sections. Windows workloads and tools are mentioned first or exclusively in several places, especially regarding SMB Transparent Failover and supported workloads. Linux equivalents for SMB-based scenarios are either omitted or explicitly marked as unsupported. In the Boomi section, Windows is prioritized for SMB, while Linux is mentioned for NFS, but there are no detailed Linux/SMB examples. The 'Next steps' section provides a link for mounting SMB volumes only for Windows VMs, with no equivalent for Linux, and the SMB application support list excludes Linux SQL Server.
Recommendations
  • Provide explicit Linux examples or guidance for SMB-based scenarios, or clarify if/why they are unsupported.
  • When listing supported workloads or tools, avoid listing Windows-only options first; instead, present both Linux and Windows options together or clarify parity.
  • Add a 'Mount SMB volumes for Linux VMs' link or section in the 'Next steps' area, or state if this is unsupported and why.
  • For each application scenario (e.g., SQL Server, Boomi), include Linux guidance where possible, or clearly state support limitations.
  • Review and balance the order of protocol/tool mentions (e.g., NFS and SMB) to avoid implicit prioritization of Windows/SMB.
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-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux (rsync) and Windows (robocopy) tool examples for file-based data migration, but consistently lists the Windows tool (robocopy) after the Linux tool (rsync). However, there is a subtle bias in the detailed linking and explanation for robocopy (linking to Windows Server docs), and the overall documentation structure and language is more familiar to Windows administrators (e.g., references to SMB, robocopy, and Azure-specific tools). There are no explicit Linux command examples or step-by-step instructions, and PowerShell/Windows terminology is more prevalent. There is also a lack of parity in providing detailed Linux/NFS migration examples or links to Linux documentation.
Recommendations
  • Provide explicit Linux/NFS migration examples, including sample rsync commands and links to official rsync documentation or Linux man pages.
  • Balance the documentation by including both Windows (robocopy) and Linux (rsync) examples side by side, with equal detail and prominence.
  • Include references to Linux-native tools (such as scp, cp, or tar) where appropriate, and provide links to their documentation.
  • Avoid assuming Windows/PowerShell familiarity by explaining SMB and NFS concepts equally, and by not prioritizing Windows terminology.
  • Add a section or table comparing migration tools for both Linux and Windows environments, with pros, cons, and usage scenarios.
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-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias primarily in the section addressing NFS access from Windows clients. Only Windows-specific tools (PowerShell, Windows mount command) and examples are provided for troubleshooting performance issues, with no equivalent Linux guidance. Additionally, the Windows example appears before or instead of any Linux example, and there is an absence of Linux troubleshooting steps for similar scenarios.
Recommendations
  • For each Windows-specific example (such as enabling CaseSensitiveLookup or mounting NFS volumes), provide equivalent Linux commands and troubleshooting steps (e.g., using mount options or sysctl settings on Linux).
  • When discussing client-side configuration or troubleshooting, present both Windows and Linux examples side by side, or alternate which platform is presented first to avoid implicit prioritization.
  • Include Linux-specific tools or commands (such as mount, nfs-utils, or relevant sysctl parameters) wherever Windows tools are mentioned.
  • Review the documentation for other sections where only Windows client behavior is discussed and add Linux client guidance where applicable.
  • Explicitly state when an issue or solution is platform-specific, and clarify if the guidance applies to both Windows and Linux clients.
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-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All examples, terminology, and troubleshooting steps are centered on Windows environments, tools, and protocols (e.g., MMC, Active Directory, Windows Server, UNC paths). There are no Linux or non-Windows client examples, nor is there mention of Linux tools or workflows for accessing or managing SMB shares. The documentation assumes the reader is operating in a Windows-centric environment.
Recommendations
  • Add examples and guidance for accessing Azure NetApp Files SMB shares from Linux clients (e.g., using smbclient, mount.cifs, or gvfs).
  • Include troubleshooting steps and best practices for Linux SMB clients, such as handling authentication, mounting shares, and dealing with file locking or permissions.
  • Mention Linux-compatible tools (e.g., Samba utilities) alongside Windows tools like MMC.
  • Clarify any differences or limitations when using SMB with Linux clients, such as supported SMB versions, authentication methods, or feature parity.
  • Provide sample configuration snippets for Linux (e.g., /etc/fstab entries, smb.conf settings) where appropriate.
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-08 04:23
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 and workflows (such as Event Viewer, MMC, and PowerShell) for administration and troubleshooting, and providing detailed steps and examples for Windows environments before (or instead of) Linux equivalents. There is a lack of Linux-specific administrative guidance, troubleshooting steps, and examples, especially for common Kerberos and LDAP operations from Linux clients.
Recommendations
  • Explicitly acknowledge the lack of support for non-Windows KDCs and provide guidance for integrating Linux clients with Windows AD in Kerberos scenarios.
  • Add Linux-focused administrative examples, such as using kinit, klist, ktutil, and editing krb5.conf, for Kerberos troubleshooting and configuration.
  • Include Linux command-line examples for viewing and managing SPNs (e.g., using ldapsearch, msktutil, or adcli), and for mounting NFS shares with Kerberos.
  • Provide troubleshooting steps and log file locations for Kerberos issues on Linux clients (e.g., /var/log/secure, journalctl, etc.), not just references to Windows Event Viewer.
  • When describing workflows or tools (e.g., managing SPNs, viewing tickets), present both Windows and Linux methods side by side, or at least mention Linux alternatives.
  • Clarify that while only Windows AD is supported as a KDC, Linux clients are fully supported for NFS Kerberos, and provide best practices for their configuration.
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-08 04:23
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 exclusively describing the process of configuring asymmetric name mapping using the Windows-only 'Active Directory Users and Computers MMC' tool, with no equivalent instructions for modifying LDAP attributes on Linux or non-Windows platforms. The workflow and screenshots are Windows-centric, and Linux is only shown as a consumer (verifying the mapping), not as an administrative platform.
Recommendations
  • Provide equivalent instructions for modifying LDAP user attributes using common Linux tools (e.g., ldapmodify, Apache Directory Studio, or command-line LDAP utilities).
  • Include Linux-based examples and screenshots for updating the UID attribute in LDAP.
  • Present both Windows and Linux workflows in parallel, or at least mention Linux alternatives before or alongside Windows tools.
  • Clarify that the process can be performed from non-Windows environments and link to relevant Linux LDAP administration documentation.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/lightweight-directory-access-protocol-schemas.md ...files/lightweight-directory-access-protocol-schemas.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a strong Windows/Active Directory bias. All configuration and indexing examples are presented exclusively in the context of Microsoft Active Directory, using Windows-specific tools such as ADSI Edit. There are no examples or guidance for equivalent operations in common Linux LDAP servers (e.g., OpenLDAP), nor is there mention of Linux-native tools or configuration patterns. The attribute mapping table and performance discussion are also framed around Windows defaults and behaviors, with no Linux parity.
Recommendations
  • Add equivalent examples and instructions for configuring LDAP schema attributes and indexing in popular Linux LDAP servers such as OpenLDAP.
  • Include Linux command-line examples (e.g., using ldapmodify, slapd.conf, or olcAttributeTypes) for schema and index management.
  • Present attribute mapping and schema explanations in a platform-neutral way, or provide parallel sections for both Windows/Active Directory and Linux/OpenLDAP environments.
  • Mention Linux tools (such as ldapsearch, ldapmodify, or phpldapadmin) alongside Windows tools like ADSI Edit.
  • Clarify any differences in default attribute indexing and schema handling between Active Directory and Linux LDAP servers.
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-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias by exclusively referencing Microsoft Active Directory as the supported LDAP server, focusing on Windows-centric LDAP schema extensions, and providing command-line examples (e.g., nslookup) in Windows syntax before mentioning Linux alternatives. There is a lack of Linux-specific configuration guidance or parity in examples, and Linux/UNIX LDAP servers (such as OpenLDAP) are not discussed as supported or referenced for integration.
Recommendations
  • Explicitly mention the lack of support for non-Active Directory LDAP servers (e.g., OpenLDAP) and, if possible, provide a roadmap or alternatives for Linux environments.
  • Provide Linux/UNIX command-line examples (e.g., using dig, ldapsearch) alongside or before Windows examples when demonstrating LDAP/DNS queries.
  • Include guidance or references for managing UNIX attributes in Active Directory from Linux clients or tools, not just Windows-based schema extensions.
  • Clarify any limitations or workarounds for Linux/UNIX administrators who may need to integrate with Azure NetApp Files in mixed environments.
  • Where possible, use neutral language and ordering (e.g., 'nslookup (Windows) or dig (Linux)') to avoid Windows-first presentation.
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-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing Azure PowerShell commands as the primary example for feature registration, mentioning Azure CLI as an alternative only after the PowerShell examples. There are no explicit Linux or cross-platform shell examples, and the UI instructions reference right-click actions, which are more common in Windows interfaces. No Linux-specific tools or command-line workflows are highlighted.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples, especially for registration steps, to ensure parity for Linux and macOS users.
  • Include explicit Linux/macOS shell command examples (e.g., bash) where applicable.
  • Clarify that Azure CLI commands work cross-platform and are often preferred for automation on Linux/macOS.
  • When describing UI actions, avoid Windows-centric terminology like 'right-click' or provide alternative instructions for users on different platforms or with accessibility needs.
  • Add a section or note highlighting cross-platform management options, including links to relevant CLI documentation for Linux users.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-default-individual-user-group-quotas.md ...p-files/manage-default-individual-user-group-quotas.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing SMB (a Windows protocol) and its SID format before or more prominently than NFS (a Linux/UNIX protocol) in quota target instructions. There are detailed instructions and examples for SMB (Windows) SID formats, but no equivalent command-line or practical examples for Linux/NFS environments. The documentation also lacks any CLI or shell-based examples for Linux users, focusing exclusively on the Azure Portal UI, which may be more familiar to Windows administrators.
Recommendations
  • Provide equivalent command-line examples for managing quotas using Linux/NFS tools (e.g., show how to retrieve user/group IDs on Linux).
  • When mentioning SMB SID formats, also provide explicit examples for NFS (UID/GID) and clarify the mapping between Windows and Linux identities.
  • Include screenshots or walkthroughs for Linux/NFS environments, not just the Azure Portal UI.
  • Ensure that Linux/NFS terminology and workflows are given equal prominence and are not always listed after Windows/SMB examples.
  • Consider adding a section or appendix specifically for Linux/NFS administrators, outlining best practices and common tasks.
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-08 04:23
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. PowerShell commands are given as the primary example for feature registration, and the detailed steps for setting SACLs are exclusively for Windows administration hosts using GUI tools. In contrast, Linux/NFSv4.1 instructions are minimal and redirect to another page, with no direct command-line or workflow examples provided in this document. There are no Linux shell or CLI-based examples for managing file access logs or ACLs directly.
Recommendations
  • Provide Linux shell (bash) and Azure CLI examples alongside PowerShell for feature registration and status checking.
  • Include step-by-step instructions for setting Audit ACEs on NFSv4.1 exports directly in this document, using common Linux tools (e.g., nfs4_setfacl).
  • Ensure that Linux/NFS workflows are described with equal detail as Windows/SMB workflows, including both GUI and command-line options where applicable.
  • When listing protocols or tools, avoid always mentioning Windows/SMB first; alternate or present both equally.
  • Add screenshots or terminal output examples for Linux-based operations, similar to those provided for Windows.
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-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively describes Windows-based tools and workflows (Windows Explorer, Microsoft Management Console) for managing SMB share ACLs in Azure NetApp Files. There are no examples or instructions for performing these tasks from Linux or cross-platform tools, and Windows tools are mentioned first and exclusively throughout.
Recommendations
  • Add equivalent instructions for viewing and managing SMB share ACLs from Linux systems, using tools such as smbclient, smbcacls, or other Samba utilities.
  • If certain operations are only possible from Windows, clearly state this limitation at the beginning of the documentation.
  • Consider including PowerShell and command-line examples for Windows, as well as CLI-based alternatives for Linux where possible.
  • Provide a summary table comparing available management options for both Windows and Linux clients.
  • Reference or link to any relevant cross-platform or REST API methods (if available) for managing SMB share ACLs.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/modify-active-directory-connections.md ...re-netapp-files/modify-active-directory-connections.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Active Directory (a Windows technology) and references Windows-centric tools, terminology, and patterns (e.g., Group Policy, 'Active Directory Sites and Services', 'NTFS permissions', 'SMB', 'Kerberos', 'LDAP', 'OU=Computers', 'SeSecurityPrivilege', SQL Server). There are no Linux command-line examples, nor are Linux/Unix tools or patterns (such as Samba, sssd, or Linux-specific LDAP/Kerberos configuration) mentioned. The documentation assumes a Windows administrative environment and does not address Linux-based integration or management scenarios.
Recommendations
  • Add Linux/Unix-focused examples for integrating Azure NetApp Files with Active Directory, such as configuring sssd, winbind, or Samba for NFS and SMB access.
  • Include references to Linux tools and configuration files (e.g., /etc/krb5.conf, /etc/sssd/sssd.conf) where relevant.
  • Provide parity in instructions for both Windows and Linux administrators, including how to manage Kerberos, LDAP, and SMB integration from Linux systems.
  • Mention Linux equivalents for concepts like 'Group Policy' (e.g., using sssd or pam_ldap for policy enforcement) and 'NTFS permissions' (e.g., POSIX ACLs or NFSv4 ACLs).
  • Clarify when features or settings are relevant to both Windows and Linux clients, and provide guidance for mixed-environment deployments.
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-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses exclusively on NTFS ACLs and references Microsoft/Windows-specific concepts and documentation. There are no examples or mentions of managing SMB permissions from Linux or cross-platform tools, nor is there guidance for Linux administrators. The only external link is to a Microsoft Windows security page, reinforcing a Windows-centric perspective.
Recommendations
  • Include examples or references for managing SMB file permissions from Linux clients, such as using the 'smbcacls' or 'setfacl' tools.
  • Mention cross-platform SMB management tools and how Linux/Unix administrators can interact with NTFS ACLs on Azure NetApp Files.
  • Provide links to relevant Linux documentation or community resources for SMB/NTFS ACL management.
  • Clarify whether and how Linux clients can view or modify NTFS ACLs on Azure NetApp Files SMB volumes.
  • Balance the documentation by addressing both Windows and Linux administrator workflows.
GitHub Create Pull Request
← Previous Page 22 of 36 Next →