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 276-300 of 896 flagged pages
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-08 00:53
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 Windows-specific tools and terminology (such as GUI steps, %PATH%, and Windows user creation) are often mentioned before or in more detail than their Linux equivalents. Some sections, such as user profile updates and environment variable configuration, give more explicit examples for Linux, but Windows instructions are less detailed and rely on generic 'Windows specific tools.' There is a tendency to mention Windows steps first or with more prominence, and some Linux-specific details (like permissions and shell commands) are present, but Windows command-line alternatives (such as PowerShell or CMD commands for environment variables) are missing. Additionally, some database connection examples are platform-agnostic, but the overall structure leans toward Windows-first presentation.
Recommendations
  • Provide explicit Windows command-line examples for tasks such as updating environment variables (e.g., using setx or PowerShell) and searching for binaries, similar to the detailed Linux shell examples.
  • Ensure that Linux and Windows instructions are presented in parallel, with equal detail and prominence, rather than listing Windows steps first or more generically.
  • Include PowerShell or CMD examples for Windows where shell commands are given for Linux, such as finding executable paths or updating user profiles.
  • Clarify any platform-specific differences in installation, configuration, and troubleshooting, ensuring Linux users have parity in guidance and troubleshooting steps.
  • Review the order of presentation to avoid implicit prioritization of Windows over Linux, and consider using tabs or side-by-side formatting for platform-specific 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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively providing instructions and screenshots for Windows environments when managing SMB volumes, such as setting NTFS permissions and modifying SMB share permissions via Microsoft Management Console (MMC). There are no examples or guidance for performing equivalent tasks on Linux clients, nor are Linux tools or workflows mentioned for SMB management. Windows terminology and tools are used throughout, and Linux alternatives are omitted.
Recommendations
  • Include examples and instructions for managing SMB volumes from Linux clients, such as using smbclient, mount.cifs, or setfacl for permissions.
  • Provide screenshots or command-line examples for Linux environments alongside Windows examples.
  • Mention Linux tools and workflows for SMB share management, and clarify any differences in capabilities or limitations.
  • Ensure parity in troubleshooting and access control documentation for both Windows and Linux clients.
  • Add a section on mounting and managing SMB shares from Linux, including authentication and permission management.
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-08 00:53
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 are specific to Windows environments (e.g., PowerShell cmdlets like Get-SmbClientNetworkInterface, Windows Performance Monitor, Hyper-V adapters). References to SMB features and configuration are exclusively tied to Windows OS versions, with no mention of Linux SMB clients (such as Samba), their configuration, or equivalent tools. There are no Linux-specific examples, commands, or performance monitoring guidance, despite SMB being cross-platform.
Recommendations
  • Add equivalent Linux/Samba examples for SMB Multichannel, signing, and encryption configuration and verification.
  • Include Linux command-line tools (e.g., smbclient, smbtorture, nstat, iftop, perf, etc.) for performance monitoring and troubleshooting.
  • Document how to check RSS and NIC capabilities on Linux (e.g., using ethtool, lshw, or ip commands).
  • Provide performance testing instructions using Linux tools (e.g., FIO, iostat, atop) and show example outputs.
  • Reference Linux SMB client support for features like Multichannel and encryption, with links to relevant documentation.
  • Ensure that all best practices and configuration steps are presented for both Windows and Linux environments, or clearly state platform limitations.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell commands are presented before Azure CLI equivalents in feature registration and volume management sections, and some feature registration steps are shown only with PowerShell examples. The Azure portal UI, which is more commonly used by Windows users, is described in detail and presented first in tabbed instructions. There is no explicit mention of Linux-specific tooling or shell environments, and the PowerShell examples use Windows-centric syntax. While Azure CLI examples are present, they are not prioritized or explained in as much detail as PowerShell, and Linux users may find the documentation less approachable.
