Azure Netapp Files

459
Total Pages
366
Linux-Friendly Pages
93
Pages with Bias
20.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

228 issues found
Showing 176-200 of 228 flagged pages
Azure Netapp Files Understand path lengths in Azure NetApp Files ...articles/azure-netapp-files/understand-path-lengths.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias in its coverage of SMB path length management. Windows-specific tools, dialogs, and registry edits are described in detail, with screenshots and step-by-step instructions for extending path limits. Linux/NFS examples are present but less detailed, and there are no equivalent instructions for extending SMB path limits on non-Windows clients. Windows terminology and tooling (CMD, registry, Group Policy) are referenced exclusively or before Linux equivalents. Linux/NFS examples focus on character byte size, but SMB management is almost entirely Windows-centric.
Recommendations
  • Add explicit instructions or notes for managing SMB path limits on Linux/macOS clients, including any relevant mount options or limitations.
  • Provide parity in example commands for querying or troubleshooting SMB path lengths on Linux/macOS (e.g., using smbclient, mount.cifs, or relevant utilities).
  • Include screenshots or error messages from Linux/macOS environments where applicable, not just Windows dialogs.
  • Clarify whether the registry and Group Policy steps are only relevant for Windows, and suggest alternatives or limitations for other platforms.
  • Reorder or balance examples so that Linux/NFS and Windows/SMB are given equal prominence and detail.
GitHub Create Pull Request
Azure Netapp Files Troubleshoot volume errors for Azure NetApp Files ...in/articles/azure-netapp-files/troubleshoot-volumes.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation demonstrates moderate Windows bias, primarily through the use of Windows-centric tools and terminology (Active Directory, Kerberos, LDAP, SMB) and by providing PowerShell commands for administrative tasks (e.g., setting Kerberos encryption type) without equivalent Linux commands. Windows/AD concepts are explained first and in greater detail, while Linux-specific troubleshooting (e.g., NFS client configuration, service restarts) is present but less emphasized and sometimes lacks step-by-step guidance.
Recommendations
  • Provide Linux command equivalents for all PowerShell examples (e.g., using 'ldapmodify', 'adcli', or 'realm' for Kerberos/AD tasks).
  • Include troubleshooting steps for Linux/macOS environments where only Windows/AD instructions are given (e.g., how to set Kerberos encryption types or manage machine accounts from Linux).
  • Balance explanations of AD/SMB errors with NFS/Linux-specific error scenarios and resolutions.
  • Where Windows tools or terminology are used, add notes or links to Linux/macOS alternatives.
  • Ensure examples and error messages include both Windows and Linux contexts where relevant.
GitHub Create Pull Request
Azure Netapp Files Understand data encryption in Azure NetApp Files ...icles/azure-netapp-files/understand-data-encryption.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias, especially in sections discussing SMB encryption, UNC hardening, and LDAP signing. Windows tools and concepts (SMB, UNC, Active Directory, Group Policy) are described in detail, often before or instead of Linux equivalents. LDAP signing and channel binding are discussed primarily in the context of Windows Active Directory, with configuration examples and links focused on Windows Server. There is little to no mention of Linux or macOS client configuration for SMB encryption, LDAP signing, or NFS Kerberos setup, and no Linux-specific tools or commands are referenced.
Recommendations
  • Add Linux/macOS examples for configuring SMB encryption, such as using mount options or Samba client settings.
  • Include instructions or references for configuring NFS Kerberos on Linux clients, including common distributions and tools (e.g., krb5.conf, nfs-utils).
  • Provide parity in LDAP signing and StartTLS configuration by referencing Linux LDAP clients (e.g., OpenLDAP) and their configuration files.
  • Balance the order of presentation so that Linux and Windows approaches are given equal prominence, or at least mention Linux/macOS alternatives alongside Windows tools.
  • Link to documentation for Linux/macOS equivalents where possible (e.g., Samba, OpenLDAP, MIT Kerberos).
