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 351-375 of 896 flagged pages
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/snapshots-introduction.md .../articles/azure-netapp-files/snapshots-introduction.md
High Priority View Details →
Scanned: 2025-08-24 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the way it lists PowerShell as a primary tool for snapshot management, often mentioning it before or alongside Azure CLI and REST API, but without providing parity for Linux-specific tools or shell scripting. There are no Linux/Unix shell (bash) command examples or references, and scripting is only linked to a Microsoft Tech Community blog focused on SQL Server (a Windows-centric workload). The documentation does not provide explicit Linux/NFS client examples for snapshot operations, despite Azure NetApp Files' strong Linux/NFS use case.
Recommendations
  • Provide explicit bash/Azure CLI command examples for common snapshot operations, such as creating, listing, and deleting snapshots, alongside or before PowerShell examples.
  • Include Linux/NFS client examples for restoring files from snapshots, such as using standard Linux commands (cp, rsync) to access the .snapshot directory.
  • When listing tools for manual or automated snapshot management, avoid listing PowerShell first or exclusively; instead, present Azure CLI and REST API equally or before PowerShell, and mention bash scripting.
  • Add references or links to Linux-focused documentation or community resources for managing Azure NetApp Files snapshots.
  • Ensure that scripting examples are cross-platform, or provide both PowerShell and bash equivalents.
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-08-23 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and screenshots for Windows environments, particularly for managing SMB permissions. All examples for setting NTFS and share permissions use Windows tools (MMC, Windows Security tab), with no mention of Linux or cross-platform alternatives. There are no Linux or Samba client instructions for accessing or managing SMB shares, and Windows terminology and tools are referenced first and exclusively.
Recommendations
  • Add instructions for managing SMB share and NTFS permissions from Linux clients, such as using smbclient, setfacl, or mount.cifs.
  • Include Linux/Samba client examples for connecting to and interacting with the SMB volume.
  • Provide parity in screenshots and walkthroughs for both Windows and Linux environments.
  • Reference cross-platform tools and clarify which steps are specific to Windows versus those that are platform-agnostic.
  • Mention any limitations or differences in SMB feature support between Windows and Linux clients.
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-08-22 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for creating an SMB volume in Azure NetApp Files demonstrates a Windows-centric bias. All examples and instructions for managing SMB permissions and shares are provided exclusively for Windows environments, using Windows tools such as MMC and referencing Windows-specific workflows. There are no examples or guidance for Linux clients, even though SMB is supported on Linux via tools like smbclient or mount.cifs. The documentation assumes the administrator is operating from a Windows system, omitting parity for Linux-based management or access.
Recommendations
  • Add equivalent instructions and examples for managing SMB shares and permissions from Linux clients, using tools such as smbclient, mount.cifs, or setfacl.
  • Include screenshots or command-line examples for accessing and mounting SMB volumes from Linux systems.
  • When describing SMB features (such as encryption or access-based enumeration), clarify how these features behave or can be configured from both Windows and Linux clients.
  • Avoid assuming the use of Windows-only tools (like MMC) and provide cross-platform alternatives where possible.
  • In sections where Windows-specific commands or interfaces are mentioned, add parallel Linux instructions or links to relevant Linux documentation.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-solution-architectures.md ...app-files/azure-netapp-files-solution-architectures.md
High Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
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 and SQL Server solutions are given their own prominent section, and Windows-specific tools and patterns (such as DFS Namespaces, SMB, FSLogix, and Windows DFS-N) are mentioned explicitly and sometimes before Linux equivalents. Some sections (e.g., Virtual Desktop Infrastructure) focus almost exclusively on Windows technologies, with little or no Linux alternative coverage. There are also references to Windows-specific high availability and deployment guides for SAP, sometimes listed before Linux guides. While Linux workloads are represented, the structure and example selection often prioritize or assume Windows environments.
Recommendations
  • Ensure Linux and Windows solutions are presented with equal prominence and parallel structure, including in section ordering and headings.
  • For every Windows-specific tool or pattern (e.g., DFS-N, SMB, FSLogix), provide Linux/NFS or open-source alternatives and examples, or explicitly state if not applicable.
  • Where possible, add Linux-focused examples for Virtual Desktop Infrastructure (e.g., Linux VDI solutions or profile management).
  • In SAP solution sections, alternate the order of Windows and Linux guides, or group by OS with clear parity.
  • Review all reference lists to ensure that for each Windows example, a Linux equivalent is provided where feasible.
  • Highlight cross-platform tools and patterns (e.g., NFS, Trident, Kubernetes) in both Windows and Linux contexts.
  • Avoid language that assumes Windows as the default or primary platform.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-file-access-logs.md ...articles/azure-netapp-files/manage-file-access-logs.md
High Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows, providing detailed step-by-step instructions for setting SACLs using Windows GUI, and referencing PowerShell for feature registration. Linux/NFS instructions are less detailed, often referring users to other documentation rather than providing direct steps. There is a lack of parity in example depth and tool coverage for Linux users.
Recommendations
  • Provide step-by-step instructions for setting Audit ACEs on NFSv4.1 volumes directly in this document, using common Linux tools (e.g., setfacl, nfs4_setfacl), rather than linking out.
  • Include CLI examples for both Azure PowerShell and Azure CLI side-by-side when discussing feature registration and management.
  • Balance the order of presentation so that Linux/NFS instructions are given equal prominence and detail as Windows/SMB instructions.
  • Explicitly mention Linux equivalents for all Windows-specific tools and workflows, including screenshots or command-line examples where appropriate.
  • Add troubleshooting and best practices sections for Linux environments, similar to those provided for Windows.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/create-short-term-clone.md ...articles/azure-netapp-files/create-short-term-clone.md
High Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell commands for feature registration and status checking, with Azure CLI (cross-platform) commands mentioned only as an afterthought in text, not as explicit examples. No Linux- or macOS-specific instructions or screenshots are provided, and the step-by-step examples assume a GUI workflow without clarifying platform neutrality.
Recommendations
  • Provide explicit Azure CLI command examples alongside PowerShell commands for all registration and status-checking steps.
  • Present Azure CLI examples before or alongside PowerShell examples to avoid implying Windows-first workflows.
  • Clarify that the GUI steps are platform-agnostic or provide notes/screenshots for Linux/macOS users if there are differences.
  • Include a section or note confirming that all steps can be performed from Linux/macOS environments using Azure CLI or the Azure Portal.
  • Where possible, use neutral terminology (e.g., 'run this command in your terminal or shell') instead of assuming PowerShell usage.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-cool-access.md ...main/articles/azure-netapp-files/manage-cool-access.md
High Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is used as the primary example for feature registration, with Azure CLI only mentioned secondarily and without explicit examples. There are no Linux-specific instructions or screenshots, and the UI instructions reference right-click actions, which are more typical of Windows environments. No parity is provided for Linux shell or automation workflows, and the documentation does not address Linux-specific considerations or tools.
Recommendations
  • Provide explicit Azure CLI examples for all feature registration and management steps, including sample commands and expected output.
  • Include Linux shell (bash) equivalents for any PowerShell commands, especially for registration and status checking.
  • Add screenshots or instructions for Linux environments, such as using the Azure Portal in browsers on Linux or using CLI tools.
  • Avoid UI instructions that assume Windows-specific interactions (e.g., right-click); clarify how these actions are performed on other platforms.
  • Mention any Linux-specific considerations for NFS/SMB volumes, such as mount options, permissions, or automation scripts.
  • Ensure that all steps and examples are presented in a cross-platform manner, or provide tabs for Windows and Linux workflows.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/snapshots-introduction.md .../articles/azure-netapp-files/snapshots-introduction.md
High Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing PowerShell as a primary tool for snapshot management, referencing Windows-centric scripting (PowerShell) before Linux alternatives, and omitting explicit Linux shell or command-line examples. While Azure CLI and REST API are mentioned (which are cross-platform), PowerShell is specifically highlighted, and there are no bash or Linux shell script examples. Additionally, external script examples reference SQL Server (a Windows-centric workload), and there is no mention of Linux-specific tools or usage patterns.
Recommendations
  • Add explicit Linux shell (bash) examples for snapshot management alongside PowerShell, especially for common operations like create, restore, and delete.
  • When listing tools, mention cross-platform options (Azure CLI, REST API) before platform-specific ones (PowerShell), or group them together to avoid perceived prioritization.
  • Include example scripts for Linux environments, such as bash scripts using Azure CLI, to demonstrate parity.
  • Reference Linux workloads (e.g., Oracle, PostgreSQL) in addition to Windows-centric ones like SQL Server when discussing application-consistent snapshots.
  • Clarify that all listed tools (Azure CLI, REST API, PowerShell) are available on both Windows and Linux, and provide links to installation guides for both platforms.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/whats-new.md ...ocs/blob/main/articles/azure-netapp-files/whats-new.md
High Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Heavy Examples
Summary
The documentation for Azure NetApp Files exhibits a moderate Windows bias. Features and enhancements related to Windows technologies (such as SMB, Active Directory, and Windows-specific tools) are frequently mentioned, often before or in greater detail than their Linux/NFS counterparts. Several features are described primarily in the context of Windows environments (e.g., SMB Continuous Availability, Access-based Enumeration, non-browsable shares, and integration with Windows tools like Windows File Explorer). In some cases, Windows/SMB scenarios are explained in depth, while Linux/NFS features are mentioned more briefly or as secondary considerations. However, there is also significant Linux/NFS and dual-protocol coverage, and some Linux-specific tools (like AzAcSnap) are highlighted, indicating an effort toward cross-platform support.
Recommendations
  • Ensure that for every Windows/SMB example or feature description, equivalent Linux/NFS examples and scenarios are provided with equal detail and prominence.
  • When introducing features that are protocol-specific (e.g., SMB vs. NFS), present both protocols together, or alternate which is mentioned first to avoid a consistent Windows-first ordering.
  • Where Windows tools or workflows (e.g., Windows File Explorer, Active Directory) are referenced, include parallel Linux tools or workflows (e.g., Linux file managers, LDAP, Kerberos) and provide usage guidance.
  • Expand documentation for Linux/NFS-specific features to match the depth and clarity of Windows/SMB sections, including troubleshooting, best practices, and integration tips.
  • Review language to ensure that Linux/NFS use cases are not treated as secondary or optional, but as first-class scenarios.
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: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All configuration commands and monitoring instructions use Windows-specific tools (PowerShell cmdlets like Get-SmbClientNetworkInterface, set-SmbClientConfiguration, and Windows Performance Monitor). References to SMB features and encryption are framed in terms of Windows versions and tools, with no mention of Linux or cross-platform SMB clients. There are no Linux or Samba examples, and no discussion of how to achieve similar monitoring or configuration on non-Windows systems.
Recommendations
  • Add equivalent Linux/Samba examples for SMB Multichannel configuration and verification (e.g., using smb.conf, smbstatus, or smbtree).
  • Include Linux command-line tools (such as netstat, ifconfig, ethtool, or perf) for monitoring network interfaces and SMB connections.
  • Discuss SMB feature support and configuration for popular Linux distributions, including how to enable or verify SMB Multichannel, signing, and encryption in Samba.
  • Provide performance monitoring guidance for Linux (e.g., using iostat, atop, or other Linux-native tools).
  • Reference both Windows and Linux documentation for SMB features, and clarify any differences in feature support or configuration steps.
  • Where possible, use cross-platform terminology and avoid assuming the reader is using Windows exclusively.
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-08-21 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for creating an SMB volume in Azure NetApp Files demonstrates a Windows bias. All examples and instructions for managing SMB permissions and shares are provided exclusively for Windows environments, referencing Windows tools such as MMC and the Windows Security tab. There are no examples or guidance for managing SMB shares or permissions from Linux or macOS clients, nor are cross-platform tools or commands mentioned. The documentation assumes the administrator is using a Windows client for all SMB management tasks.
Recommendations
  • Include instructions and examples for managing SMB shares and permissions from Linux clients, such as using smbclient, mount.cifs, or setfacl.
  • Mention and provide examples of cross-platform tools (e.g., Samba utilities) for accessing and managing SMB shares.
  • Where Windows-specific tools are referenced (e.g., MMC, Security tab), add equivalent steps or notes for Linux/macOS environments, or clarify if certain features are only available via Windows.
  • In sections about mounting or accessing SMB shares, provide both Windows and Linux command-line examples.
  • Review and update the documentation to ensure Linux and macOS administrators can perform all necessary tasks without requiring access to a Windows machine.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-file-access-logs.md ...articles/azure-netapp-files/manage-file-access-logs.md