Recommendations
  • Present Azure CLI examples before PowerShell examples in all sections, as Azure CLI is cross-platform and preferred by many Linux users.
  • Ensure all feature registration and management steps are shown with both Azure CLI and PowerShell commands, with equal detail and explanation.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., bash, zsh) for Linux users.
  • Add notes or links for Linux-specific considerations, such as installation of Azure CLI on Linux, and clarify that PowerShell Core is available cross-platform if PowerShell must be used.
  • Where screenshots of the Azure portal are shown, clarify that the portal is web-based and accessible from any OS.
  • Consider adding a section or appendix with Linux shell scripting examples for common tasks, to further improve parity.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Linux and Windows instructions for mounting NFS volumes, but there is a subtle Windows bias. The Windows section references Windows-specific tools (the 'Mount' command), and the Windows mounting instructions are less detailed than the Linux ones. The Linux section provides explicit mount command examples and fstab configuration, while the Windows section omits step-by-step guidance and does not provide PowerShell or GUI examples. Additionally, the Windows section instructs users to first mount the volume on Linux/Unix and run chmod, which may not be intuitive for Windows-only administrators.
Recommendations
  • Provide a complete, step-by-step Windows mounting example, including prerequisites (such as enabling NFS client features), and clarify how to perform necessary permissions changes from Windows without requiring Linux/Unix access.
  • Include PowerShell and GUI instructions for mounting NFS volumes on Windows, not just the legacy 'Mount' command.
  • Ensure Linux and Windows sections are equally detailed and structured, with parallel examples and troubleshooting tips.
  • Mention Linux tools and patterns (such as autofs, systemd mount units) if Windows tools (like the Mount command) are referenced.
  • Clarify any limitations or differences in NFS support between platforms in a dedicated comparison table.
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-08 00:53
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 usage is linked with PowerShell examples, and the only automation example for REST API is via PowerShell, a Windows-centric tool. There is no mention of Linux-specific tools or shell examples (e.g., Bash, curl, jq) for REST API usage. The Azure portal instructions are platform-neutral, but the CLI section does not clarify shell compatibility or provide Linux-specific context. Windows/PowerShell is referenced before any Linux alternatives, and Linux usage patterns are missing.
Recommendations
  • Add Linux/Bash/curl examples for REST API usage alongside PowerShell.
  • Clarify that Azure CLI commands work on both Windows and Linux, and provide sample commands for Bash.
  • Include references to Linux automation tools (e.g., shell scripts, cron) where PowerShell is mentioned.
  • Provide parity in example code and links for both Windows and Linux users.
  • Avoid presenting Windows/PowerShell tools before Linux equivalents unless justified by user base data.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by providing PowerShell-heavy examples and instructions, referencing Windows-specific tools and policies (such as Group Policy and registry keys), and mentioning Windows Server and AD DS features before or instead of Linux equivalents. There are no Linux-specific command examples or instructions for managing AD connections from Linux environments, and Windows terminology and tools are used throughout without offering parity for Linux administrators.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using ldapmodify, kinit, or samba-tool) for managing AD connections and Kerberos settings.
  • Include instructions for configuring Kerberos encryption types and LDAP settings on Linux clients, such as editing krb5.conf or sssd.conf.
  • Reference Linux tools and configuration files (e.g., sssd, winbind, nslcd) alongside Windows tools like PowerShell and Group Policy.
  • Add troubleshooting steps and best practices for Linux environments, especially for NFS and Kerberos integration.
  • Ensure that examples and guidance for both Windows and Linux are presented in parallel, or at least provide links to Linux-specific documentation.
  • Clarify which steps are platform-agnostic and which require platform-specific actions, so Linux administrators are not left out.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-customer-managed-keys.md .../azure-netapp-files/configure-customer-managed-keys.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides detailed instructions for configuring customer-managed keys for Azure NetApp Files using the Azure Portal, Azure CLI, and Azure PowerShell. The PowerShell section is prominent and detailed, reflecting a Windows-centric approach. The use of Azure PowerShell and references to Windows-specific tooling (PowerShell cmdlets) are present, and examples for Linux-native tools (such as Bash or shell scripting) are not provided. The ordering of examples places PowerShell on equal footing with CLI, but PowerShell is a Windows-first technology. There are no explicit Linux shell or automation examples, and the documentation does not mention Linux-specific considerations or alternatives.