GitHub Create Pull Request
Azure Netapp Files Understand guidelines for Active Directory Domain Services site design and planning ...rstand-guidelines-active-directory-domain-service-site.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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-centric tools and patterns (e.g., Active Directory Sites and Services utility, time.windows.com, Windows Server AD concepts) and providing configuration steps and screenshots only for Windows environments. Linux client support is mentioned but not illustrated with equivalent Linux tooling or examples. There are no Linux/macOS-specific instructions for AD DS site configuration, nor are cross-platform alternatives for key tasks (such as subnet assignment or domain controller management) provided.
Recommendations
  • Include Linux/macOS-specific instructions or examples for AD DS integration, such as using Samba or realmd for domain join and site configuration.
  • Provide equivalent Linux command-line examples (e.g., using 'dig' or 'host' for DNS SRV record validation instead of only 'nslookup').
  • Reference cross-platform tools and methods for time synchronization (e.g., ntpd, chrony) and clarify how to ensure time parity with Azure NetApp Files.
  • Add screenshots or walkthroughs for Linux-based AD DS management where possible, or at least describe how Linux admins can perform analogous tasks.
  • Explicitly state any limitations or requirements for Linux/macOS clients in the context of AD DS site design and planning.
GitHub Create Pull Request
Azure Netapp Files Understand volume languages in Azure NetApp Files ...cles/azure-netapp-files/understand-volume-languages.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page displays a moderate Windows bias. Windows tools (Explorer, PowerShell, Notepad, Notepad++) are frequently mentioned first or exclusively in sections about file encoding and font support. PowerShell examples are provided for file encoding conversion, while Linux equivalents (iconv, file) are mentioned later or less prominently. Windows-specific troubleshooting (fonts, region settings, chcp) is detailed, but similar Linux troubleshooting is not. Some sections (e.g., font troubleshooting, encoding conversion) lack Linux command examples or focus on Windows tools before Linux alternatives.
Recommendations
  • Provide Linux command-line examples (e.g., using iconv, file, locale, and font configuration) alongside or before Windows/PowerShell examples.
  • Include troubleshooting steps for Linux clients (e.g., changing terminal fonts, locale settings, handling encoding errors) similar to the Windows font/region advice.
  • Mention Linux GUI tools for encoding and font management (e.g., Gedit, Kate, GNOME Terminal settings) where Windows GUI tools are referenced.
  • Ensure parity in example order: present Linux and Windows examples side-by-side, or alternate which platform is shown first.
  • Add explicit guidance for macOS clients where relevant, especially in encoding and font sections.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-configure-nfsv41-domain.md ...pp-files/azure-netapp-files-configure-nfsv41-domain.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by presenting Azure PowerShell commands as the primary method for registering and checking the NFSv4.1 ID domain feature, with Azure CLI (which is more cross-platform and Linux-friendly) only mentioned secondarily in a note. The main configuration and troubleshooting examples are Linux-focused, but the initial management steps are Windows-centric.
Recommendations
  • Provide Azure CLI examples alongside or before Azure PowerShell commands for feature registration and status checking.
  • Explicitly state that all management steps can be performed from Linux or macOS using Azure CLI, and provide corresponding commands.
  • Where possible, use neutral language (e.g., 'using Azure CLI or PowerShell') and avoid defaulting to Windows tooling.
  • Consider including a table or section comparing PowerShell and CLI commands for common tasks to help users on different platforms.
  • Review other sections for similar patterns and ensure Linux-first or parity in all procedural steps.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/application-volume-group-considerations.md ...etapp-files/application-volume-group-considerations.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through the use of Windows-centric links and examples. For instance, the reference to 'Create a PPG using the Azure portal' links specifically to the Windows VM documentation, with no mention of Linux VM equivalents or examples. There are no Linux-specific instructions, examples, or references, despite SAP HANA commonly running on Linux. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users.
Recommendations
  • Add explicit references and links to Linux VM documentation, such as 'Create a PPG using the Azure portal for Linux VMs'.
  • Include Linux-specific examples and instructions wherever VM or resource creation is discussed.
  • Ensure that all procedural steps (e.g., VM pinning, proximity placement group creation) are covered for both Windows and Linux environments.
  • Review all cross-references and ensure Linux parity in linked articles and guides.
  • Consider a dedicated section or callouts for Linux users, especially in SAP HANA contexts where Linux is the primary OS.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azacsnap-cmd-ref-details.md ...rticles/azure-netapp-files/azacsnap-cmd-ref-details.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides command-line examples for the Azure Application Consistent Snapshot tool but does not specify or show any Linux-specific usage, shell, or output. There is no mention of Linux environments, and all examples are generic or reference Azure Large Instance (which is typically Windows-based), with no explicit Linux context or parity. The documentation does not clarify whether the tool or commands are cross-platform, nor does it provide Linux-specific guidance or troubleshooting.
