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 201-225 of 896 flagged pages
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azacsnap-cmd-ref-backup.md ...articles/azure-netapp-files/azacsnap-cmd-ref-backup.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. In the section describing the --flush option, Windows-specific instructions and tools (CMD, PowerShell, Task Scheduler) are listed first and in detail, including code samples and step-by-step guidance for elevation. In contrast, Linux is mentioned only briefly, with a single sentence stating that I/O is flushed using the sync command, without any example or further explanation. The Windows elevation methods (CMD, PowerShell, Task Scheduler) are described extensively, while no equivalent Linux privilege escalation (e.g., sudo) or automation methods are provided. This prioritization and depth of Windows content, along with the use of Windows tools and patterns, indicate a bias toward Windows users.
Recommendations
  • Provide Linux-specific examples for running azacsnap with --flush, including use of sudo for privilege escalation.
  • Include sample commands and automation options for Linux, such as using cron jobs for scheduled backups.
  • Balance the order and depth of Windows and Linux instructions, presenting both platforms equally and side-by-side where possible.
  • Offer troubleshooting tips and privilege requirements for Linux, similar to the detailed Windows guidance.
  • Mention Linux log file locations and result file handling, if they differ from Windows, to ensure parity.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azacsnap-configure-database.md ...cles/azure-netapp-files/azacsnap-configure-database.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides detailed, step-by-step instructions for SAP HANA, Oracle, and IBM Db2 on Linux, but the Microsoft SQL Server section is notably Windows-centric. It exclusively references Windows tools (e.g., .\azacsnap.exe), uses Windows command syntax, and omits Linux-based SQL Server examples. The SQL Server section is much shorter and lacks parity in detail compared to the Linux database sections. There is no mention of running AzAcSnap or SQL Server on Linux, nor are Linux shell commands or patterns provided for SQL Server. The documentation also lists the Microsoft SQL Server tab last, but its content is Windows-only, and references to configuration and testing use Windows paths and commands.
Recommendations
  • Add examples and instructions for configuring AzAcSnap with SQL Server running on Linux, including shell commands and Linux paths.
  • Provide parity in detail for SQL Server as is done for SAP HANA, Oracle, and Db2, including user setup, permissions, and environment configuration on Linux.
  • Explicitly mention cross-platform support for AzAcSnap with SQL Server, and clarify any differences in setup between Windows and Linux.
  • Include both Windows and Linux command syntax for SQL Server examples, or provide tabs for each OS where relevant.
  • Avoid using only Windows-specific tools and patterns (e.g., .\azacsnap.exe) in SQL Server documentation; show Linux equivalents (e.g., ./azacsnap) where appropriate.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azacsnap-installation.md ...n/articles/azure-netapp-files/azacsnap-installation.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides both Linux and Windows instructions for installing and managing AzAcSnap, but there are signs of Windows bias. Windows instructions (including GUI references and use of Windows-specific tools like 'where' and '%PATH%') are presented with equal or greater detail than Linux equivalents. Some steps (such as user creation and environment variable configuration) are described in more depth for Windows, and Windows tools are mentioned explicitly. There is also a tendency to mention Windows before Linux in some sections, and some Linux-specific troubleshooting or advanced configuration details are missing compared to Windows.
Recommendations
  • Ensure Linux instructions are as detailed and explicit as Windows instructions, including troubleshooting and advanced configuration.
  • Provide Linux-first ordering in examples and step lists, or alternate the order to avoid implicit prioritization.
  • Include Linux equivalents for all Windows tools mentioned (e.g., use 'which' or 'find' instead of 'where').
  • Add more Linux-specific guidance for common issues, such as permissions, SELinux/AppArmor, and service management.
  • Avoid referencing Windows GUI steps unless there is a Linux GUI equivalent, or clarify that the Linux process is command-line only.
  • Review all examples to ensure parity in clarity, completeness, and troubleshooting for both platforms.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-government.md ...b/main/articles/azure-netapp-files/azure-government.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell connection instructions and listing multiple PowerShell command variants, while omitting equivalent Linux shell or automation examples. The PowerShell section is more extensive than the Azure CLI section, and there is no mention of Bash, Linux-specific tools, or cross-platform scripting approaches. The ordering also places PowerShell after Azure CLI, but the PowerShell section is more detailed and tool-specific, reinforcing a Windows-centric approach.
