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 1-25 of 228 flagged pages
Azure Netapp Files Enable Continuous Availability on existing Azure NetApp Files SMB volumes ...p-files/enable-continuous-availability-existing-SMB.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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 example commands use PowerShell, and the verification step relies exclusively on Windows-specific tools (Get-SmbConnection). The instructions explicitly mention rebooting Windows systems, with no guidance for Linux or macOS clients. There are no examples or instructions for verifying SMB Continuous Availability from non-Windows platforms, nor are Linux/macOS tools or patterns mentioned.
Recommendations
  • Add instructions for verifying SMB Continuous Availability from Linux and macOS clients, using appropriate tools (e.g., smbstatus, mount options, or relevant CLI commands).
  • Clarify whether rebooting is required for non-Windows clients, and provide platform-specific guidance.
  • Include Linux/macOS examples alongside PowerShell, or at least mention equivalent steps for those platforms.
  • Reference cross-platform SMB client documentation where applicable.
GitHub Create Pull Request
Azure Netapp Files azure-netapp-files-create-volumes-smb.md ...e-netapp-files/includes/smb-continuous-availability.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by focusing exclusively on Windows workloads and tools. All supported workloads (Citrix App Layering, FSLogix, MSIX app attach, SQL Server) are Windows-centric, and explicit statements indicate that Linux SQL Server is not supported. There are no Linux/macOS examples, alternatives, or guidance, and Active Directory (a Windows technology) is referenced without mention of Linux equivalents.
Recommendations
  • Clearly state the lack of Linux/macOS support at the beginning of the documentation.
  • Provide guidance or links for Linux users, such as alternative solutions or roadmap information.
  • If possible, include parity information or future plans for Linux support.
  • Add a comparison table showing supported platforms and workloads.
  • Mention any relevant Linux technologies (e.g., Samba, LDAP) and clarify their compatibility or lack thereof.
GitHub Create Pull Request
Azure Netapp Files Manage SMB share ACLs in Azure NetApp Files ...-netapp-files/manage-smb-share-access-control-lists.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively describes Windows-based methods (Windows Explorer, Microsoft Management Console) for viewing and modifying SMB share ACLs in Azure NetApp Files. No Linux or macOS tools, workflows, or examples are provided, and all screenshots and instructions are Windows-specific.
Recommendations
  • Add instructions for managing SMB share ACLs from Linux and macOS clients, if supported (e.g., using smbclient, setfacl, or other relevant tools).
  • Clarify whether share-level ACL modification is possible from non-Windows platforms, and if not, explicitly state this limitation.
  • Provide parity in examples and screenshots for Linux/macOS environments where feasible.
  • Include a section outlining any CLI or API-based management options that are platform-agnostic.
GitHub Create Pull Request
Azure Netapp Files Mount SMB volumes for Windows VMs ...n/articles/azure-netapp-files/mount-volumes-vms-smb.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively covers mounting SMB volumes for Windows virtual machines, providing instructions only for Windows clients. There are no examples, instructions, or references for mounting SMB volumes on Linux or macOS clients, and the focus is solely on Windows tools and workflows.
Recommendations
  • Add a section detailing how to mount SMB volumes on Linux and macOS clients, including example commands (e.g., using 'mount -t cifs' or 'smbclient').
  • Provide parity in screenshots and step-by-step instructions for non-Windows platforms.
  • Clarify in the introduction that the guide is Windows-specific, or broaden the scope to include other operating systems.
  • Link directly to Linux/macOS SMB mounting documentation in the 'Next steps' section.
GitHub Create Pull Request
Azure Netapp Files Use DFS-N and DFS Root Consolidation with Azure NetApp Files ...s-n-and-dfs-root-consolidation-with-azure-netapp-files.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily Windows-centric, focusing exclusively on Windows Server, PowerShell, and Windows GUI tools for all configuration steps. There are no Linux/macOS examples, nor any mention of cross-platform alternatives or considerations. All instructions, requirements, and tooling are Windows-only, and the DFS-N technology itself is described as a Windows Server role, with no guidance for non-Windows environments.
Recommendations
  • Clearly state DFS-N is a Windows-only technology at the top of the documentation.
  • Provide guidance for Linux/macOS users on alternative approaches for namespace virtualization or SMB share migration, such as using autofs, symlinks, or third-party tools.
  • Include a comparison table or section outlining what Linux/macOS users can and cannot do with Azure NetApp Files in relation to DFS-N.
  • Reference NFS and dual-protocol scenarios more explicitly, and clarify what options exist for non-Windows clients.
  • If possible, add links to documentation for Linux-based SMB clients and how they interact with DFS-N namespaces.