Recommendations
  • Explicitly state whether the azacsnap tool and commands are supported on Linux, and if so, provide at least one example run on a Linux system (e.g., Ubuntu, RHEL).
  • Include Linux shell (bash) output examples, especially if there are differences in output or behavior compared to Windows/Azure Large Instance.
  • Mention any Linux-specific prerequisites, environment variables, or configuration file locations if applicable.
  • Clarify in the introduction or a compatibility section which platforms are supported and highlight any differences in usage or output.
  • If the tool is not supported on Linux, explicitly state this to avoid confusion.
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
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parity between Azure Portal, PowerShell, Azure CLI, ARM Template, and Terraform for all major steps. However, there is a subtle Windows bias: PowerShell examples are given their own dedicated sections, and PowerShell is mentioned before Azure CLI in several places. There is no explicit mention of Linux-specific shell usage (e.g., Bash), nor are there any Linux-specific command-line patterns or troubleshooting notes. The CLI examples are generic and could be run from Bash, but this is not clarified. The documentation also refers to 'PowerShell Cloud Shell' but does not mention Bash Cloud Shell, which is available and commonly used by Linux users.
Recommendations
  • Explicitly mention that Azure CLI commands can be run from Bash (Linux/macOS) or Windows Command Prompt/PowerShell.
  • Add examples or notes for Bash Cloud Shell usage where PowerShell Cloud Shell is referenced.
  • Ensure that Azure CLI is mentioned before or alongside PowerShell in introductory sentences to avoid Windows-first ordering.
  • Consider adding troubleshooting notes or tips relevant to Linux environments (e.g., file permissions, environment variables).
  • Where variables are defined for CLI, show both Bash and PowerShell syntax if relevant.
  • Clarify that all command-line steps are cross-platform unless a step is Windows-specific.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-application-volume-oracle-azure-resource-manager.md ...igure-application-volume-oracle-azure-resource-manager.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes deployment using the Azure Portal GUI, which is most commonly accessed from Windows environments and is illustrated with Windows-style screenshots. There are no examples or instructions for deploying via CLI tools such as Azure CLI, Bash, or PowerShell, nor is there any mention of Linux-specific workflows or tools. This may disadvantage Linux users who prefer or require command-line automation.
Recommendations
  • Add step-by-step instructions for deploying the ARM template using Azure CLI (az deployment group create) with Bash examples.
  • Include PowerShell examples if relevant, but ensure Linux/Bash parity by presenting Bash or cross-platform CLI examples first.
  • Mention that the Azure Portal is accessible from any OS, and clarify that the instructions are not Windows-specific.
  • Provide sample commands for validating and deploying the template from Linux/macOS terminals.
  • Link to documentation on using ARM templates with Azure CLI and Bash for Linux users.
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
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation shows a bias toward Windows by providing Azure PowerShell commands as the primary example for feature registration, with Azure CLI only mentioned secondarily and without explicit command examples. There are no Linux-specific CLI examples for feature registration, and the initial registration steps are presented with PowerShell syntax. However, the main NFS conversion workflow and client-side examples are Linux-focused, using Linux commands and mount options.
Recommendations
  • Provide explicit Azure CLI examples (with full command syntax) for feature registration and status checking alongside PowerShell examples.
  • List Azure CLI commands before or alongside PowerShell commands to avoid the impression of Windows-first bias.
  • Clarify that all client-side steps and examples are Linux-based, and add a note if Windows NFS clients are not supported or relevant.
  • Where possible, include Bash or shell script equivalents for any automation steps currently shown only in PowerShell.
  • Ensure parity in all command-line examples by always showing both PowerShell and CLI (and/or Bash) alternatives.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/cross-region-replication-delete.md .../azure-netapp-files/cross-region-replication-delete.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides instructions primarily through GUI interactions (e.g., right-clicking, selecting menu items) that are typical of Windows environments, without mentioning CLI or Linux-native methods. There are no examples using Linux tools, shell commands, or cross-platform Azure CLI/PowerShell alternatives. The screenshots and terminology (right-click, select, etc.) suggest a Windows-centric approach, and Linux users may not find guidance for their workflows.