Recommendations
  • Add explicit Bash/Linux shell examples for connecting to Azure Government, such as using Azure CLI on Linux or macOS.
  • Include notes or examples for using Azure NetApp Files with automation tools common in Linux environments (e.g., curl for REST API, Python scripts).
  • Balance the PowerShell section with equivalent Linux command-line instructions and clarify cross-platform compatibility for all commands.
  • Mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, and provide installation links for each.
  • Consider reordering sections or providing parity in detail between PowerShell and CLI/Linux instructions.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a Windows bias in several ways: all examples and instructions for managing SMB volume permissions and share properties exclusively use Windows tools and interfaces (MMC, Windows SMB client), with no mention of Linux SMB clients or cross-platform alternatives. Windows patterns (e.g., 'net view', Windows File Browser) are referenced as the default, and there are no Linux-specific instructions or screenshots. The page assumes Windows environments for access control and management, omitting guidance for Linux users who may need to mount or manage SMB volumes.
Recommendations
  • Add equivalent instructions and screenshots for managing SMB permissions and shares using Linux tools (e.g., smbclient, mount.cifs, setfacl).
  • Include examples of mounting and accessing SMB volumes from Linux clients, covering authentication and permission management.
  • Reference cross-platform SMB management utilities and clarify any differences in feature support or behavior between Windows and Linux clients.
  • Ensure that any command-line examples (such as 'net view') are paired with Linux equivalents (e.g., 'smbclient -L').
  • Explicitly state any limitations or considerations for Linux clients when using features like SMB3 encryption, access-based enumeration, or continuous availability.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-quickstart-set-up-account-create-volumes.md ...-netapp-files-quickstart-set-up-account-create-volumes.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides examples for Azure Portal, PowerShell, Azure CLI, ARM templates, and Terraform. However, PowerShell is featured prominently and is mentioned before Azure CLI in most sections. PowerShell is a Windows-centric tool, and its usage is described in detail, including installation notes and references to Cloud Shell sessions. There is no mention of Bash, Linux-specific shell environments, or WSL (Windows Subsystem for Linux). The CLI examples use generic shell variables but do not clarify Linux-specific nuances or provide Bash-specific guidance. Windows tools and patterns (PowerShell, Cloud Shell in PowerShell mode) are referenced more frequently and with more detail than Linux equivalents.