GitHub Create Pull Request
Azure Netapp Files Configure AD DS LDAP over TLS for Azure NetApp Files ...articles/azure-netapp-files/configure-ldap-over-tls.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows Server tools (Certification Authority, MMC snap-in) for certificate generation and export, without mentioning or providing equivalent Linux methods. All certificate management steps are described using Windows interfaces and screenshots, with no guidance for Linux/macOS users. Windows terminology and tools are presented first and exclusively.
Recommendations
  • Add instructions for generating and exporting root CA certificates using Linux tools (e.g., OpenSSL) and macOS equivalents.
  • Include command-line examples for certificate management on Linux/macOS.
  • Provide screenshots or step-by-step guides for Linux certificate management workflows.
  • Explicitly state that both Windows and Linux/macOS can be used, and clarify any platform-specific requirements.
GitHub Create Pull Request
Azure Netapp Files Enable Active Directory Domain Services (AD DS) LDAP authentication for NFS volumes ...s/azure-netapp-files/configure-ldap-extended-groups.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits 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 attribute management and configuration, with no equivalent Linux/OpenLDAP instructions or screenshots. Linux is mentioned only in the context of NFS clients, and OpenLDAP or other third-party LDAP servers are explicitly not supported. Windows tools and patterns are presented first and exclusively for critical configuration steps.
Recommendations
  • Add guidance or notes for Linux-based LDAP servers, even if only to clarify limitations or suggest alternatives.
  • Provide equivalent instructions for managing POSIX attributes using Linux tools (e.g., ldapmodify, phpldapadmin) where possible.
  • Include Linux/OpenLDAP screenshots or command-line examples for attribute management, alongside Windows MMC examples.
  • Clarify early in the document that only Windows-based LDAP servers are supported, and offer links or references for Linux users seeking similar functionality.
  • Consider adding a comparison table of supported and unsupported LDAP server types, with rationale.
GitHub Create Pull Request
Azure Netapp Files Enable Continuous Availability on existing Azure NetApp Files SMB volumes ...p-files/enable-continuous-availability-existing-SMB.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows environments. All verification steps use PowerShell commands, and only Windows systems are mentioned for rebooting and connecting to SMB shares. There are no instructions or examples for Linux or macOS clients, nor are equivalent Linux tools (such as smbclient or mount.cifs) referenced.
Recommendations
  • Add instructions for verifying SMB Continuous Availability from Linux and macOS clients, using tools like smbclient or mount.cifs.
  • Clarify whether Linux/macOS clients require any action (such as remounting) after enabling CA.
  • Provide command-line examples for Linux (e.g., using smbstatus, smbclient, or checking mount options) to verify CA status.
  • Mention any platform-specific limitations or considerations for non-Windows clients.
GitHub Create Pull Request
Azure Netapp Files azure-netapp-files-create-volumes-smb.md ...e-netapp-files/includes/smb-continuous-availability.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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 focusing exclusively on Windows-centric workloads (Citrix, FSLogix, MSIX app attach, SQL Server on Windows) and explicitly stating that Linux SQL Server is not supported. There are no Linux/macOS examples, tools, or guidance provided. Windows-specific concepts (Active Directory, domain accounts, SeSecurityPrivilege) are mentioned without Linux equivalents.
Recommendations
  • Clearly state the lack of Linux/macOS support at the top of the page to set expectations.
  • If possible, provide information about future Linux support or alternatives for Linux users.
  • Add a section listing supported and unsupported platforms explicitly.
  • Where Windows-specific tools or privileges are mentioned, note that these are not applicable to Linux and suggest alternative approaches if any exist.
  • If Linux support is planned, include a roadmap or guidance for Linux users.