High Priority View Details →
Scanned: 2025-08-21 00:01
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 in several areas. Windows administration steps and tools (such as GUI instructions and PowerShell commands) are presented first and in detail, while Linux/NFS instructions are less explicit and often deferred to other documentation. PowerShell is used for feature registration, with Azure CLI only briefly mentioned. There are no Linux command-line examples for setting audit ACEs or SACLs, and Windows GUI tools are described in detail, but equivalent Linux workflows are missing.
Recommendations
  • Provide explicit Linux command-line examples for setting Audit ACEs on NFSv4.1 volumes, such as using nfs4-acl-tools or setfacl.
  • Include step-by-step instructions for configuring audit ACEs on Linux, similar to the detailed Windows GUI steps.
  • Present Azure CLI examples for feature registration before or alongside PowerShell, and ensure parity in instructions for both platforms.
  • Balance the order of presentation so that Linux and Windows instructions are given equal prominence.
  • Reference Linux administration hosts and tools (e.g., nfs4-acl-tools, setfacl) where appropriate, not just Windows hosts.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-metrics.md ...icles/azure-netapp-files/azure-netapp-files-metrics.md
High Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for feature registration and status checking, mentioning PowerShell before Azure CLI, and omitting any Linux-specific or cross-platform command-line examples. There are no examples or guidance for Linux users or for using non-Windows tools to access or automate metrics.
Recommendations
  • Provide equivalent Azure CLI examples alongside PowerShell commands, with full syntax and output expectations.
  • Present Azure CLI (cross-platform) examples before or alongside PowerShell to avoid the impression of Windows-first bias.
  • Include explicit instructions or examples for Linux/macOS users, such as using bash or shell scripts for automation.
  • Where screenshots or UI navigation are shown, clarify that the Azure portal is web-based and platform-agnostic.
  • Audit for any other sections where only Windows tools or terminology are used, and add Linux/cross-platform alternatives.
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-08-21 00:01
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 is given equal prominence to Azure CLI, despite PowerShell being primarily a Windows-centric tool (even though it is now cross-platform, its usage is still heavily associated with Windows). There are no explicit Linux shell (bash) examples or references, and no mention of Linux-native tooling or usage patterns. The documentation does not provide any Linux-specific guidance or examples, which may make Linux users feel less prioritized.
Recommendations
  • Add explicit bash/Linux shell examples for common Azure NetApp Files operations using Azure CLI.
  • Clarify that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
  • If mentioning PowerShell, note that it is available cross-platform, but provide parity by including bash or shell equivalents.
  • Consider listing Azure CLI before PowerShell in tables and descriptions, as it is the primary cross-platform tool.
  • Include a section or note for Linux users about installation and usage best practices.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-solution-architectures.md ...app-files/azure-netapp-files-solution-architectures.md
High Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. In several sections, Windows workloads and tools are mentioned first or exclusively, such as in the 'Windows Apps and SQL Server solutions' and SAP NetWeaver sections, where Windows-specific technologies (e.g., DFS Namespaces, SMB, FSLogix) are highlighted. There are references to Windows tools and patterns (DFS-N, FSLogix, SMB) without always providing equivalent Linux/NFS or cross-platform alternatives. Some solution areas (e.g., Virtual Desktop Infrastructure) focus almost entirely on Windows-based technologies, with little or no mention of Linux-based desktop solutions. While Linux workloads are covered in detail in some sections, the overall structure and example ordering often prioritize Windows scenarios.
Recommendations
  • Ensure that for every Windows-specific example or tool (e.g., DFS-N, FSLogix, SMB), a Linux/NFS or cross-platform equivalent is provided and described with equal prominence.
  • When listing solution references, alternate or group by platform rather than consistently listing Windows first.
  • Expand Virtual Desktop Infrastructure coverage to include Linux-based VDI solutions, if supported.
  • In sections where Windows tools are discussed (e.g., DFS-N for SAP), provide parallel guidance for Linux/NFS-based approaches.
  • Review all example scenarios to ensure Linux and open-source workloads are given equal depth and visibility as Windows workloads.
  • Where possible, use neutral, cross-platform terminology and avoid implying Windows is the default or primary use case.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-cool-access.md ...main/articles/azure-netapp-files/manage-cool-access.md
High Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell command examples for feature registration, mentioning PowerShell before Azure CLI, and omitting explicit Linux or cross-platform command-line examples. The registration steps are shown exclusively with PowerShell, and while Azure CLI is referenced, no CLI command-line examples are provided. There are no Linux-specific instructions or screenshots, and the UI instructions use Windows-centric terminology (e.g., 'right-click').
Recommendations
  • Provide Azure CLI command-line examples alongside PowerShell for all registration and management steps, showing both syntaxes explicitly.
  • Include Linux/macOS-specific instructions or notes where relevant, especially for command-line operations.
  • Use neutral UI terminology (e.g., 'select', 'open context menu') instead of 'right-click', or clarify how to perform these actions on different platforms.
  • Add screenshots or CLI output examples from non-Windows environments to demonstrate parity.
  • Consider a tabbed or side-by-side format for PowerShell and CLI examples, making it clear that both are supported and cross-platform.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/snapshots-introduction.md .../articles/azure-netapp-files/snapshots-introduction.md
High Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a primary tool for snapshot management and automation, and by referencing Windows-centric scripting and tools before Linux alternatives. There are no explicit Linux shell or scripting examples, and the documentation does not mention Linux-specific tools or patterns for managing Azure NetApp Files snapshots. While NFS and SMB are mentioned for volume creation, the operational examples and tooling references favor Windows environments.
Recommendations
  • Include Linux shell (bash) and scripting examples alongside PowerShell, especially for common tasks such as creating, restoring, and deleting snapshots.
  • Reference Linux-native tools (e.g., Azure CLI usage in bash, REST API calls via curl, automation with cron jobs) equally or before Windows/PowerShell tools.
  • Provide sample commands for both Windows and Linux environments when discussing manual and automated snapshot management.
  • Clarify cross-platform support and parity in tooling, ensuring that Linux administrators have clear guidance and examples.
  • Add links to Linux-focused documentation or community resources for Azure NetApp Files snapshot management.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-nfs.md ...-docs/blob/main/articles/azure-netapp-files/faq-nfs.md