Recommendations
  • Provide explicit Bash/Linux shell examples alongside PowerShell, especially for Azure CLI usage.
  • Clarify that Azure CLI commands work natively on Linux/macOS and provide instructions for installation on those platforms.
  • Include references to Bash scripting and Linux terminal environments where appropriate.
  • Balance the order of examples so that Azure CLI (cross-platform) is presented before or alongside PowerShell, not after.
  • Mention WSL for Windows users who may prefer a Linux-like environment.
  • Add notes or links for Linux users about prerequisites, environment setup, and troubleshooting.
  • Avoid assuming PowerShell as the default command-line environment; make it clear that both PowerShell and Bash are supported.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
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 is given equal prominence to Azure CLI without clarifying that PowerShell is primarily a Windows-centric tool (though cross-platform, it is less commonly used on Linux). There are no Linux- or Bash-specific examples, and the CLI tools section does not mention Linux-native tools or patterns, nor does it provide Linux-first guidance. The documentation does not acknowledge differences in usage or installation between Windows and Linux environments.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide installation/use instructions for both Windows and Linux.
  • Clarify that PowerShell, while cross-platform, is more commonly used on Windows, and provide Bash or shell script examples for Linux users.
  • Add Linux/Bash command-line examples alongside or before PowerShell examples.
  • Include a section or note on how to use the SDKs and CLI tools in Linux environments.
  • Highlight any Linux-specific considerations or prerequisites for using Azure NetApp Files tools.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
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 is a subtle Windows bias. The Windows section is given its own heading and example, while the Linux section is more comprehensive. However, the Windows instructions reference mounting on Linux first and require Unix/Linux tools (chmod), and the Windows mount example uses the Windows-specific 'Mount' command. There is no PowerShell-heavy bias, but Windows tools are mentioned exclusively for Windows, and the Linux example is more detailed. The order of sections is Linux first, but Windows instructions depend on Linux steps, which may be confusing for Windows-only admins.
Recommendations
  • Provide a standalone Windows example that does not require mounting on Linux first, or clarify why this step is necessary.
  • Include more details about Windows NFS client limitations and alternatives, such as third-party NFS clients or SMB as a preferred protocol.
  • Add troubleshooting steps specific to Windows NFS mounts, including common errors and solutions.
  • Ensure parity in example detail: expand Windows mount command options and explain their effects, similar to the Linux section.
  • Consider adding PowerShell examples for mounting NFS volumes on Windows, if supported, to match the command-line focus for Linux.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-resize-capacity-pools-or-volumes.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-resize-capacity-pools-or-volumes.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias. REST API automation is linked with PowerShell examples, and the only explicit scripting example for REST API usage is a PowerShell link. There is no mention of Linux-specific tools (such as Bash, curl, or shell scripting) for REST API usage, nor are Linux automation patterns referenced. The Azure CLI section is platform-neutral, but REST API automation is presented with a Windows-first approach by highlighting PowerShell. No Linux/Bash example is provided for REST API usage.
Recommendations
  • Add Linux/Bash examples for REST API usage (e.g., using curl or az rest).
  • Provide links to Linux shell scripting guides for Azure NetApp Files REST API automation.
  • Ensure REST API automation examples are presented in a platform-neutral way, or offer both PowerShell and Bash/curl examples side-by-side.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Avoid referencing PowerShell as the sole automation tool for REST API usage; mention alternatives available on Linux.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing PowerShell and its module update instructions before mentioning Linux equivalents. While Azure CLI is mentioned, there are no explicit Linux shell examples or instructions, and PowerShell is called out specifically with a command and a link. No Linux-specific tools or patterns are discussed, and the update instructions for CLI are generic, not showing Linux command syntax or package management details.
Recommendations
  • Provide explicit Linux shell (bash) examples for Azure CLI usage, including update instructions using package managers (e.g., apt, yum).
  • Mention PowerShell and Azure CLI in parallel, with equal detail and prominence, and clarify cross-platform compatibility.
  • Include notes or examples for Linux users, such as how to install/update Azure CLI on Linux and how to run commands from a Linux terminal.
  • Avoid referencing PowerShell-specific commands (like 'Update-Module Az.NetAppFiles') without giving equivalent instructions for Linux environments.
  • Add screenshots or terminal snippets showing Linux usage where applicable.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All operational examples, commands, and monitoring instructions use Windows tools (e.g., PowerShell cmdlets like Get-SmbClientNetworkInterface, Windows Performance Monitor, and references to Windows Server versions). There are no Linux or macOS SMB client examples, nor any mention of equivalent Linux tools or configuration patterns. The narrative assumes Windows as the default client environment for SMB, omitting Linux-specific guidance for performance tuning, monitoring, or feature support.