GitHub Create Pull Request
Azure Netapp Files Use DFS-N and DFS Root Consolidation with Azure NetApp Files ...s-n-and-dfs-root-consolidation-with-azure-netapp-files.md
High 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 is heavily Windows-centric, focusing exclusively on Windows Server DFS Namespaces, Windows AD, Windows DNS, and PowerShell/GUI instructions. There are no Linux/macOS equivalents, examples, or guidance. All tooling and patterns assume a Windows environment, and Linux users are not addressed at all.
Recommendations
  • Explicitly state that DFS Namespaces is a Windows-only technology and clarify Linux/macOS limitations.
  • Provide alternative approaches for Linux/macOS environments, such as mentioning NFS referrals, autofs, or other cross-platform namespace/migration strategies.
  • Add a section comparing DFS-N to Linux-native solutions, or link to relevant documentation for Linux users.
  • Where possible, suggest how Linux clients can interact with DFS-N namespaces (e.g., via SMB mounts), and note any caveats.
  • If Azure NetApp Files supports NFS or dual-protocol, include migration/consolidation examples for NFS shares and Linux tools.
GitHub Create Pull Request
Azure Netapp Files Understand SMB file permissions in Azure NetApp Files ...-netapp-files/network-attached-file-permissions-smb.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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's Windows documentation for access control, without mentioning Linux file permission models (such as POSIX ACLs) or providing any Linux-specific examples or tools. The terminology and linked resources are Windows-centric, and there is no guidance for users managing SMB permissions from Linux clients.
Recommendations
  • Include a section comparing NTFS ACLs with POSIX ACLs to help Linux administrators understand differences and interoperability.
  • Provide examples of managing SMB permissions from Linux clients, such as using the 'smbcacls' tool or 'setfacl' where applicable.
  • Reference Linux documentation or resources for SMB and file permissions, in addition to Microsoft/Windows links.
  • Clarify whether and how Linux clients can view or modify NTFS ACLs on Azure NetApp Files SMB volumes.
  • Add troubleshooting tips for Linux users accessing SMB shares with NTFS ACLs.
GitHub Create Pull Request
Azure Netapp Files Understand NAS file permissions in Azure NetApp Files ...zure-netapp-files/network-attached-file-permissions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page presents Windows/SMB permission management patterns and tools (such as the 'advanced permission view' and a screenshot of a Windows interface) before Linux/NFS equivalents. It describes Windows inheritance mechanisms in detail, including UI elements, while Linux/NFS methods are mentioned briefly and without examples or screenshots. There are no Linux command-line examples (e.g., setfacl, chmod, chown) or screenshots of Linux tools, resulting in a lack of parity for Linux administrators.
Recommendations
  • Provide Linux/NFS command-line examples for managing permissions and inheritance (e.g., setfacl, chmod, chown, umask, setgid).
  • Include screenshots or step-by-step instructions for Linux/NFS permission management, similar to the Windows example.
  • Present Windows and Linux/NFS methods in parallel, giving equal detail and prominence to both.
  • Clarify differences and similarities in permission inheritance mechanisms between SMB (Windows) and NFS (Linux), with practical guidance for each.
GitHub Create Pull Request
Azure Netapp Files Access an Azure NetApp Files object REST API-enabled volume with S3-compatible clients ...articles/azure-netapp-files/object-rest-api-browser.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates Windows bias by prioritizing Windows-specific instructions and tools. The certificate installation steps are written for Windows, referencing the Edge browser and Windows certificate store, with no Linux or macOS equivalent provided. S3 Browser, a Windows-only tool, is featured exclusively. While AWS CLI installation is covered for both Windows and Linux, the overall flow and examples favor Windows environments.
Recommendations
  • Add explicit instructions for installing certificates on Linux (e.g., using OpenSSL and updating system trust stores) and macOS.
  • Include examples using Linux-native S3 clients (e.g., s3cmd, rclone, or MinIO client) alongside S3 Browser.
  • Present installation and usage steps for both Windows and Linux/macOS in parallel, rather than Windows-first.
  • Clarify cross-platform compatibility for all steps and tools mentioned.
  • Consider adding screenshots or terminal commands for Linux/macOS workflows where appropriate.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
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-centric tools (such as Active Directory Sites and Services), providing step-by-step instructions and screenshots for Windows GUI utilities, and prioritizing Windows authentication scenarios. Linux client support is mentioned only briefly, with no equivalent configuration examples or tooling guidance. There are no Linux-specific instructions, screenshots, or parity for site topology management, and all sample workflows use Windows tools.
Recommendations
  • Add Linux-focused examples for AD DS integration, including configuration steps for Kerberos authentication and LDAP client setup on Linux systems.
  • Provide CLI-based instructions (e.g., using samba-tool, ldapsearch, or realm commands) for managing AD DS site topology and verifying domain controller assignments from Linux environments.
  • Include screenshots or terminal output from Linux tools where appropriate, alongside Windows GUI screenshots.
  • Explicitly mention cross-platform considerations and clarify which steps are OS-agnostic versus Windows-specific.
  • Ensure that troubleshooting and validation steps (such as checking DNS SRV records) include Linux command-line equivalents (e.g., dig, host, nslookup on Linux).