Recommendations
  • Add equivalent instructions using Azure CLI and/or REST API, which are cross-platform and commonly used on Linux.
  • Include examples for deleting replications and volumes using shell commands (bash), and clarify any differences in workflow for Linux users.
  • Explicitly mention that the GUI steps can be performed from any OS via the Azure Portal, or provide OS-agnostic language.
  • Where screenshots are used, note that the interface is accessible from any browser, regardless of OS.
  • Consider adding a section titled 'Command-line steps (Linux/Mac/Windows)' to ensure parity and inclusivity.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-integration.md ...ob/main/articles/azure-netapp-files/faq-integration.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation tends to mention Windows examples and use cases before Linux equivalents. For instance, in the section about mounting Azure NetApp Files volumes, Windows VMs are mentioned first for both NFS and SMB, and only Windows VMs are mentioned for SMB. There are no explicit Linux command examples or detailed Linux instructions, which may leave Linux users with less guidance.
Recommendations
  • Ensure that Linux examples and use cases are mentioned alongside or before Windows examples, especially for common operations like mounting NFS or SMB shares.
  • Provide explicit instructions or references for mounting Azure NetApp Files SMB shares on Linux VMs, if supported, or clarify if it is not supported.
  • Include command-line examples for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., mount commands) where relevant.
  • Review the order of OS mentions to avoid consistently prioritizing Windows over Linux.
  • Add links to Linux-specific documentation or troubleshooting guides where appropriate.
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
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation displays a Windows bias by providing detailed quota target formats for SMB (Windows) and dual-protocol volumes using SMB, while only briefly mentioning NFS (Linux/Unix) without example formats or further explanation. The SMB (Windows) format is described in detail and appears before the NFS (Linux) format in dual-protocol guidance. There are no Linux-specific command-line or tool examples, and the documentation does not reference Linux administration patterns or tools.
Recommendations
  • Provide example quota target formats for NFS (Linux/Unix) users, including typical UID/GID values and how to obtain them on Linux systems.
  • Include Linux command-line examples (e.g., using 'id', 'getent', or other relevant tools) for determining user/group IDs for quota assignment.
  • Balance the order of protocol descriptions so that NFS (Linux/Unix) and SMB (Windows) are presented with equal prominence and detail.
  • Reference Linux administration tools or patterns where appropriate, especially in sections discussing quota management for NFS volumes.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/object-rest-api-onelake.md ...articles/azure-netapp-files/object-rest-api-onelake.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references the 'on-premises data gateway', which is primarily a Windows-only tool, without mentioning Linux alternatives or providing guidance for Linux users. There are no examples or instructions for Linux environments, and the documentation implicitly assumes a Windows setup.
Recommendations
  • Explicitly state the platform requirements for the on-premises data gateway, including its lack of Linux support.
  • If possible, provide or reference alternative solutions for Linux environments, such as Azure Data Factory Integration Runtime (if supported) or containerized gateway options.
  • Add a note for Linux users about current limitations and any workarounds or roadmap for Linux support.
  • Ensure future documentation includes parity for Linux users, with examples and instructions relevant to both Windows and Linux platforms.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/reestablish-deleted-volume-relationships.md ...tapp-files/reestablish-deleted-volume-relationships.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation primarily provides Azure PowerShell examples for feature registration, with PowerShell commands shown first and in detail. Azure CLI (which is cross-platform and preferred on Linux) is only mentioned briefly in text, with no explicit command examples. There are no Linux-specific instructions or screenshots, and the workflow assumes familiarity with Windows-centric tools.
Recommendations
  • Provide explicit Azure CLI command examples (e.g., 'az feature register ...') alongside PowerShell, not just as a mention.
  • List Azure CLI examples before or alongside PowerShell to avoid Windows-first bias.
  • Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Include notes or sections for Linux/macOS users, especially for command-line operations.
  • Ensure screenshots and UI instructions are platform-neutral or clarify any platform-specific differences.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/restore-single-file-backup.md ...icles/azure-netapp-files/restore-single-file-backup.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation demonstrates a Windows bias by providing Azure PowerShell commands first and in detail for feature registration, with Azure CLI (which is more cross-platform and Linux-friendly) only mentioned briefly in text and without explicit command examples. No Linux-specific tools or shell examples are provided.