Recommendations
  • Add equivalent Linux SMB client examples (e.g., using smbclient, mount.cifs, or relevant configuration files).
  • Include Linux commands for checking multichannel support, RSS capability, and performance monitoring (such as ethtool, nstat, or sysfs entries).
  • Describe how to enable and verify SMB Multichannel, Signing, and Encryption on Linux clients (e.g., with Samba configuration).
  • Provide Linux performance monitoring guidance (e.g., using iostat, atop, or netstat) and how to interpret results.
  • Reference Linux documentation and tools alongside Windows, ensuring parity in troubleshooting and optimization steps.
  • Clarify any differences in feature support or limitations for non-Windows clients.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-application-volume-group-sap-hana-api.md ...les/configure-application-volume-group-sap-hana-api.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively providing examples that use Azure CLI and jq, tools commonly available and pre-installed on Windows and Azure Cloud Shell. There are no explicit Linux or cross-platform shell examples, nor are alternative Linux-native tools or patterns (such as bash-only, curl-only, or Python requests) provided. The instructions assume the use of Azure CLI, which is available on Linux but is more commonly associated with Windows and Azure environments. No PowerShell-specific commands are present, but the overall workflow and examples are tailored to Azure CLI and jq, with no mention of Linux-specific nuances, such as authentication via managed identities, environment variable handling, or alternative JSON parsing tools. The documentation does not mention or show how to perform these steps on Linux distributions, nor does it provide parity for Linux users who may not use Azure CLI or jq.
Recommendations
  • Add explicit Linux shell examples, such as using curl with environment variables and native Linux authentication methods.
  • Provide alternative JSON parsing examples using tools like 'grep', 'awk', or 'python -m json.tool' for environments where jq is not installed.
  • Include a note or section on installing Azure CLI and jq on Linux, or alternatives for users who prefer not to use these tools.
  • Show how to perform authentication and API calls using Python requests or other cross-platform scripting languages.
  • Clarify that the examples are cross-platform and provide guidance for both Windows and Linux users, including any differences in command syntax or environment setup.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page shows a moderate Windows bias. While the main NFS client configuration and mounting examples are for Linux (RHEL/Ubuntu), all Active Directory and Kerberos account management instructions rely exclusively on Windows tools and PowerShell commands (e.g., Set-ADComputer). There is no mention of how to perform equivalent operations from Linux or with cross-platform tools, and Windows RSAT is referenced as a requirement for management. The documentation assumes AD DS as the Kerberos provider and does not discuss alternatives or Linux-based KDCs.
Recommendations
  • Provide equivalent instructions for managing Kerberos encryption types and computer accounts using Linux tools (such as ldapmodify, samba-tool, or other cross-platform utilities).
  • Mention or link to documentation for configuring Kerberos with non-AD KDCs, if supported.
  • Clarify whether all steps requiring PowerShell/RSAT can be performed from Linux, and if so, provide those examples.
  • Reorder sections to present Linux client configuration and mounting before Windows/AD management steps, or provide parity in example order.
  • Explicitly state any platform limitations or requirements for AD DS/RSAT so Linux-only administrators can plan accordingly.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-ldap-extended-groups.md ...s/azure-netapp-files/configure-ldap-extended-groups.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing almost exclusively on Active Directory Domain Services (AD DS) and Microsoft Entra Domain Services, both Windows-centric LDAP implementations. It references Windows tools (Ntdsutil.exe, MMC snap-in, Multi-valued String Editor, Active Directory Attribute Editor) for configuration and management, and provides detailed instructions and screenshots for these. Linux equivalents (such as OpenLDAP) are explicitly stated as unsupported, and there are no examples or screenshots for managing POSIX attributes or LDAP configuration from a Linux environment. Linux client configuration is only briefly mentioned and deferred to other documentation.
Recommendations
  • Add examples and screenshots for managing POSIX attributes using Linux tools (e.g., ldapmodify, phpldapadmin, or command-line utilities).
  • Clarify how Linux administrators can prepare their LDAP servers or integrate with AD DS, including any required schema extensions or attribute mappings.
  • Provide troubleshooting steps and error messages relevant to Linux LDAP servers and clients, even if only to clarify limitations.
  • If OpenLDAP and other third-party LDAP servers are unsupported, explain the technical reasons and suggest possible workarounds or alternatives for Linux-heavy environments.
  • Ensure that Linux client configuration steps are given equal prominence and detail as Windows/AD DS steps, including explicit configuration file examples and common pitfalls.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows Server tools (Certification Authority, MMC snap-in) for certificate management, omitting any Linux-based methods or examples. All certificate generation and export instructions are Windows-centric, with no mention of OpenSSL or other cross-platform alternatives. The guidance assumes the use of Windows Active Directory and does not provide parity for Linux administrators.