GitHub Create Pull Request
Azure Netapp Files Azure NetApp Files tools ...ob/main/articles/azure-netapp-files/tools-reference.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page lists several tools for Azure NetApp Files, but only provides a specific example of automation and reporting using PowerShell (ANFHealthCheck), which is Windows-centric. There are no equivalent Linux/bash examples or mentions of Linux-native automation/reporting tools. The use of PowerShell as the sole scripting example suggests a bias towards Windows environments, and Linux users may not find guidance for their preferred platforms.
Recommendations
  • Add examples or references for Linux/bash-based automation and reporting tools for Azure NetApp Files.
  • Provide cross-platform scripts or indicate if tools like ANFHealthCheck can be run with PowerShell Core on Linux/macOS.
  • Include guidance or links for using Azure CLI, shell scripts, or other Linux-friendly tools for monitoring and managing Azure NetApp Files.
  • Ensure that future documentation lists both Windows and Linux options for automation and monitoring, or explicitly states platform compatibility.
GitHub Create Pull Request
Azure Netapp Files Understand volume languages in Azure NetApp Files ...cles/azure-netapp-files/understand-volume-languages.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools (Explorer, PowerShell, CMD, Notepad, Notepad++) are mentioned and illustrated first or exclusively in several sections, especially in SMB and file encoding conversion scenarios. PowerShell examples and screenshots are prevalent, while equivalent Linux command-line examples (e.g., using 'file', 'iconv', 'cat') are less frequent and often appear later in the text. Windows-specific troubleshooting and configuration (fonts, region settings, code pages) are described in detail, whereas Linux alternatives (e.g., changing locale, font support in terminals) are not covered with the same depth. Some conversion and encoding operations are shown only with PowerShell, with Linux alternatives mentioned briefly or not at all.
Recommendations
  • Provide Linux command-line examples (e.g., using 'iconv', 'file', 'cat', 'locale', 'ls', 'stat') alongside or before Windows/PowerShell examples in all relevant sections.
  • Include troubleshooting steps for Linux clients (e.g., handling fonts, locale settings, encoding issues in common terminals like GNOME Terminal, xterm, etc.), similar to the depth given for Windows.
  • Mention and illustrate Linux-native tools for file encoding conversion and inspection (e.g., 'vim', 'nano', 'file', 'iconv') with screenshots or command output.
  • Balance the order of presentation so that Linux and Windows examples are given equal prominence, or alternate which platform is described first in each section.
  • Expand on Linux-specific behaviors and limitations (e.g., how different distributions or desktop environments handle Unicode, encoding, and font rendering).
  • Add notes or tips for Linux users regarding common pitfalls (e.g., locale misconfiguration, font package installation for CJK/emoji support).
GitHub Create Pull Request
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides detailed, step-by-step instructions for running the tool with administrator privileges on Windows, including launching elevated CMD, PowerShell, and Task Scheduler. These instructions are given before the Linux equivalent, which is only briefly mentioned (using the 'sync' command). The Windows section includes multiple methods and explicit PowerShell code, while the Linux section lacks comparable detail or examples. This demonstrates a 'windows_first' and 'powershell_heavy' bias, as well as a focus on Windows-specific tools.
Recommendations
  • Provide equally detailed instructions for Linux, including step-by-step guidance for running azacsnap with the necessary privileges (e.g., using sudo), and examples for common shells (bash, sh).
  • Include Linux-specific automation examples, such as using cron jobs or systemd timers, similar to the Task Scheduler example for Windows.
  • Ensure that Linux instructions are presented before or alongside Windows instructions, not after them.
  • Add troubleshooting tips for Linux environments (e.g., permissions, log file locations) to match the depth of the Windows section.
  • Where PowerShell or CMD examples are given, provide equivalent bash or shell script examples for Linux users.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azacsnap-cmd-ref-configure.md ...icles/azure-netapp-files/azacsnap-cmd-ref-configure.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. Examples and configuration guidance for Microsoft SQL Server use Windows-specific paths (e.g., C:\MSSQL_BKP\) and connection strings, with no mention of Linux-based SQL Server deployments. There are no explicit Linux shell or tool examples for SQL Server, nor is there guidance for Linux-specific configuration or file paths. The documentation also references Azure Cloud Shell and service principal authentication, but does not clarify parity or differences for Linux environments. Overall, Windows tools and patterns are mentioned exclusively or before Linux equivalents, and Linux-specific usage is missing.