Recommendations
  • Provide explicit Azure CLI command examples alongside PowerShell examples for all steps, not just a mention.
  • Consider including Bash or shell script equivalents where applicable, especially for registration steps.
  • Ensure that cross-platform (Linux/macOS) users are addressed equally in all command-line instructions.
  • If screenshots or UI elements are OS-specific, clarify their applicability or provide Linux/macOS equivalents.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/snapshots-restore-file-client.md ...es/azure-netapp-files/snapshots-restore-file-client.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows client instructions for restoring files from Azure NetApp Files snapshots. However, the Windows section includes additional GUI-based restore options (such as Previous Versions tab) and multiple screenshots, while the Linux section is limited to basic command-line usage. Windows-specific tools and patterns (GUI, Previous Versions) are highlighted, and the Windows section is more visually detailed.
Recommendations
  • Expand the Linux section to include alternative restore methods, such as using file managers (e.g., Nautilus, Dolphin) to access .snapshot directories via GUI, if supported.
  • Add screenshots for the Linux workflow to match the visual detail of the Windows section.
  • Mention Linux desktop environments and how hidden directories can be revealed, similar to the Windows 'show hidden items' step.
  • If available, describe integration with Linux backup/restore tools or file versioning features.
  • Ensure parity in the depth of explanation and visual aids between Linux and Windows instructions.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/solutions-benefits-azure-netapp-files-sql-server.md ...es/solutions-benefits-azure-netapp-files-sql-server.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively discusses SQL Server deployment scenarios, cost analysis, and performance metrics using Azure NetApp Files, but all examples, benchmarks, and tooling references are centered on SQL Server—a Windows-centric database. There are no references to Linux-based SQL Server deployments, nor examples or comparisons involving Linux tools, commands, or environments. The documentation implicitly assumes Windows as the platform, omitting Linux parity in both technical details and practical guidance.
Recommendations
  • Include explicit guidance and examples for deploying SQL Server on Linux with Azure NetApp Files.
  • Reference Linux-compatible benchmarking tools (e.g., sysbench, fio) alongside SSB and perfmon.
  • Discuss any differences or considerations for SQL Server on Linux (e.g., supported distributions, configuration steps, performance characteristics).
  • Add links to documentation for creating NFS volumes in Azure NetApp Files, not just SMB.
  • Where VM instance types are discussed, clarify that both Windows and Linux VMs are supported and note any differences.
  • Provide cost and performance comparisons for SQL Server on Linux VMs versus Windows VMs using Azure NetApp Files.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/test-disaster-recovery.md .../articles/azure-netapp-files/test-disaster-recovery.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references the 'Azure Application Consistent Snapshot tool' (AzAcSnap), which is primarily a Windows-based tool, without mentioning Linux alternatives or providing Linux-specific guidance. There are no explicit examples or instructions for Linux environments, such as using native Linux snapshot tools or mounting NFS volumes on Linux VMs. The steps and tooling implicitly assume a Windows-centric workflow.
Recommendations
  • Include information about creating application-consistent snapshots on Linux, such as using pre/post scripts with AzAcSnap (if supported) or alternative Linux-native tools.
  • Provide explicit instructions or examples for mounting/unmounting Azure NetApp Files volumes on Linux VMs (e.g., using mount commands for NFS/CIFS).
  • Mention and link to documentation for Linux-based disaster recovery testing workflows, ensuring parity with Windows guidance.
  • Clarify if AzAcSnap supports Linux, and if not, suggest equivalent Linux solutions or workarounds.
  • Ensure that both Windows and Linux environments are addressed equally in all steps, especially where OS-specific actions are required.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/volume-delete.md ...blob/main/articles/azure-netapp-files/volume-delete.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides only Azure Portal (GUI) instructions and omits any command-line examples. While it mentions unmounting the volume and removing it from automounter configurations (which are Linux-relevant), it does not provide explicit Linux (e.g., Bash/CLI) or Windows (e.g., PowerShell) command examples. However, the lack of CLI examples, especially for Linux users, and the use of GUI-centric steps (which are more familiar to Windows users) indicate a subtle Windows-first and missing Linux example bias.