High Priority View Details →
Scanned: 2025-08-20 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page contains a section specifically addressing Windows NFS client configuration issues, providing PowerShell commands and Windows-specific mount examples, but does not provide equivalent troubleshooting or configuration guidance for Linux clients. This creates a Windows bias by focusing on Windows tools and omitting Linux examples in areas where both platforms are relevant.
Recommendations
  • For sections that address client-side configuration or troubleshooting (e.g., improving folder lookup performance), provide equivalent Linux commands and configuration steps alongside Windows instructions.
  • When presenting examples (such as mounting NFS volumes), include both Windows and Linux command-line examples to ensure parity.
  • If a Windows-specific issue is discussed (such as CaseSensitiveLookup), clarify whether similar issues exist on Linux and, if so, provide guidance; if not, explicitly state that the issue is Windows-only.
  • Review all sections for platform parity and ensure that Linux administrators are equally supported, especially given that NFS is more commonly used in Linux environments.
  • Consider reordering examples or explanations so that Linux and Windows are presented with equal prominence, or alternate which platform is presented first.
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-08-20 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for Windows environments, particularly for managing SMB permissions and share properties. It references Windows-specific tools (MMC, Windows File Browser, Control Panel), and does not mention or provide equivalent Linux commands or tools for accessing or managing SMB shares. Linux access patterns and tools are omitted, despite SMB being cross-platform.
Recommendations
  • Include Linux-based instructions for mounting and managing SMB shares, such as using the 'mount.cifs' command or 'smbclient'.
  • Provide examples of setting SMB permissions from Linux clients, or clarify any limitations.
  • Mention Linux GUI tools (e.g., Nautilus, Dolphin) for browsing SMB shares, if applicable.
  • Where Windows tools (MMC, File Browser) are referenced, add Linux equivalents or note the differences in management approaches.
  • Add a section or callout on how Linux and macOS clients can connect to and use SMB volumes, including authentication and permission considerations.
  • Ensure that any troubleshooting or next steps include Linux-relevant guidance.
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: 2025-08-20 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page references PowerShell and REST API usage with PowerShell, but does not provide equivalent Linux or cross-platform automation examples (e.g., Bash, curl, or Python). The REST API section specifically links to 'REST API using PowerShell for Azure NetApp Files', suggesting a Windows-centric approach. No explicit Linux or cross-platform command-line examples are provided for REST API usage, and the only automation example is PowerShell-focused.
Recommendations
  • Provide REST API usage examples using cross-platform tools such as curl or HTTPie, and/or include sample scripts in Bash or Python.
  • When referencing REST API automation, link to or include both PowerShell and Bash/curl examples to ensure parity.
  • Explicitly state that the Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Avoid referencing PowerShell as the primary or sole automation tool; instead, present it alongside alternatives.
  • Add a section or note for Linux/macOS users on how to perform equivalent operations using native tools.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/understand-volume-languages.md ...cles/azure-netapp-files/understand-volume-languages.md
High Priority View Details →
Scanned: 2025-08-20 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools, settings, and workflows (such as PowerShell, Notepad, Notepad++, Windows Terminal, Windows Explorer, and region settings) are frequently mentioned first or in greater detail than their Linux equivalents. PowerShell and CMD examples are provided for encoding and file manipulation, while Linux examples are often secondary or less detailed. Some sections (e.g., file encoding conversion) focus on Windows tools and only briefly mention Linux alternatives. There are also more screenshots and step-by-step instructions for Windows environments compared to Linux.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not just after or as an aside.
  • Provide equivalent step-by-step instructions and screenshots for Linux tools (e.g., GNOME Terminal, KDE Konsole, nano/vim for encoding, locale settings in Linux, etc.).
  • When discussing encoding conversion, offer Linux-first examples (e.g., using iconv, file, or recode) before or alongside PowerShell/Windows methods.
  • Highlight Linux-specific behaviors and troubleshooting tips (e.g., dealing with locale or font issues in popular Linux terminals).
  • Mention Linux tools (such as Midnight Commander, GNOME Files, or xdg-open) for file management and encoding inspection, not just Windows Explorer.
  • Balance the number of screenshots and detailed walkthroughs between Windows and Linux environments.
  • Where possible, use cross-platform tools or commands (e.g., Python scripts, cross-platform editors) to demonstrate encoding handling.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-cool-access.md ...main/articles/azure-netapp-files/manage-cool-access.md