Recommendations
  • Add explicit examples and configuration guidance for SQL Server on Linux, including Linux file paths and connection string formats.
  • Clarify whether AzAcSnap supports SQL Server on Linux and provide instructions for installation and usage in Linux environments.
  • Include Linux shell command examples (e.g., using bash, cat, etc.) for all supported databases, not just SAP HANA.
  • Where file paths or tools are mentioned, provide both Windows and Linux equivalents side-by-side.
  • Review all references to authentication and service principal setup to ensure Linux parity and document any differences.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azacsnap-configure-storage.md ...icles/azure-netapp-files/azacsnap-configure-storage.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns (such as Azure Resource Manager, Azure CLI, and service principal files) without explicitly providing parity for Linux or non-Windows environments. While some commands are shown in Bash (Cloud Shell), there is an implicit assumption of a Windows/Azure-centric workflow, and there are no explicit Linux-native or cross-platform examples for authentication, file permissions, or environment setup. The documentation does not provide PowerShell-specific commands, but it also does not address Linux-specific nuances (e.g., SELinux, systemd, or non-Azure authentication patterns).
Recommendations
  • Add explicit Linux examples for authentication, file permissions, and environment setup, including common Linux distributions.
  • Clarify when instructions are cross-platform and highlight any differences for Linux users (e.g., file paths, permission commands, environment variables).
  • Provide parity for Linux-native tools and workflows, such as using systemd for service management, or alternatives to Azure CLI if applicable.
  • Include troubleshooting tips for common Linux-specific issues (e.g., SELinux/AppArmor, file permission errors, dependency installation).
  • Clearly indicate when instructions are Azure/Windows-specific and offer Linux alternatives where possible.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Linux and Windows instructions for installing and managing AzAcSnap, but there are subtle signs of Windows bias. Windows is often mentioned before Linux in lists and instructions (e.g., in the download section and environment variable setup). Windows-specific tools and terminology (such as GUI-based steps, use of `%PATH%`, and 'Open a terminal session' on Windows) are referenced without always providing equivalent Linux context or tools. Some command examples and explanations are more detailed for Windows, and the structure sometimes assumes a Windows-first perspective. However, Linux instructions are present and generally complete.
Recommendations
  • Ensure Linux and Windows instructions are always presented in parallel, with Linux examples given first or both shown side-by-side.
  • Avoid Windows-first ordering in lists and downloads; alternate or group by platform.
  • Where Windows GUI or tools are mentioned, provide explicit Linux equivalents (e.g., for user creation, path management, and binary location).
  • Clarify when steps are platform-specific and avoid assuming familiarity with Windows tools or patterns.
  • Consider adding more Linux-specific troubleshooting and verification steps, matching the detail given for Windows.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions and command tables, while not mentioning or providing equivalent Linux shell (bash) or cross-platform scripting examples. PowerShell is highlighted as the primary scripting interface, and there is no explicit guidance for Linux users beyond Azure CLI, nor are Linux-native tools or workflows referenced. The order of presentation also places PowerShell (a Windows-centric tool) after Azure CLI but gives it a dedicated, detailed section, reinforcing its prominence.