Recommendations
  • Add explicit Bash/shell scripting examples for Linux users alongside Azure CLI examples.
  • Clarify that Azure CLI commands can be run natively on Linux, macOS, and Windows, and provide sample shell scripts for Linux automation.
  • Consider including notes or sections on using the REST API directly with curl or similar Linux-native tools.
  • Where PowerShell is referenced, note that PowerShell Core is cross-platform, but provide guidance for Linux users on installation and usage.
  • Review screenshots and UI references to ensure they are not Windows-specific (e.g., avoid showing only Windows-style dialogs if possible).
  • Add troubleshooting and operational notes relevant to Linux environments, such as file permissions, environment variables, and shell differences.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows Server tools and workflows (Certification Authority, MMC snap-in) for certificate generation and export. There are no instructions or examples for performing these steps on Linux systems, nor are Linux tools or commands mentioned. The guidance assumes a Windows-based environment for Active Directory and certificate management.
Recommendations
  • Add instructions for generating and exporting root CA certificates using common Linux tools (e.g., OpenSSL).
  • Include Linux-based examples for viewing and managing certificates, such as using the 'openssl' command or 'certtool'.
  • Mention Linux-compatible Active Directory integration options and clarify if the process differs for Linux-based AD DS environments.
  • Present both Windows and Linux workflows side-by-side or in separate sections to ensure parity and inclusivity for cross-platform administrators.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page presents quota observation instructions for Windows clients before Linux clients, with detailed references to Windows Explorer and the 'dir' command, while Linux instructions are limited to the 'quota' command. Windows-specific concepts such as Security Identifiers (SID) are mentioned alongside UNIX UIDs/GIDs, and the Next Steps section links to Windows documentation. There is a lack of parity in example depth and tool references between Windows and Linux, and group quota reporting is noted as unsupported, but Linux users are left with only error-based feedback.