Recommendations
  • Add Linux-based instructions for generating and exporting root CA certificates, such as using OpenSSL.
  • Include examples of managing certificates on Linux systems, including file locations and export formats.
  • Mention cross-platform tools and clarify that LDAP over TLS can be configured using non-Windows environments.
  • Provide parity in screenshots and step-by-step instructions for both Windows and Linux environments.
  • Explicitly state any platform requirements or limitations, and offer guidance for mixed-OS environments.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. PowerShell examples and commands are provided before Azure CLI equivalents in several sections, and feature registration is demonstrated primarily with Azure PowerShell. The use of Windows-centric terminology (e.g., Active Directory, domain controllers) is prominent, and screenshots and walkthroughs focus on the Azure Portal (which is platform-agnostic but often associated with Windows workflows). Linux-specific patterns, troubleshooting, or command-line examples are not highlighted, and there is no mention of Linux shell scripting or integration with Linux-native tools.
Recommendations
  • Provide Linux shell (bash) examples alongside or before PowerShell examples, especially for feature registration and querying.
  • Expand CLI coverage: For every PowerShell command, offer an equivalent Azure CLI (bash-friendly) command and make it clear both are supported.
  • Include Linux-specific troubleshooting tips, especially for NFS volumes and DNS/domain controller connectivity.
  • Add notes or sections on using the documentation from Linux environments, including any differences in authentication, tooling, or scripting.
  • Ensure that examples and screenshots do not implicitly assume a Windows environment (e.g., avoid only showing PowerShell or Windows-style paths).
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/convert-nfsv3-nfsv41.md ...in/articles/azure-netapp-files/convert-nfsv3-nfsv41.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a bias toward Windows environments in the feature registration section, where Azure PowerShell commands are presented first and in detail, while Azure CLI (more commonly used on Linux) is only briefly mentioned. The registration examples and instructions are PowerShell-centric, and there is no parity in showing CLI commands or Linux-native workflows for feature registration. However, the actual NFS conversion steps and client-side instructions are Linux-focused, using Linux mount/umount commands and examples.
Recommendations
  • Provide full Azure CLI examples for feature registration, including command syntax and output, alongside PowerShell examples.
  • Present Azure CLI instructions before or alongside PowerShell instructions to avoid Windows-first ordering.
  • Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and link to installation guides for non-Windows platforms.
  • Ensure all administrative steps (not just client-side) have both PowerShell and CLI examples to support cross-platform users.
  • Review other sections for subtle Windows-centric language or assumptions, and clarify where steps are platform-agnostic.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. Most command-line examples use PowerShell, and references to Windows tools and policies (e.g., Group Policy, registry keys) are prevalent. Windows terminology and features are introduced before or instead of Linux equivalents, and there are no concrete Linux-specific examples or instructions for managing Active Directory connections, Kerberos, or LDAP from Linux environments. The documentation assumes familiarity with Windows Server and Active Directory concepts, with limited guidance for Linux administrators.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using 'ldapsearch', 'kinit', 'adcli', or 'realm' for Kerberos and LDAP operations).
  • Include instructions for configuring Kerberos encryption types and LDAP settings on Linux clients, not just Windows (e.g., editing '/etc/krb5.conf', using 'authconfig', etc.).
  • Reference Linux tools and configuration files (such as '/etc/krb5.conf', '/etc/ldap.conf', and 'sssd') alongside Windows Group Policy and registry settings.
  • Add troubleshooting steps and best practices for Linux environments, including how to handle Kerberos ticket lifetimes and LDAP query timeouts on Linux clients.
  • Clarify which features and settings are relevant or different for Linux-based SMB/NFS clients, especially in mixed environments.
  • Balance examples and terminology so that both Windows and Linux administrators can follow the documentation without needing to cross-reference external Linux guides.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools (Active Directory Users and Computers MMC snap-in) are referenced exclusively for managing LDAP POSIX attributes, and step-by-step instructions are provided only for Windows environments. There are no equivalent Linux examples or instructions for managing LDAP attributes or accessing similar functionality. The order of presentation and screenshots also prioritize Windows tools and workflows, with no mention of Linux alternatives for directory or attribute management.