Recommendations
  • Add explicit bash or Linux shell examples for connecting to Azure Government, especially for common tasks such as authentication and resource management.
  • Include cross-platform scripting guidance, such as using Azure CLI in bash/zsh, and clarify that Azure CLI is available on all major platforms.
  • Mention and provide examples for using REST API tools common on Linux (e.g., curl, httpie) for REST API access.
  • Balance the PowerShell section with equivalent Linux shell or Python scripting examples to ensure parity.
  • Reorder sections or clarify that PowerShell is cross-platform, but also highlight Linux-native approaches where appropriate.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md ...-netapp-files/azure-netapp-files-create-volumes-smb.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. All examples and instructions for managing SMB permissions and shares are given using Windows tools (MMC, Windows Security tab), with no mention of Linux SMB clients or their management tools. The 'non-browsable-share' feature is described only in terms of Windows client behavior and Windows commands. There are no examples or guidance for Linux users on how to mount, access, or manage SMB volumes, nor are Linux tools (such as smbclient, mount.cifs, or Samba utilities) referenced.
Recommendations
  • Add equivalent instructions and screenshots for managing SMB permissions and shares from Linux clients (e.g., using smbclient, setfacl, or mount.cifs).
  • Describe how Linux users can mount and access SMB volumes, including example commands.
  • Clarify which features (such as non-browsable shares, access-based enumeration, and SMB3 encryption) are supported and behave on Linux clients.
  • Reference Linux documentation and tools alongside Windows tools, and avoid presenting Windows instructions exclusively or first.
  • Include troubleshooting steps and best practices for Linux SMB clients.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-sdk-cli.md ...icles/azure-netapp-files/azure-netapp-files-sdk-cli.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation lists both Azure CLI and PowerShell as supported CLI tools, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, despite CLI being cross-platform and PowerShell being historically Windows-focused. No explicit Linux shell (bash) examples or references are provided, and no Linux-specific tools or usage patterns are mentioned. The documentation does not clarify that Azure CLI is the recommended or default tool for Linux users, nor does it provide Linux-oriented guidance or examples.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and the primary tool for Linux users.
  • Provide example commands using bash/zsh shells to demonstrate usage on Linux.
  • Clarify the platform compatibility of PowerShell and Azure CLI, noting that PowerShell Core is available on Linux but is less commonly used than CLI.
  • Add a section or note for Linux users, highlighting best practices and any platform-specific considerations.
  • Ensure that CLI examples precede PowerShell examples, or provide parallel examples for both environments.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md ...etapp-files/azure-netapp-files-set-up-capacity-pool.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page displays a Windows bias by referencing PowerShell and its module update command, providing explicit instructions for PowerShell users, and mentioning PowerShell before any Linux equivalents. There are no Linux-specific instructions or examples, such as Bash or shell commands for updating the Azure CLI or interacting with Azure NetApp Files, and no mention of Linux tools or patterns.
Recommendations
  • Add Linux-specific instructions, such as how to update the Azure CLI on Linux (e.g., using apt, yum, or curl).
  • Include Bash or shell command examples alongside PowerShell commands for parity.
  • Mention cross-platform compatibility for CLI and REST API usage, clarifying that steps apply to both Windows and Linux environments.
  • Provide links or references to Linux documentation for Azure NetApp Files management.
  • Ensure that examples and tool references are presented in a platform-neutral order, or alternate between Windows and Linux where appropriate.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-cache-volumes.md ...articles/azure-netapp-files/configure-cache-volumes.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias primarily in the feature registration section, where Azure PowerShell commands are presented first and in detail, with Azure CLI (which is cross-platform and more common on Linux) only briefly mentioned as an alternative. The PowerShell examples are highlighted and formatted, while the CLI commands are referenced via a link, not shown inline. Additionally, there is a general assumption of familiarity with Windows-centric tools and patterns (e.g., Active Directory, SMB, PowerShell), and Linux equivalents (such as LDAP, NFS) are mentioned but not given equal prominence or step-by-step examples. No explicit Linux shell (bash) commands or instructions are provided for feature registration or management.
Recommendations
  • Provide Azure CLI command examples inline and with equal prominence as PowerShell, especially for feature registration and status checking.
  • Explicitly mention and show bash shell command examples where applicable, not just PowerShell.
  • Ensure Linux-native tools and patterns (e.g., LDAP, NFS) are described in as much detail as their Windows counterparts (e.g., AD, SMB).
  • When referencing commands, do not default to Windows/PowerShell first; present both options side-by-side or in tabs.
  • Clarify any platform-specific requirements or differences in the workflow for Linux and Windows administrators.
GitHub Create Pull Request
← Previous Page 1 of 10 Next →