High Priority View Details →
Scanned: 2025-08-20 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for feature registration, mentioning PowerShell commands before Azure CLI, and omitting direct Linux/CLI examples or screenshots. The registration steps are shown exclusively with PowerShell, and while Azure CLI is referenced, no explicit CLI command examples are given. There are no Linux-specific instructions or parity in command-line guidance.
Recommendations
  • Provide explicit Azure CLI command examples (e.g., 'az feature register ...') alongside PowerShell for all registration and status-check steps.
  • Present Azure CLI examples before or at least equally with PowerShell to avoid Windows-first ordering.
  • Include screenshots or instructions that are platform-agnostic or show both Windows and Linux environments where applicable.
  • Clarify that all operations can be performed from Linux/macOS using Azure CLI, and link to relevant CLI documentation.
  • Consider adding a section or callout for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-file-access-logs.md ...articles/azure-netapp-files/manage-file-access-logs.md
High Priority View Details →
Scanned: 2025-08-20 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows/Powershell workflows and tools first or exclusively in several sections. The instructions for setting SACLs on SMB shares are detailed for Windows administration hosts, with no equivalent step-by-step guidance for Linux clients. Powershell commands are shown (even if commented out), and Windows GUI tools are described in detail, while Linux/NFSv4.1 instructions are minimal and refer to external documentation. There is also a lack of parity in example depth and clarity between Windows and Linux workflows.
Recommendations
  • Provide equivalent, step-by-step instructions for setting Audit ACEs on NFSv4.1 shares from a Linux client, including command-line examples (e.g., using nfs4_setfacl).
  • When mentioning registration or configuration steps, include both Powershell and Azure CLI examples side-by-side, not just as a note.
  • Balance the depth of explanation for Windows and Linux workflows, ensuring both have clear, actionable steps in the documentation.
  • Avoid always listing Windows tools or workflows first; alternate or present both platforms in parallel tabs or sections.
  • Explicitly mention and provide guidance for Linux administration hosts where applicable, not just Windows.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/snapshots-introduction.md .../articles/azure-netapp-files/snapshots-introduction.md
High Priority View Details →
Scanned: 2025-08-20 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the way it presents tooling and examples. In the 'Ways to create snapshots' section, PowerShell is listed as a primary tool alongside Azure Portal, REST API, and Azure CLI, but there is no mention of Linux-specific command-line usage or examples. The documentation does not provide explicit Linux shell (bash) examples or highlight Linux-native scripting approaches, and PowerShell is mentioned before any Linux-native alternatives. There are no Linux-specific instructions or parity in scripting examples, and the only scripting reference points to a SQL Server/Windows-centric blog post.
Recommendations
  • Add explicit Linux/bash shell examples for snapshot management using Azure CLI, including sample commands.
  • When listing tools, present Azure CLI and REST API before PowerShell, or group them neutrally, to avoid a Windows-first impression.
  • Include references or links to Linux/Unix scripting guides for Azure NetApp Files snapshot management.
  • Provide example scripts for both PowerShell and bash to ensure parity.
  • Ensure that any external blog or script references include Linux-compatible examples, not just Windows/SQL Server/PowerShell scenarios.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-cool-access.md ...main/articles/azure-netapp-files/manage-cool-access.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in its command-line examples and tool references. Feature registration steps are shown primarily using Azure PowerShell cmdlets, with Azure CLI (cross-platform) only mentioned secondarily and without explicit CLI command examples. There are no Linux shell or Bash examples, and the UI workflow descriptions and screenshots focus on graphical interfaces, which are more common in Windows environments. No Linux-specific guidance or parity is provided.
Recommendations
  • Provide explicit Azure CLI command examples (e.g., 'az feature register', 'az feature show') alongside or before PowerShell examples, with full syntax and sample output.
  • Include Bash/Linux shell command equivalents where relevant, especially for automation or scripting scenarios.
  • Clarify that all command-line steps can be performed on Linux, macOS, and Windows, and specify any OS-specific prerequisites if needed.
  • Balance UI workflow descriptions with CLI alternatives, especially for users who may not have access to the Azure Portal or prefer automation.
  • Add a section or callout for Linux/macOS users, highlighting any differences or confirming full parity.
GitHub Create Pull Request
← Previous Page 15 of 36 Next →