Recommendations
  • Add Azure CLI and/or Azure PowerShell examples for deleting a volume, with both Linux (Bash) and Windows (PowerShell) command syntax.
  • Include explicit Linux commands for unmounting (e.g., `umount /mount/point`) and updating `fstab`.
  • Provide parity in instructions by showing both GUI and command-line methods, and ensure Linux and Windows users are equally supported.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/volume-hard-quota-guidelines.md ...les/azure-netapp-files/volume-hard-quota-guidelines.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a Windows bias in several ways. In the VM-level monitoring section, Windows examples (Explorer, dir command) are presented before Linux (df command), and with more screenshots and detailed steps. In the CLI/PowerShell section, PowerShell screenshots are used exclusively for command examples, even though Azure CLI is cross-platform and commonly used on Linux. There is no demonstration of Linux shell usage for Azure CLI commands, nor are there Bash examples or screenshots. The documentation also references Windows tools (Explorer, PowerShell) more prominently than Linux equivalents.
Recommendations
  • Present Linux examples alongside Windows examples, not after them, and with equal detail and screenshots.
  • Include Azure CLI command examples and screenshots from a Linux shell (e.g., Bash), not just PowerShell.
  • Add instructions for using Azure CLI on Linux, including installation and usage in native Linux environments.
  • When describing monitoring or management steps, alternate the order of Windows and Linux instructions, or present them in parallel.
  • Ensure parity in troubleshooting and FAQ sections by including Linux-specific guidance where relevant.
GitHub Create Pull Request
Azure Netapp Files Install the Azure Application Consistent Snapshot tool for Azure NetApp Files ...n/articles/azure-netapp-files/azacsnap-installation.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Linux and Windows instructions, but Windows examples and terminology (such as GUI-based steps, use of 'where' and 'copy' commands, and references to Windows environment variables) are often presented first or with more detail. Windows-specific tools and patterns (like GUI user creation, use of .exe, and %PATH%) are mentioned explicitly, while Linux equivalents are present but sometimes less detailed. There is a slight tendency to favor Windows in order and terminology, though Linux instructions are generally present.
Recommendations
  • Ensure Linux and Windows instructions are presented with equal detail and clarity.
  • Alternate the order of Linux and Windows examples to avoid implicit prioritization.
  • Provide command-line examples for Windows (e.g., using PowerShell or CMD) alongside GUI instructions.
  • Explicitly mention macOS compatibility or limitations if relevant.
  • Where possible, use cross-platform terminology (e.g., 'terminal session' instead of 'GUI' for Windows).
  • Add troubleshooting steps or notes for Linux-specific issues, such as permissions and library paths.
GitHub Create Pull Request
Azure Netapp Files Quickstart: Set up Azure NetApp Files and NFS volume ...-netapp-files-quickstart-set-up-account-create-volumes.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parity across Azure Portal, PowerShell, Azure CLI, ARM Template, and Terraform, but consistently lists PowerShell (a Windows-centric tool) before Azure CLI in each section. PowerShell examples are detailed and prominent, which may subtly signal a Windows-first approach. However, Azure CLI examples are present and equally functional, and there are no Windows-only tools or missing Linux/macOS instructions.
Recommendations
  • Alternate the order of PowerShell and Azure CLI tabs, or list Azure CLI first to better reflect cross-platform usage.
  • Explicitly mention that both PowerShell and Azure CLI are available in Azure Cloud Shell, which runs on Linux and is accessible from any OS.
  • Add a note clarifying that all CLI commands work on Linux/macOS as well as Windows.
  • Where possible, highlight cross-platform usage and avoid implying PowerShell is the default or preferred method.
GitHub Create Pull Request
Azure Netapp Files Mount NFS volumes for virtual machines ...etapp-files-mount-unmount-volumes-for-virtual-machines.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Linux and Windows instructions for mounting NFS volumes, but there is a slight Windows bias. Windows-specific tools (the 'Mount' command) are referenced, and the Windows section includes explicit instructions and links to Windows command-line utilities. The Linux section is more detailed and comes first, but Windows tools and patterns are mentioned exclusively in the Windows section, and the Windows mounting process relies on first mounting the volume on Linux to set permissions. There is also a reference to PowerShell/Windows command-line utilities without equivalent Linux command references in the Windows section.
Recommendations
  • Provide equivalent Linux command references when mentioning Windows tools (e.g., clarify Linux alternatives to the Windows 'Mount' command).
  • Include more parity in troubleshooting and advanced options for both platforms.
  • Clarify that the Windows mounting process depends on Linux for permission setting, and suggest alternatives if possible.
  • Add explicit Linux command-line references in the Windows section for comparison.
  • Consider mentioning cross-platform tools or approaches where relevant.
GitHub Create Pull Request
← Previous Page 8 of 10 Next →