Recommendations
  • Add instructions and examples for managing LDAP POSIX attributes using common Linux tools (e.g., ldapmodify, ldapadd, phpldapadmin, or command-line utilities).
  • Provide Linux-based workflows and screenshots for viewing and editing LDAP attributes, such as using openldap tools or other cross-platform solutions.
  • Ensure that both Windows and Linux methods are presented in parallel, or at least mention Linux alternatives when describing Windows-specific steps.
  • Clarify which steps are OS-agnostic and which require platform-specific tools, and provide links or references to Linux documentation where appropriate.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/default-individual-user-group-quotas-introduction.md ...s/default-individual-user-group-quotas-introduction.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. In the 'Observing user quota settings and consumption' section, Windows client instructions and screenshots are presented before Linux client instructions. Windows-specific tools (Windows Explorer, dir command) are mentioned explicitly, while the Linux section only references the quota(1) command. There is no mention of Linux file managers or alternative CLI tools. The documentation also references Windows security identifiers (SID) before UNIX user IDs (UID) when describing individual user quotas. The 'Next steps' section links to Windows-specific documentation ('Security identifiers') without Linux equivalents.
Recommendations
  • Present Linux and Windows client instructions in parallel or alternate their order to avoid implicit prioritization.
  • Include examples using common Linux file managers (e.g., Nautilus, Dolphin) to observe quotas, if supported.
  • Reference both UNIX user IDs (UID) and Windows SIDs equally when describing quota assignment.
  • Provide links to Linux documentation or man pages (e.g., for GID, UID, quota tools) in the 'Next steps' section.
  • Clarify any differences in user experience between Linux and Windows clients, and provide troubleshooting steps for both platforms.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
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 management, mentioning Azure CLI only in passing without examples, and omitting any Linux-specific guidance or command-line patterns. The focus on PowerShell and lack of Linux/Unix shell examples may disadvantage users who primarily use Linux environments.
Recommendations
  • Add explicit Azure CLI command examples alongside PowerShell for all steps (e.g., feature registration, status check, unregistration).
  • Include Linux/Unix shell usage patterns, such as how to use az CLI from bash or other shells.
  • Clarify that both PowerShell and CLI approaches are supported and provide guidance for users on Linux systems.
  • Consider adding screenshots or terminal outputs from Linux environments to improve parity.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
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, referencing Microsoft best practices, and providing detailed Windows-centric examples and screenshots. Windows tools (nslookup) are explained first and in more detail, with Linux tools (dig) covered only briefly. Several operational and troubleshooting steps are described solely in the context of Windows DNS Manager, with little or no equivalent guidance for Linux/BIND environments.
Recommendations
  • Provide Linux/BIND-specific configuration and troubleshooting steps alongside Windows/Active Directory instructions, including screenshots of BIND or other common Linux DNS management tools.
  • When describing DNS record management (creation, TTL, scavenging), include explicit instructions for both Windows DNS Manager and BIND/named.conf workflows.
  • In sections where Windows tools (e.g., nslookup) are explained in detail, offer equally detailed examples and explanations for Linux tools (e.g., dig), including advanced usage and output interpretation.
  • Avoid always referencing Microsoft best practices first; instead, present guidance for both Windows and Linux DNS environments in parallel.
  • Where screenshots or UI walkthroughs are provided for Windows DNS Manager, add equivalent examples for Linux-based DNS management (e.g., Webmin, command-line BIND tools).
  • Clarify any Azure NetApp Files features that are only supported with Microsoft DNS, and suggest workarounds or alternatives for Linux/BIND users where possible.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias: Windows/NTFS concepts and tools (Active Directory, Windows RPC, NTFS ACLs) are described in detail and often mentioned before or more prominently than their Linux/NFS equivalents. Windows-centric terminology (NTFS, SID, Windows RPC) is used throughout, and there are references to Windows tools and management methods (Windows security properties tab, Windows RPC calls) without equivalent Linux GUI or tool examples. Linux/NFS management is described as CLI-only, with less detail and no example commands or screenshots. There are no explicit Linux-focused permission management examples, and the documentation assumes Active Directory as the primary identity source, with limited support for local Linux users.