Recommendations
  • Present Linux and Windows client instructions in parallel or alternate order to avoid implicit prioritization.
  • Expand Linux examples to include graphical tools (e.g., GNOME Disks, Dolphin file manager) if applicable, and provide more detailed command output samples.
  • Reference Linux equivalents for concepts like SIDs (e.g., UIDs/GIDs) in the Next Steps section.
  • Clarify limitations and workarounds for group quota reporting on Linux, possibly suggesting monitoring scripts or tools.
  • Ensure all diagrams and screenshots have Linux equivalents where possible.
  • Add a table summarizing protocol support and quota observation methods for both platforms.
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: 2026-01-08 00:53
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 presenting Azure PowerShell commands first and exclusively in the feature registration section, with only a brief mention of Azure CLI as an alternative. No explicit Linux shell examples (e.g., Bash) are provided, and the step-by-step instructions focus on GUI interactions typical of Windows environments. There is a lack of parity in command-line instructions for Linux users, and no mention of Linux-specific tools or patterns.
Recommendations
  • Provide equivalent Bash/Azure CLI examples alongside PowerShell commands for all command-line steps.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Include screenshots or instructions for using the Azure CLI in Linux environments.
  • Reorder command-line instructions to present Azure CLI first or in parallel with PowerShell.
  • Add a note clarifying that all operations can be performed from Linux, macOS, or Windows, and link to platform-specific setup guides.
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-08 00:53
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 moderate Windows bias. Windows/Active Directory DNS is consistently presented as the default or recommended configuration, with Microsoft best practices and tools (such as DNS Manager) referenced throughout. Windows-centric tools and command-line examples (e.g., nslookup on Windows, C:\> prompt) are given before or in greater detail than Linux equivalents. Linux/BIND is mentioned only as an alternative, and Linux-specific instructions or troubleshooting steps are minimal or missing. The documentation also references Windows DNS UI elements and features (like 'Delete this record when it becomes stale' and DNS Manager's Advanced View) without Linux/BIND equivalents.
Recommendations
  • Provide Linux/BIND-focused configuration and troubleshooting steps alongside or before Windows/Active Directory DNS instructions, including how to create and manage relevant DNS records (A/AAAA, PTR, SRV, URI) in BIND.
  • Include Linux/BIND equivalents for all Windows DNS Manager UI actions (e.g., how to view TTLs, enable scavenging, or create reverse lookup zones in BIND).
  • Balance command-line examples: For every Windows nslookup example, provide a Linux dig or nslookup example with equivalent detail and explanation.
  • When referencing best practices, include authoritative sources or recommendations for BIND/Linux DNS, not just Microsoft/Windows.
  • Avoid assuming Active Directory DNS as the default; clarify when instructions are specific to Windows environments and provide parallel guidance for Linux/BIND users.
  • Expand troubleshooting sections to include common issues and solutions for BIND/Linux DNS servers, not just Windows DNS.
  • Where possible, use neutral language (e.g., 'DNS server' instead of 'Active Directory DNS server') unless the distinction is necessary.
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-08 00:53
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 consistently referencing Windows/NTFS concepts and tools before their Linux/NFS equivalents, providing more detail and links for Windows features, and omitting practical Linux/NFS examples (e.g., no explicit Linux CLI commands for managing NFSv4.x ACLs). Windows terminology and tools (Active Directory, Windows RPC, NTFS ACLs) are described in greater depth, while Linux/NFS management is mentioned but not exemplified. The guidance and decision matrices also tend to frame choices from a Windows-centric perspective.
Recommendations
  • Add explicit Linux/NFS examples for permission management, such as sample commands for nfs4_getfacl/nfs4_setfacl, chown, chmod, and their usage in real scenarios.
  • Provide equal detail for Linux/NFS concepts as is given for Windows/NTFS, including links to relevant Linux documentation and tools.
  • Balance the order of presentation so that Linux/NFS options and terminology are described before or alongside Windows/NTFS equivalents.
  • Include troubleshooting scenarios and workflows for Linux/NFS environments, not just Windows/Active Directory.
  • Clarify that both Linux and Windows clients are first-class citizens in dual-protocol environments, and avoid language that implicitly prioritizes Windows management endpoints.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias in the feature registration section, where Azure PowerShell commands are presented first and in detail, with Linux/CLI alternatives only briefly mentioned. The registration instructions and examples use PowerShell syntax, which is native to Windows, and the CLI alternative is referenced only as a secondary option. However, the main conversion workflow and client-side instructions are Linux-focused, using Linux mount/umount commands and referencing Linux configuration files.
Recommendations
  • Present Azure CLI examples alongside PowerShell examples, not just as a note, but with full command syntax and output samples.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Where PowerShell commands are shown, provide equivalent Bash/CLI commands in parallel sections or tabs.
  • Clarify that the conversion process is platform-agnostic and that both Windows and Linux administrators can perform the steps using their preferred tools.
  • Consider adding a short section on how Windows clients (if supported) interact with NFS volumes and any differences in remounting or configuration.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits Windows bias by relying on Windows-centric tools (Active Directory, RSAT), providing PowerShell commands for key configuration steps, and referencing Windows patterns (AD DS, gMSA) without Linux equivalents. The instructions for setting Kerberos encryption type on computer accounts are given only in PowerShell, and mention running the command from a domain controller or a PC with RSAT installed, both Windows-specific environments. There is no mention of how to perform equivalent steps from a Linux environment or with cross-platform tools.
Recommendations
  • Provide equivalent instructions for configuring Kerberos encryption type using Linux-native tools (e.g., ldapmodify, samba-tool, or other LDAP utilities).
  • Include examples of managing Active Directory computer accounts from Linux, such as using openldap or samba.
  • Clarify whether all steps requiring PowerShell/RSAT can be performed from Linux, and if so, provide those steps.
  • Mention cross-platform alternatives for AD DS and gMSA, or note any limitations for Linux-only environments.
  • Ensure that Linux examples are given equal prominence and detail as Windows examples, especially for administrative tasks.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias in the section addressing NFS access from Windows clients. It provides explicit PowerShell commands and Windows mount examples, but does not offer equivalent Linux commands or examples for troubleshooting NFS access or performance. The Windows-specific tools and patterns are mentioned exclusively, with no Linux parity in troubleshooting or configuration guidance for similar scenarios.
Recommendations
  • Add equivalent Linux troubleshooting steps and commands for NFS access issues, such as how to optimize folder lookups or address performance problems.
  • Provide Linux mount command examples (e.g., using 'mount' with appropriate options) alongside Windows examples, especially in sections discussing mounting volumes and performance tuning.
  • Ensure that any Windows-specific configuration advice is paired with Linux-specific advice where relevant, such as adjusting NFS client settings for performance.
  • Review all examples and ensure both Windows and Linux are represented equally, especially in sections where only one platform is currently covered.
  • Consider reordering examples so that Linux and Windows are presented together or alternate which platform is presented first, to avoid implicit prioritization.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
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 verification steps use PowerShell commands, instructions explicitly mention rebooting Windows systems, and there is no mention of Linux or macOS clients, nor any SMB tooling or verification steps for those platforms. Windows tools and patterns are referenced exclusively.
Recommendations
  • Add equivalent verification steps for Linux (e.g., using smbclient, mount.cifs, or checking mount options).
  • Clarify whether Linux or macOS SMB clients require any action (such as remounting) after enabling Continuous Availability.
  • Include examples of how to check CA status from non-Windows systems.
  • Mention any platform-specific limitations or considerations for non-Windows clients.
  • Reorder instructions to be platform-neutral, or provide parallel steps for each major OS.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/monitor-volume-capacity.md ...articles/azure-netapp-files/monitor-volume-capacity.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation presents Windows client instructions before Linux, with more detailed steps and screenshots for Windows tools (File Explorer, dir command). Windows-specific tools and patterns (File Explorer, mapped drive properties) are described in detail, while Linux instructions are more concise and limited to the df command. REST API usage references PowerShell explicitly, but does not mention Linux shell or curl examples.
Recommendations
  • Present Linux and Windows client instructions in parallel, or alternate which is described first.
  • Expand Linux section to include additional commands (e.g., ls, stat, du with caveats) and troubleshooting tips.
  • Provide REST API usage examples using curl/bash in addition to PowerShell.
  • Include screenshots for Linux commands similar to Windows, ensuring parity in visual aids.
  • Avoid referencing Windows tools (File Explorer, mapped drive) exclusively; mention Linux equivalents (e.g., Nautilus, Dolphin) if relevant.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows Active Directory as the only supported KDC, prioritizing Windows terminology and tools (such as Event Viewer, MMC, PowerShell, and setspn), and providing detailed workflows and troubleshooting steps using Windows-centric utilities. Linux equivalents, examples, and tools are either missing or mentioned only in passing, with little guidance for Linux administrators. Windows patterns and tools are introduced before any Linux alternatives, and practical Linux command-line examples (e.g., kinit, klist, keytab management) are largely absent.
Recommendations
  • Explicitly state support or limitations for non-Windows KDCs (such as MIT or Heimdal) and provide guidance for integrating Linux-based KDCs if possible.
  • Include Linux-focused examples for Kerberos configuration, such as keytab management (ktutil), principal creation, and troubleshooting using Linux tools (e.g., journalctl, systemd logs, klist, kinit).
  • Provide Linux command-line examples for mounting NFS shares with Kerberos, including sample krb5.conf and keytab file management.
  • Mention and explain Linux equivalents for Windows tools (e.g., setspn vs. ktutil, Event Viewer vs. syslog/journalctl) in relevant sections.
  • Balance troubleshooting guidance by including common Linux error messages and diagnostic steps alongside Windows-centric instructions.
  • Clarify any Azure NetApp Files limitations regarding Linux integration, and offer best practices for Linux environments where possible.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/migrate-volumes.md ...ob/main/articles/azure-netapp-files/migrate-volumes.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 a PowerShell sample script as the only referenced automation workflow, using Azure PowerShell cmdlets as the primary example for feature registration, and not offering equivalent Linux/bash examples or scripts. The Azure CLI is mentioned only as an alternative, and no bash or Linux shell scripts are provided. There is also no mention of Linux-native tools or guidance for users working in non-Windows environments.
Recommendations
  • Provide equivalent bash or shell script examples for all PowerShell scripts, especially for the migration assistant workflow.
  • Present Azure CLI commands alongside PowerShell commands, not just as a secondary note, and include full CLI command examples for all steps.
  • Explicitly mention Linux/macOS compatibility and provide guidance for users on those platforms.
  • Ensure that any downloadable sample scripts (such as the migration assistant workflow) are available in both PowerShell and bash/CLI formats.
  • Review all step-by-step instructions to ensure parity between Windows and Linux environments, including any prerequisites or environment setup steps.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/generate-user-group-quota-reports.md ...zure-netapp-files/generate-user-group-quota-reports.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Azure PowerShell examples for feature registration and status checking, mentioning PowerShell commands first and in detail, while only briefly referencing Azure CLI as an alternative. There are no Linux-specific or cross-platform command-line examples, and no mention of Linux tools or patterns for quota reporting or management. The instructions and screenshots focus on the Azure portal and PowerShell workflows, which are more familiar to Windows users.
Recommendations
  • Provide explicit Azure CLI examples for feature registration and status checking alongside PowerShell, with equal prominence.
  • Include Linux shell command examples (e.g., using curl with REST API, az CLI) for quota report generation and management.
  • Clarify that all steps can be performed from Linux/macOS environments using Azure CLI or REST API, not just PowerShell.
  • Add notes or sections highlighting cross-platform compatibility and usage patterns.
  • Ensure screenshots and UI descriptions do not assume a Windows environment.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively describing the configuration of asymmetric name mapping using Windows tools (Active Directory Users and Computers MMC), without mentioning or providing Linux-based alternatives for editing LDAP attributes. The instructions and screenshots focus on Windows environments first, and there is no guidance for administrators who may be managing LDAP from Linux or UNIX systems.
Recommendations
  • Include instructions for editing LDAP user attributes using Linux tools (e.g., ldapmodify, Apache Directory Studio, or command-line utilities).
  • Provide Linux/UNIX-based examples and screenshots for configuring asymmetric name mapping in LDAP.
  • Present both Windows and Linux methods in parallel, or clearly indicate cross-platform options to ensure parity.
  • Reference relevant Linux documentation or tools for managing LDAP user attributes.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/object-rest-api-browser.md ...articles/azure-netapp-files/object-rest-api-browser.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-specific instructions and tools. The certificate installation steps are tailored exclusively to Windows (using Edge browser and Windows certificate store), and the S3 Browser tool is Windows-only. Although AWS CLI installation is covered for both Windows and Linux, the overall workflow and examples assume a Windows environment, with Linux users receiving less detailed guidance.
Recommendations
  • Provide certificate installation instructions for Linux, including how to export and trust certificates using common browsers (e.g., Firefox, Chrome) and how to add certificates to Linux trust stores (e.g., update-ca-certificates on Debian/Ubuntu, trust anchor on RHEL/CentOS).
  • Mention and provide examples for S3-compatible clients available on Linux (e.g., s3cmd, rclone, Cyberduck) in addition to or instead of S3 Browser.
  • Ensure that all steps, especially those involving certificate handling, are accompanied by equivalent Linux commands and GUI instructions.
  • Avoid assuming the use of Windows-specific tools or patterns (such as the Windows certificate store) as the default; present cross-platform options side by side.
  • Where possible, use neutral language and ordering (e.g., 'For Linux, do X. For Windows, do Y.') rather than always listing Windows first.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. SMB/Windows scenarios are described in greater detail, with explicit mention of Windows-only workloads (e.g., Microsoft SQL Server not Linux SQL Server) and recommendations for using SMB shares with Windows VMs. Linux equivalents are often referenced generically or as secondary options, and some examples or guidance for Linux-specific tools or patterns are missing. The order of presentation and specificity favors Windows environments, especially in the SMB sections.
Recommendations
  • Provide explicit Linux examples and guidance for all scenarios, especially where only Windows/SMB examples are given.
  • When mentioning supported workloads (e.g., SQL Server), clarify Linux support status and provide alternatives or parity guidance.
  • Balance the order of presentation so that Linux/NFS and Windows/SMB scenarios are treated equally, or alternate which is presented first.
  • Include Linux-specific troubleshooting steps, configuration examples, and best practices where Windows/SMB guidance is given.
  • Avoid language that implies Windows is the default or preferred platform unless technically justified.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
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 documentation, with no mention of Linux SMB tools, POSIX ACLs, or cross-platform management approaches. All examples and links are Windows-centric, and there is no guidance for Linux administrators or parity in tooling.
Recommendations
  • Include examples of managing SMB file permissions from Linux clients (e.g., using smbclient, setfacl, or mount.cifs options).
  • Reference Linux tools and commands for viewing and modifying SMB/NTFS ACLs, such as 'smbcacls' or 'getfacl'.
  • Provide guidance on interoperability between Windows and Linux SMB clients, including any limitations or considerations.
  • Add links to relevant Linux documentation or community resources for managing SMB permissions.
  • Clarify whether Azure NetApp Files supports POSIX ACLs or how Linux clients interact with NTFS ACLs in this context.
GitHub Create Pull Request
← Previous Page 12 of 36 Next →