Recommendations
  • Provide Linux/NFS permission management examples, including sample commands (e.g., chown, chmod, nfs4_getfacl, nfs4_setfacl) and screenshots of Linux tools where appropriate.
  • Balance the explanation of Windows and Linux identity sources, including more detail on LDAP and Linux-based directory services (such as OpenLDAP or local /etc/passwd integration).
  • Offer parity in describing GUI and CLI management for both platforms, e.g., mention Linux desktop ACL management tools if available.
  • Clarify limitations and alternatives for Linux/NFS users and groups, and provide guidance for environments that do not use Active Directory.
  • Reorder sections or tables to avoid always listing Windows/NTFS concepts first, and ensure NFS/Linux concepts are given equal prominence.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. SMB/Windows-specific workloads (Citrix App Layering, FSLogix, MSIX app attach, Microsoft SQL Server) are listed for SMB Continuous Availability, with explicit exclusion of Linux SQL Server. SMB recommendations and examples are focused on Windows VMs, while Linux is only mentioned in the context of NFS. For Boomi, SMB is recommended for Windows VMs and NFS for Linux VMs, but no Linux SMB guidance is provided. The page generally presents Windows/SMB options before Linux/NFS equivalents and omits Linux alternatives for some features.
Recommendations
  • Provide Linux equivalents or guidance for SMB-based workloads, including any supported scenarios for Linux SMB clients.
  • Include examples and recommendations for Linux SQL Server if supported, or clarify the limitations.
  • Present NFS/Linux options alongside SMB/Windows options, rather than after or as an alternative.
  • Expand documentation to cover Linux-specific tools, patterns, and best practices for application resilience on Azure NetApp Files.
  • Ensure that recommendations for high availability and failover are balanced between Windows and Linux environments.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-smb.md ...-docs/blob/main/articles/azure-netapp-files/faq-smb.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page for Azure NetApp Files SMB FAQs demonstrates a strong Windows bias. Most examples, troubleshooting steps, and tool references are exclusively for Windows environments (e.g., MMC, Active Directory Users and Computers, Windows Server, DFS Namespace, Windows updates). There are no Linux-specific instructions, examples, or mentions of Linux SMB clients or tools (such as smbclient, mount.cifs, or Samba). The documentation assumes a Windows-centric audience and omits guidance for Linux users who may need to access SMB shares or integrate with Active Directory.
Recommendations
  • Add Linux-specific examples for accessing SMB shares (e.g., using smbclient, mount.cifs, or gvfs-smb).
  • Include troubleshooting steps and best practices for Linux SMB clients.
  • Mention Linux-compatible tools for managing SMB shares and sessions (such as smbstatus, smbcacls, etc.).
  • Clarify Active Directory integration steps for Linux environments (e.g., using winbind, realmd, or sssd).
  • Provide parity in documentation by listing both Windows and Linux approaches for common tasks (mounting, permissions, diagnostics).
  • Explicitly state any limitations or considerations for Linux clients when using Azure NetApp Files SMB volumes.
GitHub Create Pull Request
← Previous Page 9 of 36 Next →